TheStakk /legal / privacy

Legal

Privacy policy

Plain language, no hedging. This page says what we collect, why, where it sits and how to make us delete it.

Last updated 24 August 2026 Legal review pending

01

Who we are

Our website is thestakk.com. TheStakk is operated from Sens, France. We are the data controller for the information described in section 02 and the data processor for the content our customers put into the applications.

Legal entity, registration number and registered address: to be supplied. Data protection contact: info@thestakk.com.

02

What we collect

Three categories, nothing else.

  • ·Account data — name, professional email, company, and the plan you are on. You give us this when you sign up.
  • ·Content you submit — the inputs you put into an application and the results it produces. Yours, held on your behalf.
  • ·Technical logs — which application ran, when, how long it took and how many credits it consumed. This is what your invoice and your audit trail are built from.

03

Why we process it

  • ·To run the applications you ask us to run — the contract you signed with us.
  • ·To meter consumption and bill you accurately.
  • ·To keep the service secure, investigate incidents and prevent abuse.
  • ·To answer you when you contact support.

We do not process your data for advertising, profiling or resale. There is no fourth reason.

04

What we never do

These are commitments, not intentions.

  • ·We never use your content to train any model — ours or anyone else’s.
  • ·We never sell, rent or share your data with advertisers or data brokers.
  • ·We never read your content except when you explicitly ask us to help with a specific problem, and only for as long as that takes.
  • ·We never surface credentials in logs, interfaces or exports.

05

Where your data lives

Hosting and processing take place inside the European Union. Your workspace is separated from every other customer at database level, and credentials are held encrypted in an isolated vault.

Exact hosting providers and regions: to be supplied. Where a subprocessor operates outside the EU, the transfer is covered by Standard Contractual Clauses and listed in section 07.

06

How long we keep it

  • ·Account data — for the life of your account, then deleted within 30 days of closure.
  • ·Content you submit — until you delete it, or until account closure. confirm retention window
  • ·Execution logs — retained for billing and audit purposes. confirm retention window
  • ·Backups — rolling, overwritten on a fixed cycle. confirm cycle

You can export your data and execution history at any time, in a machine-readable format, without asking us.

07

Who else touches it

We use a small number of subprocessors — hosting, model providers, payment processing, transactional email. The full current list, with each one’s role and location, is published and versioned: subprocessor list to be published.

Model providers process your inputs to produce a result and are contractually barred from retaining them or training on them. We notify customers before adding or replacing a subprocessor.

One small thing worth naming: if you request a password reset, your IP address is included in the reset email. That is how you can tell whether the request came from you.

08

Your rights

Under the GDPR you can ask us to give you a copy of your data, correct it, delete it, restrict how we use it, or object to a processing activity. You can also ask us to send it to another provider.

Write to info@thestakk.com. We answer within one month, and usually within a few days. If our answer does not satisfy you, you may complain to the CNIL, the French supervisory authority.

One limit applies to erasure: we cannot delete data we are legally required to keep – invoices, and the execution records that back them, for the retention period French accounting law imposes. Everything else goes.

09

Agency workspaces

If you reached an application through an agency, that agency is your point of contact and the controller of your relationship. They decide which applications you can use and what you pay.

We process your content on their instruction and ours never leaves the isolation of your workspace. Agencies can be granted access to a workspace to help you — that access is recorded in the audit trail, and requires your consent.

10

Website visitors

Everything above concerns the applications. Browsing thestakk.com is a separate matter, and a much shorter one.

If you fill in a form to contact us or request access, we keep what you typed and the email address you gave us, so we can reply. That is the whole of it: no account is created, no profile is built, and the message is deleted once the conversation is closed.

We measure page traffic in aggregate to know which pages are read. Those measurements do not identify you and are not linked to any application account.

The website has no comment section, no visitor uploads and no embedded third-party content, so none of the tracking that usually comes with those exists here.

11

Cookies

We use the strict minimum, and every one of them is functional.

Login Two days, or two weeks if you tick “Remember me”. Removed when you log out.
Display preferences One year, so your screen options survive between sessions.
Cookie check A temporary cookie set on the login page to confirm your browser accepts cookies. No personal data, discarded when you close the browser.
Aggregate measurement Page traffic counts that do not identify you individually.

No advertising cookies, no third-party trackers. Full cookie inventory: to be supplied.

12

Changes and contact

When we change this policy in a way that affects you, we tell you by email before it takes effect and keep the previous version available. Minor corrections are dated at the top of this page.

Questions, requests or complaints: info@thestakk.com.

This page is a draft pending legal review.

Every amber badge marks a fact only you can supply — legal entity, hosting providers, retention windows, subprocessor list. Nothing on this page has been invented: the commitments restate what the security documentation already says.