Privacy Policy

Last updated: 26 August 2026 Version: 1.0

1. Who processes your data (Controller)

The controller of personal data under the GDPR is:

  • Name: Valere Damee, entrepreneur individuel (activité libérale)
  • Registration number: SIREN 109055723
  • Address: 18 rue Mélingue, 75019 Paris, France
  • Email for data requests: privacy@valtip.fr

The controller is established in France (EU), so no representative under Art. 27 GDPR is required. No Data Protection Officer has been appointed: the processing carried out does not fall within the cases where appointment is mandatory under Art. 37 GDPR.

Referred to below as "we", "the Service", "the Platform".

2. In short

The Platform is a tip accounting system for venues: a guest leaves a tip through a secure page, the money is collected into the venue's account via Stripe (the payment is executed directly on the venue's account and does not pass through any Platform account), and the Platform keeps a transparent record of shares and settlements. We collect the minimum data needed to run the service and we do not store card details — those are handled by Stripe.

3. What data we collect

3.1. Account data (employees and venue owners)

First name, last name, username, email address (and its verification status), contact details (phone/messenger, if provided), profile photo (optional), position, interface language. Passwords are stored as a hash only (bcrypt); we never see them in clear text.

3.2. Authentication and security data

Session identifier (stored hashed, not in clear text), IP address and User-Agent at sign-in, failed sign-in counter and lockout time, history of recent password hashes (to prevent reuse), hashes of single-use password reset tokens and email verification codes (with a limited lifetime).

3.3. Tip and payment data

Amount, currency, date/time, Stripe operation identifiers (e.g. PaymentIntent), fee amounts (platform and payment processing), operation status. A guest's email for the receipt (if the guest provides one) is passed to Stripe only and is not stored in our database. We neither receive nor store the guest's card details — the payment is processed on Stripe's side.

3.4. Settlement records

Records of calculated shares (payouts) and of the fact of settlement: who, to whom, how much, when and by whom it was recorded. The actual handover of money to an employee happens outside the Platform (see the Terms of Service).

3.5. Activity log (audit)

For security and accountability we record key events: sign-ins, settlements, permission changes, deletion, password reset, refunds and chargebacks.

3.6. Cookies

  • __Host-session_id (in production; in dev — session_id) — sign-in session (strictly necessary, HttpOnly).
  • csrf_token — CSRF protection (strictly necessary).
  • lang — chosen interface language (functional).

We use no analytics or advertising cookies, so no consent banner is shown: the cookies above are either strictly necessary for the service to work or a record of your own language choice.

3.7. Guest (payer) data

A guest leaves a tip without creating an account. We store neither the guest's name, nor email, nor card data. What is processed:

  • Payment amount and currency — in our database (see 3.3) and at Stripe.
  • Email for the receipt (optional) — at Stripe only; the receipt is sent by Stripe.
  • Card data — at Stripe only (Stripe Elements form); our server never sees it.
  • The guest's IP address — briefly in the rate-limiting system (not persisted to the database) and in the web server's technical logs (retention: see point 8).

4. Why we process it and on what legal basis (Art. 6 GDPR)

Purpose Legal basis
Registration, sign-in, operation of the account area Performance of a contract (6(1)(b))
Accepting tips, calculating shares and fees, settlement records Performance of a contract (6(1)(b))
Security: brute-force protection, rate limiting, audit Legitimate interest (6(1)(f))
Retention of financial/payment history Legal obligation — accounting and tax (6(1)(c))
Email verification, service notifications Performance of a contract / legitimate interest
Optional communications (none are sent at present) Consent (6(1)(a))

5. Who sees your data inside the Service

Running the Service involves limited disclosure of data to its other users:

  • Guests see, on the payment page, the name, photo (if uploaded) and position of employees currently on shift, as well as the venue's name.
  • The venue owner and managers (within their area of responsibility) see employees' profile data, their shifts, calculated tip shares and settlement records.
  • Colleagues/subordinates see contact details if you filled in that optional profile field.

Do not put information into profile fields that you are not prepared to disclose to these categories of users.

6. Who we share data with (recipients and sub-processors)

We do not sell personal data. We use suppliers acting as processors on our instructions, and we conclude a data processing agreement (DPA, Art. 28 GDPR) with each of them:

  • Stripe — payment acceptance and processing (Stripe Connect). Stripe acts as an independent controller for the payment side and processes data under its own terms. See Stripe's privacy policy: https://stripe.com/privacy. Since 21/08/2026 the payment is executed on the Venue's account at Stripe (a direct charge), not on a Platform account. The practical consequence for the allocation of roles: for the payment operation the controllers are the Venue and Stripe, while the Platform processes only the outcome of the operation (amount, currency, identifiers, fees, status) for its own purpose — accounting for shares. The Guest's payment credentials never reach the Platform at any point, as before.
  • Hosting/infrastructure — OVH SAS, Gravelines data centre, France (EU).
  • Email (SMTP) — OVH SAS (France, EU) for verification/reset messages.
  • Photo storage — locally on our server (no external object storage is used).
  • Cache/rate limits (Redis) — self-hosted on the same server (OVH, France).
  • Error tracking (Sentry) — not used.
  • CDN providers (js.stripe.com, Tailwind Play CDN, cdnjs) — the visitor's browser loads scripts/styles from them, so they see the IP address and technical browser headers. No account data is passed to them.

7. International data transfers

The Service's infrastructure (servers, database, mail, files) is located in France; account data does not leave the EEA. Data goes outside the EEA in two cases only:

  • Stripe — Stripe Payments Europe Ltd (Ireland) may transfer data to Stripe, Inc. (USA) within its own group. Such transfers are covered by the EU Standard Contractual Clauses (SCC) and by Stripe, Inc.'s participation in the EU-U.S. Data Privacy Framework.
  • CDN providers (Tailwind Play CDN, cdnjs) — when the visitor's browser loads scripts and styles, they see its IP address and technical headers. No other data is passed to them.

8. Retention periods

  • Active account data — for as long as the account exists.
  • On account deletion, personal data (name, contacts, photo, etc.) is erased/anonymised. Financial history (tips, settlements, calculations) is retained, anonymised where possible — this is required for accounting and tax purposes. Retention period: 10 years from the end of the financial year (Art. L123-22 of the French Commercial Code).
  • Audit log — retained until the venue is deleted.
  • Web server technical logs — written to a size-limited buffer (at most 30 MB per service); the oldest entries are overwritten automatically as new ones arrive.
  • Reset/verification tokens — minutes/hours (single-use).

9. Your rights (Chapter III GDPR)

You have the right to: access your data; rectification; erasure (the "right to be forgotten", subject to point 8 on financial history); restriction of processing; portability; objection to processing based on legitimate interest; withdrawal of consent previously given; and to lodge a complaint with a supervisory authority (in France: the CNIL).

How this is implemented in the Service: - Viewing/correcting your profile — in the account area. - Account deletion — the "Delete account" function (erases personal data while keeping the anonymised financial history under point 8). - Other requests — to privacy@valtip.fr, answered within one month (Art. 12 GDPR).

10. Security

We apply reasonable technical measures: password hashing (bcrypt), storing session identifiers as hashes, brute-force protection (lockout with exponential backoff), CSRF protection, Content-Security-Policy, and data transmission over HTTPS. No system is 100% secure; we cannot guarantee absolute security.

In the event of a personal data breach we notify the CNIL within 72 hours of becoming aware of it (Art. 33 GDPR) and, where the breach is likely to result in a high risk to your rights, we inform you without undue delay (Art. 34 GDPR).

11. Children

The Service is not intended for persons under 16, and we do not knowingly collect their data.

12. Links to third-party services

Pages of the Service may contain links to third-party sites and services (for example Stripe). This policy does not apply to them; we are not responsible for their data practices — please read their own privacy policies.

13. Changes to this policy

We may update this policy. Material changes are communicated by email. The date of the last update is shown at the top.

14. Contact

Questions about data processing: privacy@valtip.fr. Postal address: 18 rue Mélingue, 75019 Paris, France.