Privacy policy
This policy describes the personal-data processing Action Flow actually performs. It complements the terms of use.
Controller
Action Flow is published by Traindy, 86 rue Damrémont, 75018 Paris, France. Traindy is the controller for platform accounts. For participants, support contacts and pedagogical email recipients, the customer organisation is the controller and Traindy acts as processor (Article 28).
Contact
To exercise your rights or ask a question about this policy: privacy@traindy.io.
People we process
Platform users (trainers, organisation admins, app admins); people and participants in a training session; support-network contacts (manager, peer); transactional email recipients; product-update marketing contacts; organisation DPO contacts.
Processing
- User account: identity, email, sign-in method, language and timezone. Legal basis: contract (acceptance of the terms and this policy). The terms-acceptance timestamp is kept after anonymization as proof (Article 7.1).
- Pedagogy: identity, email, optional phone, external id, activity answers, implementation intention, transfer profile, end-of-session review (Likert scores and free-text), pedagogical notes written by the team (free text, visible on the Audit tab; optional inclusion in the sponsor report), completion proofs, scores. Legal basis: the contract between the customer organisation and Traindy, performed by the trainer.
- Product updates and onboarding tips: email, first name, last name, organisation name, only if the email is verified, the account is not suspended, and the profile toggle is on. The list is synced to Mailtrap. You can opt out at any time from your profile.
- Organisation DPO contact: email, organisation name, only if the organisation has filled in the contact. The list is synced to Mailtrap. You can change it at any time from the organisation settings.
- Support network: a contact is reached only after a consent request. A refusal, expiry or withdrawal purges the contact. Legal basis: consent.
- Transactional email (activities, visio, consent, alerts, billing): address, name, subject, delivery metadata. Legal basis: contract or legitimate interest (pedagogical digests).
- Billing: organisation name, admin email, VAT, Stripe customer id, consumed credits. Legal basis: contract and accounting duties. Card payments are handled by Stripe; Action Flow does not store card numbers. The Stripe customer is not deleted when an organisation is removed: it is kept for about 10 years.
- AI flow generation: text extracted from documents you upload (PDF, DOCX, PPTX, images) is sent to an AI provider (OpenAI by default). Do not upload participant lists or other personal data. Legal basis: legitimate interest / pre-contractual steps at your request. See also the notice shown before send.
- Visio and calendar: optional connection (Google or Microsoft) to create, update, and cancel visios on a calendar you choose. Google user data is described in the Google user data section. Legal basis: the trainer’s consent.
- Quality tracking (KPIs, Excel / PDF exports, activity report for the sponsor): scores, technical ids, and where applicable review quotes (first name) and shared notes (trainer name). Anonymized people are excluded from exports. Legal basis: legitimate interest and, where applicable, training-evidence duties.
- Technical logs needed to operate and secure the service. Legal basis: legitimate interest.
- Marketing attribution: a first-party cookie (af_utm) may store UTM parameters from a guest visitorʼs first click (source, medium, campaign, content, term) for 30 days, then attach them to the organization created at sign-up. Legal basis: legitimate interest.
Retention
Training sessions: 3 years after the end date, then purge (activity emails, proofs, support contacts, pedagogical notes, anonymization or deletion of the person if they are no longer active elsewhere). The training catalogue is never deleted by this job. User account: anonymization on request rather than a hard delete, so the history we still need (credits, files, audit) survives. The terms-acceptance timestamp is kept as proof. Language, timezone and appearance are reset to defaults. Invitations addressed to the account email are deleted. Technical events (AI usage, email) are kept for as long as needed to operate the service. Credit-consumption proofs are detached from the session and kept for accounting. The Stripe customer (id, billing email, organisation name) and billing records are kept for about 10 years to meet French accounting duties, including after an organisation is deleted.
Processors
Stripe (payments); Mailtrap (email delivery and, when enabled, the marketing list); OVH object storage (France) for files and proofs; OpenAI or another configured AI provider for flow generation; Google, Microsoft and LinkedIn for sign-in and, where used, calendars. On Stripe, the customer and billing records are kept for about 10 years (accounting duties). Retention of Google user data held by Action Flow is described in the Google user data section. Copies that remain in the user’s Google account are controlled by that account.
Google user data
Action Flow accesses Google account data in two separate cases, each with its own consent. The five points below state what is accessed, why, with whom it is shared, how it is protected, and how long it is kept.
Google user data we access
Our application accesses the Google user data you authorize, including the categories below, and no other Google user data.
Sign-in with Google. Data read: Google account identifier, email address, given name, family name, and OAuth tokens. Action Flow uses this Google user data to create or sign in to the Action Flow account, prefill identity, confirm the email, and re-confirm identity. This consent is not used to read mail, files, contacts, or calendar.
Google Calendar, if you connect it. Data read: the connected Google account email, the list of calendars you own (identifier, name, primary flag), OAuth tokens, and, only for events Action Flow created, the event identifier and the Google Meet link. Action Flow does not read your other appointments. Action Flow uses this Google user data to let you pick a calendar, then create, update, and delete visios scheduled in the application (title, time, timezone, link back to the session, description: organisation, training, session, participant display names, agenda). Participants are not added as Google attendees; invitations are sent by Action Flow.
How we use Google user data
We use your Google user data only to provide and improve the user-facing features you request in the application, such as signing in and, if you connect it, managing visios on a calendar you choose. This data is not used for any other purpose. Google sign-in: to create or open your Action Flow account, prefill your identity (given name, family name), confirm your email address, and re-confirm your identity. Google Calendar: to list the calendars you own so you can choose one, then to create, update, and delete on that calendar the visios you schedule in Action Flow (title, time, timezone, link to the session, description). Action Flow does not use Google user data for advertising, selling it to third parties, or to develop, improve, or train non-personalized artificial intelligence or machine-learning models. Google Workspace APIs are not used to develop, improve, or train non-personalized AI or ML models.
Sharing of Google user data
We do not transfer or disclose your Google user data to third parties for purposes other than the ones provided in this policy. We do not sell this data, we do not use it for advertising, and we do not send it to the AI provider. OAuth tokens and the Google account identifier are not disclosed to other users or other applications. The email obtained from Google becomes the account email: it may appear in transactional email (Mailtrap) and, if you turn it on, in product updates. You may share one specific calendar with your organisation: members can then schedule visios on it, without access to the tokens or to your other calendars. Traindy administrators do not read your calendar contents. For the security review of a share you turned on, they see only the calendar name, the account email, and the owner name. The Meet link is shown in the application and emailed to the trainer and the session participants. Action Flow’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Sensitive data protection
Security procedures are in place to protect the confidentiality of Google user data. We use encryption to protect this information. Data exchanged between your browser, Action Flow, and Google is encrypted in transit (TLS). OAuth tokens are encrypted at rest. Access is limited to the features you request: sign-in and calendar use separate OAuth clients, calendar connection uses PKCE, tokens are not written to logs, only calendars you own are listed, and sharing a calendar with your organisation stays off until you turn it on.
Retention and deletion of Google user data
We retain Google user data for the length of time needed to fulfill the purposes outlined in this privacy policy, unless a longer retention period is required or permitted by law. When that period expires, we delete it. You may request for your Google user data to be deleted by writing to privacy@traindy.io, by disconnecting the calendar, or by deleting your account. Google sign-in data (identifier, tokens) is kept for the life of the account, then deleted on anonymization; the token is revoked at Google. Calendar data (account email, calendar names and identifiers, tokens, shares) is kept only while the calendar stays connected. Disconnecting deletes it immediately and revokes the token; events already created remain in your Google Calendar, where you can delete them. If the calendar is still connected when the account is deleted, upcoming visios are cancelled at Google before that revocation. Cancelling a visio or deleting the session deletes the corresponding Google event. The Meet link stored on the session follows session retention (3 years after the end date, then purge), or is removed sooner if the visio is cancelled.
Your rights
You can access and rectify your data from your profile (account) or the participant / support space. Deleting an account anonymizes your row. A participant may leave a session; their identity is then anonymized if they have no other active participation. For a consolidated access, portability or objection request, write to privacy@traindy.io. You may also lodge a complaint with the CNIL.
Transfers outside the EU
Some processors (payments, sign-in, AI) may process data outside the EU. Those transfers rely on the safeguards required by applicable law. File storage is in France.
Changes
This policy may be updated to match the product. The date at the top of the page prevails. Material changes will be signalled to signed-in users when reasonable.