Privacy policy
Tour de Growth records the bare minimum needed to compute your score, hand it back to you through its link, and measure whether the tool works. This page says exactly what, why, for how long, and what you can ask for.
Who is responsible for your data
Tour de Growth is a personal project, built and published by Antoine Berthaud on a non-professional, non-commercial basis. The controller of your data is therefore a natural person, not a company.
For any question about your data, or to exercise the rights described below, write to contact@tourdegrowth.com.
What we record, and why
There is no account. You never have to give your name, your email or your company's name to take the Tour.
- Your fifteen answers and your score
The option chosen at each of the fifteen questions, the five stage scores, the total, the weakest stage, the tone you picked (straight up or roast), the language, and the date. It is what your result page shows, and what lets it be shown again to anyone who has its link.
- Where you came from, if it was a share
If you opened Tour de Growth from someone else's result link, that result's identifier is recorded with yours. It is what lets us measure whether the tool spreads — the viral coefficient — and nothing more: it does not say who shared, only which result.
- The Deep dive, if you take it
The generated recommendations, in both tones and both languages, and the name of the model that wrote them. Your ten context answers and any free text you typed are used to write those recommendations and are not kept afterwards: only whether the free-text field was filled in is retained.
- An ownership token
When your result is created, your browser receives a secret token of which only a fingerprint (a hash) is stored on our side. It is what proves that you, and not anyone you sent the link to, can run the Deep dive on your result.
The legal basis is the performance of the service you request when you start the calculation. For the audience and spread measurement described below, it is our legitimate interest: knowing whether the tool is used and spreads, which is exactly what it exists to demonstrate.
What we don't record
- No account, no email, no name, no company name. If you type one into the Deep dive's free-text field, it is used for the generation and not kept.
- No advertising cookie, no third-party tracker. The only cookie set remembers your language.
- No IP address kept by the application. It is used in memory, for a few minutes, to limit how many requests one connection can send, then forgotten. The host keeps its own technical logs, under its own policy.
- No sale, rental or transfer of your data to anyone.
On your device
Your browser keeps, in its local storage, your answers in progress (so a reload doesn't make you start over), the identifier of the result that may have brought you here, the list of results you created with their ownership token, and the progress of a Deep dive under way. None of it leaves your device other than through the requests described above, and clearing the site's data in your browser clears it entirely — including the ability to run the Deep dive on a result already created.
If you use the growth engine, your browser also keeps, in the same place, the numbers and text you enter there. None of it is sent, to us or to anyone: the only ways out are the files you download and what you copy yourself. Clearing the site's data also clears your engine, unless you saved it to a file.
Audience measurement
Page views and a few events (Tour started, stage finished, result created, share, Deep dive) are counted with GoatCounter, a cookie-free audience measurement service with no individual identifier. It cannot follow you across sites or tell who you are. That is why no consent banner is shown: there is nothing to consent to.
On the growth engine, the only things counted are the page being opened, how you sell as ticked (self-serve, sales-assisted or both), the first number saved in each stage of each engine, a new month being started, a request being copied, the link with your Tour, the slides being opened, exported or copied as text, a file being exported (backup, reminder or template), and the link you came in through — never a number, a status or any text you enter.
Where your data is, and who processes it for us
Your data is hosted in the European Union.
- Google Cloud (Firestore)
The database where results are stored.
- Google (Gemini API)
Only if you take the Deep dive: your twenty-five answers, your score and any free text are sent to it to write your recommendations. Google processes that text to produce the answer and, on its API's paid tier, does not use it to improve its products.
- Vercel
Hosting the site and running its code.
- GoatCounter
The audience measurement described above.
None of these providers receives your data for any purpose other than the one stated, and no third-party application can read the database: its access rules refuse any direct access; only Tour de Growth's server writes to and reads from it.
How long we keep it
- Your result (answers, scores, tone, language, Deep dive recommendations) is kept with no time limit: its link is meant to be shared, and a link that dies months after a share would break the very thing you sent it for. You can ask for it to be deleted at any time (see below).
- The Deep dive's free text and context answers are not kept once the recommendations have been generated.
- Audience measurement data is aggregated and cannot single you out.
Your rights
Under the GDPR, you have the right to access, rectify, erase, port, restrict and object to the processing of your data.
Since there is no account, the only proof that you authored a result is its link: to ask for a result to be deleted or copied, write to contact@tourdegrowth.com with the page's address (https://www.tourdegrowth.com/r/…). We answer within a month.
If you believe your rights are not respected, you can lodge a complaint with the CNIL (the French data protection authority), 3 place de Fontenoy, 75007 Paris, France, or at cnil.fr.
Changes to this document
If this policy changes significantly, the date at the top of this page changes with it. The site's code being public, every change is visible there too.