Privacy Policy

Introduction

This Privacy Policy explains how Outcoder Sàrl processes personal data in connection with Orpius.

Orpius is an AI execution and collaboration platform operated by Outcoder Sàrl, a software company incorporated in Switzerland.

Data controller and contact details:

Registered office: Collonge-Bellerive, Geneva
Commercial Register: CH-660-0276012-9
UID/VAT: CHE-466.276.960

You can contact us through our contact form.

In this policy, "Orpius" or the "Service" means the Orpius software platform and associated services. "We", "us" and "our" refer to Outcoder Sàrl.

1. Information we collect

We aim to collect and process only the personal data reasonably necessary to provide, secure and operate Orpius.

1.1 Account information

When you create an account, we collect information such as your username or name, email address, authentication credentials and account identifiers.

We may also record account creation dates, login activity, organisation membership, access permissions and acceptance of applicable terms.

We use this information to administer accounts, authenticate users, protect the Service and communicate with account holders.

1.2 Content provided through Orpius

When you use the Service, we process information you provide or authorise Orpius to access, including:

• Messages, prompts and conversations.
• Files, documents and other workspace content.
• Instructions for AI assistants and Operations.
• AI-generated responses and tool results.
• Information used by automated processes.
• Configuration of workspaces, integrations and tools.

We process this information to provide the functionality you or your organisation request.

1.3 External participants

Orpius allows users to communicate and collaborate with people who do not have an Orpius account.

For example, when an assistant arranges a meeting by email, we may process external participants' names, email addresses, messages and other information associated with the interaction.

We use this information to route and deliver communications, manage conversations and carry out the requested activity.

1.4 Connected services

If you connect Google Calendar or another external service, we process the authorisation information and service data needed to provide the integration.

Depending on the integration, this may include calendar availability, event details, identifiers, files or other information required for an authorised task.

1.5 Communications with us

When you contact us, we process your contact details and message to respond to your enquiry, provide support or manage our relationship with you.

1.6 Technical and security information

Our systems may process IP addresses, browser and device information, timestamps, requests, application diagnostics, operational logs and security events.

We use this information to operate, secure, troubleshoot and improve the reliability of Orpius.

2. How we use personal data

We process personal data to:

• Create, authenticate and administer accounts.
• Provide AI assistants, workspaces and Operations.
• Execute instructions and automated activities.
• Enable communication and collaboration.
• Operate authorised integrations and connected services.
• Provide technical support and resolve problems.
• Maintain security, reliability and service availability.
• Understand and improve the Service.
• Communicate important operational and legal information.
• Comply with applicable laws and protect legitimate rights.

We do not sell personal data or use Google Calendar information for advertising.

3. Email addresses, secrets and AI providers

Orpius separates communication routing and sensitive credentials from the information supplied to AI models.

3.1 Email addresses

Email addresses held by Orpius as account, sender, recipient, CC or routing information are not supplied to AI models merely to address or deliver communications.

This applies to both account holders and external participants. An assistant can therefore help compose and process communications without needing access to their underlying delivery addresses.

This separation applies to addressing information managed by Orpius. If an email address appears in a message body, prompt, document or other task content, it may be included in information processed by the selected AI provider.

3.2 Secrets and credentials

Orpius manages sensitive credentials, such as API keys and OAuth refresh tokens, separately from ordinary conversational content.

AI models may receive references to authorised capabilities, but do not need the underlying secret values to decide which tools to use.

When an authorised tool requires a credential, Orpius resolves it within the execution environment rather than supplying it as ordinary model context.

3.3 Information sent to AI providers

Orpius allows users and organisations to configure different AI models and providers. Some plans or deployments may also make AI inference available through an Orpius-managed arrangement.

When an AI model is used, information relevant to the task may be transmitted to its provider. Depending on the task, this may include:

• Prompts and instructions.
• Relevant conversation history and context.
• Selected file or document contents.
• Information returned by authorised tools.
• Relevant information from connected services.

The provider, processing location, contractual arrangements and data practices depend on the model configuration and applicable service.

Where you or your organisation select a provider, you should review its terms and data-processing practices before transmitting sensitive information.

4. Google Calendar integration

Orpius offers an optional Google Calendar integration that enables AI assistants to help with meeting scheduling and calendar management.

The integration is activated only when a user authorises the relevant Google permissions.

4.1 Google information accessed

Orpius requests the following Google Calendar OAuth scopes:

• https://www.googleapis.com/auth/calendar.events.freebusy — allows Orpius to check free/busy availability on calendars the user can access.
• https://www.googleapis.com/auth/calendar.events.owned — allows Orpius to view, create, modify and delete events on calendars owned by the user.

Information accessed may include availability, event dates and times, titles, descriptions, locations, attendees and identifiers, depending on the authorised operation.

4.2 How Calendar data is used

Calendar data is used to provide features authorised by the user, including:

• Checking availability and finding meeting times.
• Coordinating schedules with other participants.
• Creating appointments and calendar events.
• Modifying or cancelling authorised events.
• Responding to calendar-related instructions.

AI assistants may perform these actions in response to a direct request or according to an authorised Operation or automation configured by the user.

4.3 Use of AI models with Calendar data

Relevant Calendar information may be processed by the AI model used by an assistant where necessary to provide a requested or authorised calendar-related feature.

For example, an assistant may use availability information to suggest meeting times or event details to help prepare a scheduling response.

Such processing is limited to the authorised user-facing functionality and must comply with Google's applicable data-use restrictions.

We do not use or transfer information received from Google Calendar APIs to develop, train or improve general-purpose or non-personalised AI or machine-learning models.

We do not sell Google user data, use it for advertising or make it available to data brokers.

4.4 Storage and protection

Orpius stores the authorisation information necessary to maintain a connected Google account. Refresh credentials are protected using encryption.

Short-lived access tokens are used to make authorised Google API requests. Credentials are managed separately from the AI model's conversational context.

Calendar information may be included in conversation histories, assistant responses or records of authorised actions. This information is subject to the applicable retention and deletion rules.

4.5 Revoking access and requesting deletion

You can revoke Orpius's access to your Google account through Google Account connections .

Revoking access prevents the existing authorisation from being used for further access to Google data.

You may also request removal of stored connection credentials and personal data associated with the integration through our contact form.

Revoking access does not automatically remove information already included in conversation histories or other records. Such information is subject to the applicable retention policy and deletion rights.

4.6 Google API Limited Use

Orpius's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements.

Google user data is accessed, used and transferred only for permitted purposes, including authorised user-facing functionality, security and legal compliance, subject to Google's applicable policies.

5. Communications from us

We use account contact information to send communications necessary to operate Orpius, including:

• Registration and account notifications.
• Security and authentication notices.
• Responses to enquiries and support requests.
• Service availability and operational notices.
• Important Beta announcements.
• Changes to our legal terms and policies.

We may separately send optional product news or promotional communications where permitted by law. Where consent is required, we will obtain it before sending these messages.

You may unsubscribe from optional marketing communications without affecting necessary account or security notifications.

6. Sharing information

We disclose personal information only where reasonably necessary for the purposes described in this policy.

6.1 AI providers

Relevant task information may be transmitted to the AI provider used by the relevant assistant or activity, as described above.

6.2 Other participants

When you ask Orpius to communicate or collaborate with another person, relevant information may be shared with that person.

Other users in a shared workspace may also access information according to their permissions and organisational configuration.

6.3 Service providers

We use third-party providers to help operate Orpius and its website. These may include:

• Hosting and infrastructure providers.
• Email delivery and routing services.
• Security, logging and monitoring services.
• Website analytics and contact form providers.
• Other services necessary to provide Orpius.

Our public website uses Formspree to process contact enquiries and Google reCAPTCHA to help prevent automated submissions.

These providers may process information associated with your use of their services under their applicable privacy terms.

6.4 Legal requirements

We may disclose information when required by law or a competent authority, or where reasonably necessary to protect legal rights, users or the security of the Service.

7. Google Analytics and website cookies

Our public website uses Google Analytics to understand how visitors use the website and to help improve its content and usability.

Google Analytics may collect information such as pages visited, session activity, browser and device characteristics, approximate location and pseudonymous identifiers stored in cookies.

We do not intentionally provide Orpius account credentials, secrets, private workspace content or Google Calendar data to Google Analytics.

Where applicable law requires consent for optional analytics cookies or similar technologies, those technologies are used only after obtaining the required consent.

You may refuse or withdraw optional analytics consent without losing access to essential website or Service functionality.

Essential cookies and similar technologies may also be used for authentication, security and service operation.

8. Where information is processed

The core Orpius-managed Service is hosted in Switzerland. Orpius may also be deployed in customer-controlled infrastructure.

Information may be processed outside Switzerland where we use international service providers or where users configure external models, tools and integrations.

Such processing may occur in the European Economic Area, the United States or other countries depending on the provider and configuration concerned.

Where Outcoder is responsible for an international transfer, we apply safeguards required by the relevant data-protection law.

Users and organisations selecting their own external providers should also assess the relevant processing locations and contractual arrangements.

9. Data retention and deletion

We retain personal information only for as long as reasonably necessary to provide the Service and fulfil legitimate operational or legal requirements.

9.1 Conversations

Orpius supports configurable conversation retention. The default retention setting is 30 days of inactivity.

Conversations are eligible for automatic deletion when no new messages have been recorded within the configured inactivity period, subject to applicable retention settings and exceptions.

New messages can extend the retention period. An actively used conversation may therefore remain available longer than 30 days after its creation.

9.2 Other information

Other information may have different retention periods appropriate to its purpose:

• Account information is normally retained while the account exists and as necessary afterwards for legitimate purposes.
• Connected-service credentials are retained while needed for an authorised integration or until removed in accordance with applicable deletion procedures.
• Workspace files and operational records are subject to their applicable retention and deletion rules.
• Support correspondence is retained as necessary to manage the enquiry and maintain appropriate records.
• Technical and security logs have retention periods appropriate to security and diagnostics.

Deleted information may remain temporarily in backups until the relevant backups expire or are replaced.

Longer retention may apply where required by law or necessary to establish, exercise or defend legal claims.

10. Security

We use technical and organisational measures designed to protect personal information against unauthorised access, disclosure, alteration, loss and destruction.

These measures include access controls, protected credentials, encrypted communications and separation of sensitive secrets from conversational data.

Orpius supports workspace permissions and controls over the capabilities made available to AI agents.

No internet-connected service can guarantee absolute security.

11. Your data protection rights

Depending on applicable law, you may have the right to:

• Ask whether we process personal data about you.
• Access personal data held about you.
• Request correction of inaccurate information.
• Request deletion where applicable.
• Object to or restrict certain processing.
• Request data portability where applicable.
• Withdraw consent where processing relies on consent.

These rights are subject to applicable legal conditions and exceptions.

To exercise your rights, please use our contact form.

We may ask you to verify your identity before responding to a request.

Where an organisation is responsible for information processed through its workspace, we may refer the request to that organisation.

You may also contact the Swiss Federal Data Protection and Information Commissioner (FDPIC) or another competent data protection authority.

12. Legal basis and organisational processing

Swiss data-protection law applies to Outcoder as a Swiss company. Other laws, including the EU General Data Protection Regulation, may also apply in relevant circumstances.

Where the GDPR requires a legal basis, processing may rely on:

• Contractual necessity to provide and administer the Service.
• Legitimate interests in operating, securing and improving Orpius, where those interests are not overridden by applicable individual rights.
• Legal obligations applying to Outcoder.
• Consent where required, including certain optional analytics or marketing activities.

Where an organisation uses Orpius to process information for its own purposes, it may act as data controller and Outcoder may act as data processor.

Separate data-processing terms or agreements may apply to these arrangements.

13. Changes to this policy

We may update this Privacy Policy as Orpius develops or as our processing practices or legal obligations change.

We will publish updated versions with a revised effective date and provide additional notice where required.

14. Contact us

For privacy questions, data access requests, deletion requests or other concerns, please use our contact form.

You can also review our Terms of Service.