Legal information

Privacy policy.

What data Prestafy processes, why, with which providers, how long it is kept and how to exercise your rights.

Last updated: October 2026

This Privacy policy explains how data is processed when you use:

  • the prestafy.fr website (public site),
  • the Prestafy merchant area (the dashboard used to manage your mobile app),
  • the Prestafy (demo) mobile app (iOS/Android), connected only to demo.prestafy.fr.

1) Data controller

The data controller is:

  • PRESTAFY, a Société par Actions Simplifiée with share capital of €1,000,
  • Registered office: 39 Rue de Jouy, 77970 Bannost-Villegagnon, France,
  • Melun trade register no. 105 356 794,
  • Contact for any question about personal data: contact@prestafy.fr.

2) Data processed

2.1 The prestafy.fr website

We may process:

  • your email address and the content of your message if you contact us,
  • technical data (logs) needed for security and operation,
  • visit statistics from Google Analytics.

2.2 The Prestafy (demo) app

The app is a demo connected only to demo.prestafy.fr (demonstration store).
We may process:

  • technical data (for example app version, OS version, errors) for operation and diagnostics,
  • push notification identifiers (token) if you enable notifications,
  • usage statistics where enabled (Firebase Analytics),
  • demo data shown in the app (for example orders and products from the demonstration store).
    Please avoid entering real personal information in the demo environment.

3) Why (purposes)

  • provide the service (website + demo app),
  • send notifications where enabled,
  • improve and secure the service (maintenance, performance, bug fixing),
  • answer requests (support and contact),
  • suggest settings and an app home page suited to your shop (artificial intelligence features, section 6b).

4) Legal bases

Depending on the case, processing relies on:

  • the performance of pre-contractual measures or of the contract (providing the service, answering your requests),
  • your consent (push notifications, usage statistics where enabled),
  • Prestafy's legitimate interest (security, fraud prevention, service improvement),
  • compliance with a legal obligation where applicable.

5) Service providers (sharing)

We use the technical providers we need:

  • Hostinger International Ltd (Cyprus): website hosting,
  • Firebase (Google): analytics/diagnostics and/or notifications (where enabled),
  • OneSignal: notifications (where enabled),
  • Google (reCAPTCHA): protection of the website forms against automated submissions,
  • Stripe: payment and management of merchant area subscriptions; your card details are entered and kept at Stripe,
  • Brevo (France): emails about your account and, if you agreed to them, newsletters,
  • Codemagic: building and signing your mobile app, from the settings and files you upload,
  • Anthropic (United States): artificial intelligence features of the merchant area (section 6b).

Some of these providers may transfer data outside the European Union; where that happens, such transfers are covered by appropriate safeguards (European Commission standard contractual clauses).

We do not sell your data.

6) Your Google account data ("Sign in with Google" and "Connect and provision with Google" features)

In the merchant area, you can connect your Google account to sign in (SSO) and, if you wish, to let Prestafy automatically set up the push notification infrastructure for your app ("Connect and provision with Google"). This section describes precisely how the Google data concerned is processed.

6.1 Data we access

  • your basic Google identity: name, email address, avatar (identifying the connected account);
  • with your explicit consent (Google authorisation screen), through the Google Cloud and Firebase APIs: the list of your Firebase / Google Cloud projects (identifiers and names) so that you can choose one or create a dedicated project, then, on that project only: the registration of your iOS and Android apps, their Firebase configuration files (google-services.json, GoogleService-Info.plist) and a service account dedicated to notifications ("prestafy-push@…") together with its key.

6.2 Use

This data is used exclusively to set up, at your request, the push notifications of your mobile app. No other purpose: no advertising, no profiling, no analysis of your other Google resources.

6.3 Sharing and transfer

Data from your Google account is never sold or transferred to third parties, with two exceptions, both triggered by you: the Firebase configuration files are embedded in the build of your mobile app (that is their purpose); and if you enable the OneSignal notification provider, the service account key is sent to your own OneSignal account so that notifications can be delivered.

6.4 Protection

Google access tokens and configuration files are encrypted at rest in our databases, transmitted exclusively over TLS, and accessible only to the processes required for the feature.

6.5 Retention, revocation and deletion

  • retained for as long as your merchant account is active;
  • you can disconnect at any time from your dashboard (the token is revoked) — resources already created (Firebase project, service account) remain your property, on your Google account;
  • revocation is also possible from myaccount.google.com/permissions;
  • deletion on request (contact@prestafy.fr) and when your account is deleted.

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

6a) AI assistants connected by the merchant

In the merchant area, you can connect an artificial intelligence assistant of your choice (for example Claude by Anthropic, ChatGPT by OpenAI or Le Chat by Mistral AI) to your Prestafy account, through the MCP protocol (Model Context Protocol). This section describes the data involved.

6a.1 Who does what

The assistant you choose is provided by its publisher, which acts as an independent data controller for the data you entrust to it in your conversations, including the information Prestafy sends it at your request. Its own terms and privacy policy apply: we invite you to read them. Prestafy remains responsible for the processing it carries out to run the connection, described below.

6a.2 What Prestafy sends to the assistant

Only what the assistant asks for to answer your conversation, and only for the apps you approved:

  • your app's status: name, status, remaining steps, targeted platforms, status of your Apple and Google accounts, services used (Firebase, OneSignal) and progress of the Firebase setup, last known result of the checks on your store credentials, your store's connection, as well as your account's plan and whether it is connected to Google;
  • your content and settings: the Studio draft and published version (home screen, menu, navigation bar, appearance), your notification campaigns, segments and automations and your announcements shown when the app opens, texts included, and your sending limits for marketing notifications;
  • your store's catalogue, read live: products, categories, brands, pages and languages;
  • the list of your Prestafy media library: name, type, dimensions and collection of each file, never the file itself;
  • your app's statistics, as your Prestafy dashboard shows them: revenue and orders placed in the app, average basket, mobile share, installs, store ratings and other indicators, always as totals, for a period compared with the previous one or day by day; never an individual order, a customer, a search term or the text of a review;
  • results, always as totals and never at the level of a person: those of your notifications (sends accepted by the provider, opens, orders and revenue recorded after an open, your customers' acceptance of notifications), of your automations and of your announcements (displays, button taps, dismissals), and the estimated audience of your campaigns and saved segments;
  • a few technical identifiers, to guide you through your settings: your app's identifier on the stores, those of your Firebase project, your Google Cloud project, your Google Play developer account and your Google Analytics property (in the links to their consoles), the version of the Prestafy module installed on your store and your store's domain.

At your request, the assistant can also have a store credential checked again with Apple or Google: Prestafy uses the credential you uploaded, without ever sending it to the assistant.

Prestafy never sends the assistant any data about your end customers (name, email address, named order, device identifier), nor any key, password, service account file or access token.

Do not entrust any secret to the assistant: what you write in the conversation goes to its publisher. If a request from the assistant to Prestafy contains what looks like a key, a password or a token, Prestafy refuses it and only records in its log where it was and what kind of secret it recognised, never the value. This check relies on known formats: it prevents common mistakes, it cannot recognise everything.

6a.3 Access, duration and revocation

You approve access on Prestafy, with your account, choosing the apps concerned. Each approval is separate: giving a new one does not widen what a token already issued allows. The assistant receives an access token valid for one hour, renewable with a refresh token valid for thirty days, itself replaced each time it is used. A refresh token presented a second time revokes the whole approval it comes from: it is the sign that it has been copied.

From Prestafy (My account, then Connected assistants), you can at any time:

  • remove an app from an access: from its next request, the assistant can no longer read or prepare anything for this app;
  • revoke the whole access: it takes effect immediately and all the assistant's tokens stop working.

Removing the connector from the assistant does not notify Prestafy: the tokens already issued remain valid until they expire, at most thirty days after they were last used. To cut access straight away, revoke it from Prestafy. An access the assistant no longer uses expires on its own thirty days after it was last used.

6a.4 What Prestafy keeps, and for how long

  • the access: the assistant's name and domain, the apps and permissions granted, the dates of approval, of last use and, where applicable, of revocation. Kept while it is in use; deleted at the latest 90 days after its revocation, or one week after its last token expires;
  • the tokens: Prestafy only keeps their identifier, permissions and expiry date, never the token itself. A refresh token is deleted at the latest one week after it expires, together with the access token issued alongside it;
  • the log of the assistant's actions: each draft prepared, segment created, automation prepared, changed or removed, and change proposed, with your account, the app and item concerned, the date, the assistant, the tool and the identifier of the token used, never the texts. These entries are kept for 180 days. Security events (a request refused because it contained a secret, a refresh token reused, an app or access removed) and the outcome of proposals on an automation are also kept for 180 days;
  • change proposals on an active automation: a full copy of the automation as it was and as the assistant proposes it (texts, delays, conditions), kept until you apply or dismiss it, or until a new proposal replaces it, then for 180 days;
  • the assistant's mention on what it prepared: "prepared by the assistant" on an automation it created, as long as the automation exists, and its name, its domain and the identifier of the token used in the Studio's version history, like the rest of the app's history.

The content of your drafts, campaigns, announcements and automations is handled like your other content, whether or not it was prepared with the assistant.

When your merchant account is deleted, Prestafy immediately deletes your assistant accesses, their approvals and their tokens, the change proposals, the "prepared by the assistant" mentions and the log of the assistant's actions, including its security events and the outcome of proposals. Prestafy does not keep the content of your conversations with the assistant: they take place at the assistant's publisher, not at Prestafy.

6b) Prestafy's artificial intelligence features

Prestafy uses Anthropic's Claude models for three features of the merchant area. Anthropic then acts as Prestafy's processor. These features are separate from the assistants you connect yourself (section 6a).

6b.1 What is processed

  • Your brand colours: when you enter your shop's address (creating an app, or the "Get started" page of the website), a screenshot of that site's public home page is analysed to suggest your colours.
  • Your app's home page: when the app is created, the visible text of the site's public home page is summarised into a short business profile (sector, customers, tone, key moments of the year, selling points shown on the site). When your shop first connects, this profile, the names of your categories, brands and pages and Prestafy's starter visuals are used to suggest a home page for your app.
  • Translation: the texts of your app that you ask to translate from the Studio.

This processing covers the publicly visible content of your site, including the contact details it shows, and your app's content. Prestafy never adds any data about your end customers, nor any login, password or key.

6b.2 Terms

  • Legal basis: performance of the contract (providing the service).
  • Anthropic processes this data on Prestafy's behalf, in the United States, under its commercial terms, which rule out its use to train its models, and keeps it for a limited period. This transfer outside the European Union is covered by the European Commission standard contractual clauses.
  • Prestafy keeps neither the screenshot nor the site's text. The business profile is kept with your app while your account is active; you can ask for its deletion at contact@prestafy.fr.
  • The suggested home page is a starting point: you edit or replace it freely in the Studio.

7) Retention

  • contact messages: up to 12 months,
  • logs and diagnostics: up to 6 months,
  • notification tokens: for as long as the app is used and/or notifications are enabled (then deleted or disabled).

8) Your choices & deletion

  • Notifications: turn them off in the iOS/Android settings (or in the app).
  • You can delete local data by signing out and/or uninstalling the app.
  • You can request the deletion of the associated technical data (for example the push token): contact@prestafy.fr.

9) Your rights

Under the General Data Protection Regulation (GDPR) and the French Data Protection Act, you have the rights of access, rectification, erasure, objection, restriction and portability of your data.
You can exercise these rights by writing to contact@prestafy.fr.

If, after contacting us, you consider that your rights are not being respected, you may lodge a complaint with the CNIL (the French data protection authority), 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07 — www.cnil.fr.

10) Updates

This policy may change. The update date will be amended if necessary.