Data processing agreement
This version is being reviewed by our lawyer and may still change before launch. Text in [brackets] is still to be settled.
1. Parties and roles
This agreement is between:
- the Customer that owns a Website under the terms of sale ("the Club"), the controller; and
- Three Hammers Exploration Corp., SASU with a share capital of €1,000, RCS Saint-Malo 132 498 247, head office at 25 Rue du Marché, 35350 La Gouesnière, France, trade name Verticale ("Verticale"), the processor.
It applies whenever Verticale processes personal data on the Club's behalf to provide the services: from the first content read or uploaded for a Website, published or not.
It doesn't cover the personal data of the people who use Verticale's app (the Club's team), or the Club's billing details. Verticale processes those as a controller, under its privacy policy at getverticale.com/privacy.
Words such as "personal data", "processing" and "personal data breach" have the meaning the GDPR gives them, and include "personal information" under Quebec and Canadian law.
2. Processing on the Club's instructions
Verticale processes personal data only:
- to provide the services;
- on the Club's documented instructions, which are the terms of sale, this agreement, the Club's settings in the app and its written requests;
- or where the law requires it, in which case Verticale tells the Club first, unless the law forbids it.
If Verticale believes an instruction breaks data protection law, it tells the Club.
Verticale doesn't sell the Club's personal data, use it for advertising, combine it with other customers' data, or use it to train AI models.
3. Details of the processing
Annex 1 sets them out: the subject matter, duration, nature and purpose, the types of personal data, and the people concerned.
4. Confidentiality and access
Only people who need access to provide the services may process the data, and they're bound by confidentiality.
Verticale's team (its super admins) can read any Website, read only, to help its owners. It edits a Website only during a Done-for-you setup the Club bought, and only that Website, or when the Club asks. Each opening during a setup is recorded.
5. Security
Verticale applies the technical and organisational measures in Annex 2, and adapts them to the risk.
6. Subprocessors
- General authorisation. The Club allows Verticale to use the subprocessors in Annex 3.
- Changes. Verticale tells the Club's owners by email at least 30 days before adding or replacing one. The Club may object on reasonable grounds; if no solution is found, it may end the affected service.
- Same obligations. Verticale imposes the same data protection obligations on its subprocessors, and remains responsible for them.
- Services the Club chooses. Services the Club chooses to link to or show on its Website, such as its booking provider (Chronogolf, for example), a YouTube or Vimeo video, app stores or social networks, aren't Verticale's subprocessors. Visitors' browsers reach them directly, under their own terms. For visitors in the EU, the EEA and the UK, the Chronogolf widget and the video don't load at all.
7. Transfers outside the EU, the EEA, the UK and Quebec
Some subprocessors process data in the United States or on a global network (Annex 3). Verticale ensures an appropriate safeguard for each transfer: [for each subprocessor: the EU–US Data Privacy Framework, the EU standard contractual clauses, and the UK addendum].
For Clubs in Quebec, Verticale provides the information the Club needs for its privacy impact assessment (Law 25, s. 17).
8. Helping the Club
Taking into account the nature of the processing, Verticale helps the Club to:
- answer requests from the people concerned (access, correction, deletion, objection). The visitor counts keep nothing that identifies a visitor, and contact-form messages aren't kept, so such a request usually has nothing to match;
- carry out impact assessments and consult an authority where required;
- meet its security obligations.
9. Personal data breaches
Verticale notifies the Club's owners of any personal data breach affecting the Club's data without undue delay, and at the latest within 48 hours of becoming aware of it.
The notice includes what Verticale knows then: the nature of the breach, the data and people concerned, the likely consequences, and the measures taken or proposed. Verticale completes it as it learns more.
10. End of the processing
When the Club deletes a Website, or the Workspace or account that holds it:
- the Website goes offline at once;
- Verticale keeps it for 30 days, then erases it permanently: its drafts, published versions, images and uploads, module data, what was read for it, the text of its AI requests, its visitor counts and its domain connection;
- the backups keep erased data a little longer: the database's history (Cloudflare D1 Time Travel) keeps earlier states for 30 days, and the nightly copy of stored files keeps a deleted file for 30 days. Erased data leaves both within 31 days of the erasure.
What remains names no person: the Website's name and vertical, its plan, its dates, how many generations and AI changes it had, and what its AI requests cost Verticale.
A Website started without an account is erased after 30 days without a visit.
Before deleting, the Club can [export: no tool yet, to decide].
11. Audits
Verticale makes available the information needed to show that it meets this agreement, starting with this document and its annexes.
It allows reasonable audits, at most once a year, with 30 days' notice, at the Club's cost, and without access to other customers' data. Subprocessors' own certifications (such as Cloudflare's SOC 2 and ISO 27001) count as evidence for their part.
12. Duration and precedence
This agreement lasts as long as Verticale processes personal data for the Club. On personal data, it prevails over the rest of the terms of sale.
Annex 1 — Details of the processing
A. Published site and its visitor counts
- Purpose.
- Hosting and serving the Club's Published site.
- Counting its visitors (how many, where they come from, which buttons they use) and showing the totals to the Club.
- Protecting the site against abuse.
- People concerned. Visitors of the Published site.
- Personal data.
- The visitor's IP address and browser description (User-Agent). They're used only for the length of a request: to filter robots and to compute a visitor code. They're never stored.
- The visitor code: a keyed hash of the IP address, the User-Agent and the Website, under a random key that changes every day in the Club's timezone and is deleted when that day ends. It's kept with each event.
- For each page view: the time, the channel (search, social, paid, email, referral or direct) and the Club's local day.
- The channel comes from the referring site's name, which isn't kept.
- Outside the EU, the EEA and the UK, it also uses the campaign tags
utm_sourceandutm_medium, which aren't kept either.
- For each click on a button or a link: the kind of action (booking, phone, email, directions, social, app, contact form, other link or on-page), whether it was the header button, and the section of the page.
- For a visit to an address that doesn't exist on the Website: that address, without anything after a question mark.
- Counters that limit how many events one network sends, under a hashed key, for about a day.
- Not collected. No cookies, nothing stored on the visitor's device (except their own choice to turn counting off), no full URLs, no device, browser, country or city reports, and no cross-site tracking. A browser sending Global Privacy Control isn't counted.
- Retention.
- Individual events: 48 hours at most.
- The daily key: until the end of its day.
- Daily totals, which aren't personal data: 25 months.
- Operations. Collection, filtering, pseudonymisation, storage, aggregation, deletion.
B. The Club's content
- Purpose. Building, generating, editing and publishing the Club's Website, including with AI.
- People concerned. People who appear in the content the Club provides or has Verticale read, such as staff, coaches and contacts.
- Personal data. Names, roles, professional emails and phone numbers, and photos, as found in:
- the Club's current website, which Verticale reads (public pages only, following its robots.txt);
- the Club's uploads, answers, edits and module data (events, prices, menus, gallery, apps, map address);
- the requests the Club's team makes to the AI.
- AI generation. For a draft or a change, Verticale sends OpenAI the Club's answers, the text read from its website, a few of its photos and the request, asking OpenAI not to store the results. OpenAI doesn't train its models on this data and keeps it for at most 30 days to detect abuse, unless the law requires otherwise.
- Retention. As long as the Website exists, then 30 days after it's deleted (section 10). Verticale keeps the text of each AI request, without its photos, to look into problems; it goes with the Website.
- Operations. Reading the Club's public website, storage, AI generation and editing, publication.
C. The contact form
- Purpose. Passing visitors' messages to the Club, when the Club's Website has a contact form.
- People concerned. Visitors who write to the Club through the form.
- Personal data. Name, email address, phone number if given, and the message.
- How. Each message is emailed through Cloudflare's email service to the address the Club confirmed, with the visitor as Reply-To. Verticale keeps no copy.
- Retention. None for the message. A counter that limits messages per visitor is kept for about a day, under the daily visitor code.
- Operations. Collection, filtering against spam, transmission.
D. The map
- Purpose. Showing where the Club is, when its Website has a map.
- People concerned. Visitors who see the map.
- Personal data. The visitor's browser asks Google for the map image, so Google receives the visitor's IP address and browser details. Verticale only signs the image's address; it receives and keeps nothing. In the EU, the EEA and the UK, the image loads only after the visitor taps "Show the map".
- Retention. None at Verticale. Google's own retention applies.
Annex 2 — Technical and organisational measures
- Encryption. HTTPS everywhere in transit; data at rest encrypted in Cloudflare D1 and R2.
- Backups. 30 days of database history (Cloudflare D1 Time Travel), and a nightly copy of stored files in a second Cloudflare R2 bucket in the same region, which keeps a deleted file for 30 days.
- Isolation.
- Published sites are served from their own domain and their own Worker, apart from the app, so they share no origin or cookie with Verticale or with other Clubs.
- Generated pages contain no model-written scripts.
- A strict content security policy limits what they can load. Third-party content (the booking widget, videos, maps) loads only on the Website's own address, never in the Studio or shared previews.
- Data minimisation in the visitor counts.
- No IP addresses stored.
- Daily keys deleted.
- Individual events deleted after 48 hours at most.
- Robot and data-centre traffic filtered.
- Campaign tags ignored for visitors in the EU, the EEA and the UK.
- Access control.
- Workspace roles: owner, editor, viewer. Every request is authorised against the Workspace's memberships.
- Passwords stored only as hashes; the sign-in cookie can't be read by scripts; emailed links expire.
- Verticale's super admins sign in with a second step. Their access to a Club's Website is read only, except during a Done-for-you setup for that Website, when each opening is recorded.
- Secrets are kept in Cloudflare's secret store, never in code.
- Protection against abuse. Bot checks before free generation and website readings; limits per network and per account on sign-in, readings, generation, emails and contact-form messages.
- Deletion. Deleting a Website takes it offline at once; 30 days later its database rows, its stored files and its workflow history are erased, and the erasure is retried until it succeeds.
- Recovery. The database's history (Cloudflare D1 Time Travel) allows restoring it to any minute of the last 30 days.
- Accountability.
- Product and architecture decisions are recorded with their dates.
- Security-sensitive changes are tested automatically before release.
- Security audits have been run on the product (first in October 2026).
[To complete: logging and monitoring, staff confidentiality undertakings, incident response.]
Annex 3 — Subprocessors
| Subprocessor | Service | Data | Location |
|---|---|---|---|
| Cloudflare, Inc. | Hosting of the app and Published sites, database (D1), file storage (R2), email delivery (including contact-form messages), bot checks, security | All of Annex 1 except D | United States (database and storage in Eastern North America); global network for serving pages |
| OpenAI (OpenAI, L.L.C. [or OpenAI Ireland Ltd, depending on the contracting entity]) | Writing and changing Websites with AI | Annex 1 B: personal data in the Club's content and requests, never visitor data | United States |
| Google LLC (Google Maps Platform) | Map images on Published sites that show a map | Annex 1 D: visitors' IP address and browser details, sent by their browser | United States [and Google's global network] |
| Stripe (Stripe Payments Europe Ltd. / Stripe, Inc.) | Payments, invoices and tax | The Club's billing details, for which Verticale is the controller; never visitor data | EU, United States |
Verticale also uses Google's PageSpeed Insights and Chrome UX Report to measure the speed of the Club's current and published website. Only the website's public address is sent, so no personal data is processed there.
Last updated 18 November 2026