Privacy Policy

Last updated: October 2026

1. Information we collect

We collect the information you provide directly: name, email, optional profile photo, timezone, preferred language, and all the content you create inside the platform (projects, tasks, comments, wikis, time entries).

If an organization asks you to confirm a job you received, and you have no account, the person from the organization who asks you saves on screen what you write: your name, your ID number if you choose to give it, and your stroke, as a list of coordinates and never as an image, plus the date and who held the device. Its purpose is to record that a job was received. The data belongs to the organization: it decides why it asks, it is the controller, and Orkestra keeps it on its behalf. It is not a digital signature and does not promise legal validity. Only when someone sees the ID number is it noted in the audit log; opening the task without seeing it is not recorded. Each member of the organization connects their own AI assistant, and the one of any member who can see that task, and is not a guest, can read the confirmations, ID number included. They are kept until the organization is deleted; to have them removed, ask the organization: its administrator erases the name, the document and the stroke, and only the date remains.

2. How we use your information

We use your information to operate the service, authenticate you, send operational notifications (due date reminders, assignments, configurable digests), and protect the platform from abuse. We do not use it for ad profiling and we do not share it with ad networks.

3. Storage and security

Your data is stored on our own servers, hosted in France (European Union). There is a single server and no other region to choose: every organization's data lives there. Passwords are hashed with bcrypt; refresh tokens are rotated with compromise detection. All connections use TLS 1.2+. Sensitive tokens (API keys, SCIM) are stored only as SHA-256 hashes.

4. Data sharing

We do not sell your personal information. We share it with third parties only when strictly necessary to operate the service:

5. Google user data

Orkestra uses two Google services, and neither turns itself on: both start when you connect them.

Sign in with Google

The "Continue with Google" button asks for openid email profile. We receive your email address, whether Google holds it as verified, your name and the address of your photo. With that we recognise your account or create it: the email becomes your identifier, and the name and photo fill in your profile, which you can change afterwards. We ask for no ongoing access and store no credential from that permission, so once you are in there is no door left open into your Google account.

Google Calendar sync

How we access it. We ask for a single permission, calendar.app.created, which reaches only the calendars this application created. Your existing calendars and appointments are not kept safe by a promise of ours: they are unreachable for Orkestra. On connecting we create a calendar of our own in your account, named "Orkestra", and work only inside it.

How we use it. We write your tasks, your assigned subtasks and your activities there — the name, the date, the time and one reminder. Every fifteen minutes we read that same calendar to see whether you changed something, and from what we read we take two things and no others: when it is, and what it is called. An event Orkestra did not write is ignored rather than adopted. None of this is used for advertising, for profiling you, or to train artificial-intelligence models, ours or anyone else's.

What we store. The credential that lets us keep writing, the identifier of the calendar we created, and for each event we wrote its identifier and its start date, so we know which task it belongs to. All of it lives on the same server in France as the rest of your data. We store the contents of no event we did not write ourselves.

Who we share it with. Nobody. No data received from Google is sold, handed over or transferred to another service.

How you delete it. Disconnecting the calendar in Settings → Calendar deletes the credential and the links between events and tasks. The "Orkestra" calendar stays in your Google account, which is yours: you keep it or delete it. You can also withdraw the permission at myaccount.google.com/permissions. Deleting your Orkestra account removes all of the above.

Limited Use

Orkestra's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6. Your rights

You can access, correct, or delete your information at any time from your account settings. The steps to delete your account are in Delete your account. To exercise GDPR rights (access, portability, erasure, rectification) write to us at privacy@orkestra.team.

7. Retention

We retain your information while your account is active. When you delete your account, your email, password, photo, sessions, tokens and preferences are removed and you leave every organization; your personal projects and any organization where you were the only member are deleted. What you did inside an organization — tasks, comments, hours and attendance, sales, expenses, inventory movements — is kept with your name next to each record, because the people who stay need to know who did what; no contact details are kept. If your organization kept a staff file on you, that file stays as the employer's record, with no fixed period, and is read only by those who have permission for it; it is deleted together with the organization or when someone with that permission deliberately deletes it. An electronic invoice already issued keeps the buyer's tax ID (CUIT) even if the contact is deleted, because the law requires it, but not the name. Organization administrators may set how many days their audit log is kept, and configure policies that automatically delete old messages, time entries, notifications and comments. If you sign in without email, only with a PIN on a phone, your account is deleted by whoever administers people in your organization, and the same is erased as if you deleted it yourself.

8. Contact

For privacy inquiries, write to us at privacy@orkestra.team.