Privacy

1. What this site does NOT do

No user accounts, no visitor database, no audience-analytics tool (Google Analytics or similar), no advertising, no ad tracker or pixel, no reselling of data. The site is static: almost every page loads with zero request to a third party.

2. The contact form — the site's only personal-data processing

Data controller: the publisher of the GaautGunner site, a private individual acting on a non-professional basis (see the legal notice for the applicable identification regime).

Data processed, exactly matching the form on theContact page:

• Message (required) — up to 5,000 characters.
• Name (optional) — up to 200 characters.
• Email (optional, only if you want a reply) — up to 200 characters, used as the reply-to address if it has a valid email format.

A hidden "honeypot" field exists in the form but is never filled in by a human visitor; if it is, the message is not sent. No other data is collected by this form (no IP address logged by the site, no cookie set on submission).

To keep bots out, the form also goes through Turnstile, a check run by Cloudflare. When the page loads, Cloudflare looks at your IP address and technical signals from your browser to check that the message comes from a person, not a program. The site sends Cloudflare only the token this check produces, gets back a valid-or-not verdict, and keeps nothing from it. This check falls underCloudflare's privacy policy.

Purpose: receiving your message and replying if you left an email. Nothing else — no marketing, no newsletter, no profiling.

Legal basis: the publisher's legitimate interest (GDPR article 6.1.f), strictly limited to receiving and replying to messages voluntarily sent through this form. This basis covers nothing else — no marketing use, no reuse of your details for another purpose. That's also why the form has no "I accept the privacy policy" checkbox: the processing isn't based on your consent, so a checkbox wouldn't carry legal meaning here.

Required vs. optional: only the message is required (the form cannot be submitted empty). Name and email are optional; without an email, your message is still received but no reply can be sent through this channel.

Recipients: the site's publisher (email gaautgooner@gmail.com), and the technical delivery provider Resend (see § 3). No other transmission, no sale or sharing with any third party.

3. Resend — email delivery provider

The form does not send an email directly: the content (name, email, message) is sent to the Resend API, which delivers it to the publisher's inbox. Resend acts here as a processor under GDPR, not as controller of the form's data.

• Entity: Plus Five Five, Inc. (operating the service as Resend), 2261 Market Street #5039, San Francisco, CA 94114, USA.
• Primary processing: in the United States.
• Retention at Resend: message and log data is kept for 30 days while the account is active (Free/Pro/Scale plans), then deleted; on account termination, remaining data is deleted within 90 days.
• Transfers outside the EEA and safeguards: EU and UK Standard Contractual Clauses built into Resend's Data Processing Addendum, and Resend's certification to the EU-U.S. Data Privacy Framework (and its UK extension).
• Resend's own subprocessors: list maintained by Resend atresend.com/legal/subprocessors.

Sources: Resend's Data Processing Addendum and GDPR page (resend.com/legal/dpa,resend.com/security/gdpr), reviewed while writing this page.

4. Cloudflare — hosting

The site is hosted and served by Cloudflare, Inc. (seelegal notice). Like any web host, Cloudflare necessarily processes technical connection data (notably IP addresses) for every request, as part of running its network (serving pages, abuse protection). Cloudflare acts here as a processor; its terms state that transfers outside the EU/UK rely on the EU Standard Contractual Clauses and its participation in the EU-U.S. Data Privacy Framework.

Source: Cloudflare's Customer Data Processing Addendum (cloudflare.com/cloudflare-customer-dpa), reviewed while writing this page.

The exact retention settings for connection logs on the Cloudflare side (duration, level of detail) are configured from the Cloudflare account dashboard: they are not part of the site's code and could not be verified while writing this page.

5. Retention period

Two distinct periods apply, at two different levels:

• At Resend (technical delivery provider, § 3): 30 days of automatic retention for message and log data while the account is active, 90 days at most on termination. This period is set by Resend, not by the site's publisher, and only covers the message's technical passage through its API — not how long it's kept once received.
• At the publisher's end (the gaautgooner@gmail.com inbox and any exchange that follows): a message and any follow-up exchange are kept for12 months at most from the last exchange, then deleted, unless there's a specific reason to keep it longer (an ongoing exchange, a legal obligation). This rule is applied by the publisher directly in their Gmail inbox — it isn't an automatic mechanism of the site, which has no access to that inbox.

6. Your rights

Under GDPR, you have rights of access, rectification, erasure, restriction and objection over data about you processed through the contact form. Thecontact form is the intended way to exercise them.

You can also file a complaint with the French data protection authority (CNIL):cnil.fr/fr/plaintes.

7. Display preference (localStorage)

The site remembers, locally in your browser (localStorage, keygg-theme), which kit you've chosen for the visual theme (home / away / third). This stays on your device, is never sent to the site or a third party, and serves no tracking or advertising purpose — only remembering your display choice for your next visit. It's cleared by clearing your browser's site data.

8. Cookies

This site sets no audience-measurement, advertising or tracking cookie. No cookie-consent banner is shown, because there's nothing to consent to. The only browser-side storage is the kit preference described in § 7, which falls outside cookie-consent scope (strictly functional purpose, no tracking).

9. Changes

This page may be updated if how the site works changes (a new provider, a new feature that collects data). A "last updated" date isn't shown automatically yet — to add if this page starts changing regularly.