Personal data

Privacy notice

Last updated: 14 October 2026. This notice covers this website, customer accounts, billing, pilot enquiries and support contact.

Who is responsible?

HERBRETEAU Nicolas Frédéric — Entrepreneur individuel, trading as XYNTHERA AI, 2 COTE CARRAU, 65150 MONTEGUT, France. Contact: herbreteaunicolas1@gmail.com.

Pilot enquiries

We use your organisation, email, selected plan, optional country and workflow description to assess your request and contact you about that pilot. The form records your consent to this contact. Required fields are marked with an asterisk; without them the request cannot be processed. There is no automatic marketing subscription.

The form sends these details only when you submit it. Do not include identity documents, payment details, credentials or secrets. Requests are stored in the Xynthera AI backend provided through Supabase; the project database is located in the Paris region.

Customer accounts and billing

For email-authenticated accounts, we use your verified email, business name, optional business address, country and professional-use declaration to provide your account and the service you request. New self-service purchases use the prepaid budget route described below; these email account and subscription sections concern previously accepted subscriptions. Supabase Auth processes sign-in credentials and email confirmation. A verified user is linked to their own account; a contact-form email does not establish account ownership.

If you choose to start an available subscription, the backend transmits the business profile and verified billing email to Stripe to prepare checkout and associate payment with your account. Payment details are entered on the provider’s hosted checkout, not in the public contact form. For Managed Payments, the checkout identifies the seller through Link and the applicable payment terms. Payment status, subscription identifiers and paid access dates are kept to provide and administer the subscription. The provider’s privacy information also applies to its own processing.

Account and subscription processing is necessary to take steps at your request and perform the service contract. Security checks and restricted technical logs protect accounts and the service; invoicing records may be retained to meet applicable legal obligations. API keys are displayed once and only their hashes are stored in the API database. Never send a password or API key in a support request.

New prepaid API budgets

For purchases from €10 to €10,000 including applicable taxes, Xynthera processes the declared billing country, amount, professional-use and terms acceptance, acquisition channel and payment/order identifiers. Stripe collects payment contact and card information in hosted checkout. The API generates a private recovery capability; only its hash is stored by the ledger. Your browser temporarily keeps the capability in session storage and lets you download it. The code is also your Bearer API credential; never send it to support or put it in a URL.

The prepaid service stores neither submitted documents nor returned reports or signatures. Download and retain every result yourself. Limited request identifiers, hashes and calculation metadata support replay for 30 days; this is not report retention or credit expiry. Accounting, payment and anti-double-debit metadata have their own necessary retention. Provider operational logs and payment records follow their own policies. There is no automatic email delivery of your private capability or reports. If your saved code is lost, contact support with your payment reference before paying again; an email address alone cannot authorise access.

Previously accepted guest subscriptions

Where guest checkout is offered, we process your declared business name, country, professional-use declaration, email and plan to prepare the requested subscription. The email can identify the payment contact but is not a verified sign-in identity. Checkout supplies payment information; its paid invoice country is checked against the configured list of covered billing countries before API access is granted.

Your browser generates a secret recovery code. The application stores it in session storage where available and lets you save your own recovery file. The backend stores a hash of that code, not its readable value. Possession of the code authorises guest subscription and API-key controls; an email-only request cannot take over the account. Do not share the code or recovery file. A downloaded file stays under your control and is not uploaded to this website.

Guest subscription identifiers, plan, payment state, access period and necessary security records are processed to perform and administer the requested service. An invoiced country outside the covered list requires refusal of access and order reversal under the service conditions. A change between two covered countries is not itself a reason for refusal. The same legal, security and record-keeping limits described for customer accounts apply.

Recipients and service providers

The business operator uses your request to provide a response. The website is hosted through ChatGPT Sites / OpenAI Ireland Ltd. The enquiry backend is provided through Supabase, with this project database in the Paris region (eu-west-3). Technical providers also process data needed for email correspondence. This setup does not guarantee exclusive EU residency for every website, support or infrastructure operation. Website delivery can involve connection metadata such as IP address, request time and technical logs. Providers may use international infrastructure or support operations under their contractual data-protection arrangements.

Anonymous product funnel measurement

On the EffectGuard and SpendTruth pages, the browser can send a minimal milestone to the Xynthera Supabase backend: a random event ID, event name, product, page scope and time. Form values, email, payment credentials, Bearer codes, IP fields, user-agent fields and visitor identifiers are not included in the event table. Website delivery and Supabase infrastructure can still process connection metadata such as IP address, request time and security logs under their own operational policies.

These milestones are indicative and non-authoritative. They measure aggregate page, simulation and purchase-button use and are kept separate from authoritative payment events. Session storage prevents the same browser session from sending the same milestone twice; the backend also deduplicates the random event ID and applies a global ingestion quota. Records are configured for deletion after 90 days through the daily retention job. Measurement remains unavailable until the database verifies that the exact purge job, retention index and quota are active. The application embeds no advertising tracker and sets no marketing cookie.

The account page uses session storage for a temporary one-use email-confirmation verifier. Sign-in tokens and displayed API keys stay in the page’s memory and are cleared on sign-out or navigation; API keys are also hidden after one minute. Your email application and any external website you choose to open have their own policies.

How long are data kept?

Pilot enquiry details are kept while the request is being assessed and discussed, then deleted if no business relationship is established. If a pilot proceeds, necessary correspondence becomes part of the customer record and is handled for that relationship and any applicable record-keeping obligations. You may ask us to withdraw your request or erase information sooner.

Previously accepted assurance subscriptions may retain technical receipts and Replay reports according to their existing terms; that retention does not apply to new prepaid reports. It does not mean that contact enquiries or invoices are automatically deleted after 7 days. Technical provider logs follow the relevant service's operational and security retention settings.

Your rights

Where applicable, you can request access, correction, erasure, restriction or portability of your personal data, and withdraw consent for pilot contact at any time without affecting earlier lawful processing. Contact the address above, identifying the email used for your request. You can also raise a complaint with the French data-protection authority, the CNIL.

Account records

Account and subscription information is kept for the active customer relationship and any applicable record-keeping, security or dispute-handling obligations. A deletion request is reviewed against those obligations; this page does not promise that financial records or provider logs are deleted immediately. Contact us to request account closure or correction of a business profile.

Before a production integration

The data categories and respective responsibilities for any customer integration must be agreed before activation. This notice is not a data-processing agreement for end-user identity data.

Existing subscription Workbench consistency reports

Workbench retains tenant/request identifiers, an input hash and the signed analysis report for seven days. It does not retain the original supplied OpenAPI document, offer or event body. Reports can contain submitted endpoint names and findings; remove sensitive identifiers before calling. This follows the same service purpose and contact rights described above.

Existing subscription Agent Action controls

Agent policies are retained while configured. Only the hash of the separate management key is stored. Approval tokens are hashed and their records are deleted one day after expiration. Budget reservation and commit metadata are retained for the current and previous two UTC months to preserve budget accounting. Signed control reports are retained seven days; original action parameters are not retained. Opaque identifiers and derived amounts in reports and ledger records remain customer data.