Ariadne

Privacy policy

Version 2026-10-11

1. Who is responsible

Ariadne is operated by Vitalii Tyshchenko, Wolfratshauser Str. 42, 82065 Baierbrunn, Germany — a private individual, called "we" or "the operator" below, and the controller under the EU General Data Protection Regulation (GDPR). Contact: the email address in the Impressum.

2. What Ariadne is

Ariadne is a personal workspace for managing an executive career transition: target companies, search firms and other channels, contacts, opportunities, activities, projects, and your own profile and documents. Access is by invitation only, and Ariadne is in beta. Every person's workspace is its own database, separate from every other workspace.

3. What data Ariadne processes

  • Your account. When you sign in with Google, Ariadne receives the name, email address and profile picture of your Google account. It uses them to check that you are on the access list of your workspace and to show who is signed in.
  • What you enter. Your profile and positioning, target roles, location and salary expectations, CVs and other documents, and the companies, channels, opportunities, activities, projects and notes of your search.
  • Other people's data that you enter. Contacts, recruiters and interviewers, with your notes about them. You decide what you record and are responsible for having a lawful basis for it.
  • Your acceptance of the terms. Your email address, the time and the version of the terms you accepted.
  • Technical data. Server logs (IP address, time, the address requested) for security and fault-finding, and one session cookie. No tracking, no analytics services, no advertising.
  • Your AI connection and its log. If you connect an AI assistant, Ariadne stores a hash of its access token, the connection's name and permissions, and when it was created, last used and revoked. It also logs the assistant's requests: the time, the connection, whether the request was allowed, the tool called and one short identifying value — a record's number, a company or contact name, or a search query. It does not log what was returned, nor the text of notes or documents.

4. Google user data

"Google user data" is what Ariadne receives from Google about you. There are two cases: signing in, and — only if you choose it — connecting your Google Calendar.

Signing in. Ariadne receives the identifier of your Google account, your name, your email address, whether Google has verified that address, and the address of your profile picture. It stores them in your workspace's database, together with the tokens Google issues at sign-in — which Ariadne does not use to call Google on your behalf — and your session, including the session's IP address and browser identifier. It uses all of this only to sign you in, to check your access and to show who is signed in, and shares it with no one.

Connecting your Google Calendar (optional). Connecting a calendar is being introduced during the beta; this section applies from the moment you connect one. Ariadne asks for the permission only when you press "Connect calendar", never at sign-in.

  • What Ariadne reads. The list of your calendars (name and your access level). From every calendar that counts as busy: when its events start and end, so that Ariadne knows when you are not free. From every calendar with "Show details" on, also each event's title, place, participants (name, email address and whether they accepted), the organiser's email address, your own response, its status and its link. When you connect, the calendars you own or can edit count as busy, and "Show details" is on for your main calendar only; a calendar you add later gets the same defaults. You see both switches for every calendar when you connect and can change them at any time in Settings. Ariadne does not import or store event descriptions, attachments or conference access codes.
  • What Ariadne writes. Only a separate calendar named "Ariadne" that it creates in your Google account. There it places the Activities you planned with a time. The permission Ariadne asks Google for does not allow it to change, move or delete anything in your other calendars. Inside the "Ariadne" calendar it changes only the events of its own Activities. An event Ariadne writes carries the Activity's title, its time and a link back to Ariadne; no contact names and no notes.
  • What Ariadne uses it for. To show your real week in the Planner beside your planned Activities; to work out when you are free and propose time slots, which you accept or decline; to move an Activity whose time Ariadne itself chose to the next free slot when a new event lands on it — Ariadne tells you and you can undo it, and it never moves an Activity whose time you set; to keep the Activities in the "Ariadne" calendar in step with Ariadne; and to offer — never to do on its own — to log a meeting that has ended, to link a meeting to a planned Activity, or to add a participant as a Contact when you click. Nothing else.
  • How Ariadne stores it. In your workspace's database in the EU (Frankfurt): the event details listed above, with the identifiers needed to keep them in step with Google, for about two weeks back and two months ahead, refreshed while you use Ariadne; the email address of the connected Google account, the permissions you granted and your time zone; your list of calendars and your choices for each; the record of your consent; and the refresh token Google issues, stored encrypted. The token and the imported events are not part of your workspace export.
  • Who Ariadne shares it with. No one. In particular, Ariadne does not pass your calendar events to an AI assistant: an assistant you connected to Ariadne sees Ariadne's own Activities, never your events and never the free time worked out from them. A record you make yourself from an event — a meeting you log, a participant you add as a Contact — becomes part of your workspace like anything else you enter, and your assistant reads it as such. If you want your assistant to work with your calendar itself, you connect the calendar in the assistant's own settings; that connection is between you, Google and the assistant's provider, and Ariadne has no part in it.
  • Who can read it. The operator does not read your calendar data. The only exceptions: you explicitly ask us to look at specific data to fix a problem you reported; it is necessary for security (for example, investigating abuse); or the law requires it.
  • How you remove it. "Disconnect" in Settings → Calendar withdraws Ariadne's access at Google and deletes the token, the imported events, your list of calendars and any changes still waiting to be written; copies in automatic backups expire as described in section 8. The Activities you planned or logged stay — they are your own records — including the note that one was made from a calendar event. You choose whether the "Ariadne" calendar is removed from your Google account. You can also withdraw the permission in your Google account at myaccount.google.com/permissions.

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

  • Google user data is used only to provide the features described above, which you see in Ariadne.
  • It is never sold, never used for advertising, and never passed to data brokers or other resellers.
  • It is never used to create, train or improve an AI or machine-learning model. Ariadne has no AI of its own.
  • People do not read it, except in the three cases named above.

5. Your own AI assistant (optional)

Ariadne has no AI inside it. You may connect your own AI assistant (for example Claude or ChatGPT) with a personal access token. The assistant then reads data from your workspace when you ask it to, and can make a small number of limited changes — for example add a note or plan an Activity. What it reads is processed by the provider of that assistant under its terms and privacy policy, which you accepted with that provider. We recommend switching off the use of your conversations for model training in the assistant's own settings. Ariadne makes no automated decisions about you.

6. Why Ariadne may process your data

  • To sign you in, check your access, record your acceptance of the terms and provide your workspace under the terms of use — Art. 6(1)(b) GDPR. A Google account on the access list is necessary: without it we cannot give you access. Everything else is optional.
  • To run it securely (server logs, the AI access log) — Art. 6(1)(f) GDPR, our legitimate interest in a safe and working service.
  • Your calendar — your consent, Art. 6(1)(a) GDPR. You withdraw it at any time by disconnecting the calendar; what was processed before stays lawful, and Ariadne works without a calendar.

7. Where your data is and who processes it for us

The application and the database run in Frankfurt, Germany. We use these providers, which process data on our instructions under their data-processing agreements:

  • Google Cloud (Cloud Run, Frankfurt, europe-west3) — runs the application and keeps its server logs. Data-processing agreement.
  • TiDB Cloud by PingCAP (on AWS, Frankfurt, eu-central-1) — the database, where your workspace is stored. Data-processing agreement.
  • Cloudflare — the network entry point: it receives every request, protects against attacks and passes the request on to the application. It processes the traffic and technical data such as IP addresses; your workspace is not stored there. Data-processing agreement.

These are international companies: technical processing, server logs and their support may be handled outside the European Economic Area. For those cases the agreements linked above contain the safeguards — the EU–US Data Privacy Framework or the EU standard contractual clauses. You can ask us for a copy.

8. How long data is kept

  • Your workspace: for as long as you have access. After your access ends it is deleted from the live database within 30 days; copies in the database provider's automatic backups expire after at most 30 further days.
  • Calendar data: until you disconnect the calendar (section 4).
  • Your session: until you sign out, or 30 days without use.
  • Server logs: 30 days. The AI access log: 90 days; older entries are removed the next time an assistant makes a request.
  • You can export the content of your workspace at any time in Settings → Data, and you can ask us to delete it at any time. The export leaves out what belongs to sign-in and security — your account and sessions, your acceptance of the terms, access tokens — and imported calendar events. To receive that data, write to us.

9. Your rights

You have the right to access, correct, delete and receive your data, to restrict its processing and to object to it (Art. 15–21 GDPR), and to withdraw a consent you gave. Write to the email address in the Impressum. You may also complain to a data protection authority — for the operator this is the Bavarian State Office for Data Protection Supervision (BayLDA).

10. Cookies

Ariadne sets one cookie, after you sign in: the session cookie that keeps you signed in. It is technically necessary. This public website sets no cookies at all.

11. Changes to this policy

We change this policy when what Ariadne does with data changes; the version date at the top changes with it. Before Ariadne uses your Google user data in a new way, we tell you and ask for your consent again.