Sipix

This page is a translation provided for information only. Only the French version of these documents is authoritative and prevails in the event of any discrepancy.

Privacy policy

Last updated on 11 November 2026

This policy sets out how the Sipix Service processes personal data, in accordance with Regulation (EU) 2016/679 (GDPR) and the French Data Protection Act (the “loi Informatique et Libertés”). Capitalised terms (Publisher, Organiser, Guest, Service) have the meaning given to them in the terms and conditions.

1. Data controller

The data controller is Monko Co Solns, 173 rue de Courcelles, 75017 Paris (see the legal notice). For any question, or to exercise your rights, write to contact@sipix.eu.

2. Data processed

Organisers (account holders)

  • account data: email address and login details;
  • event data: the couple’s first names, date, theme, settings;
  • technical data: access logs and session data;
  • if a paid plan is purchased: payment data (card details) and billing data (name, address and, for business customers, SIREN/SIRET and VAT numbers) are collected and stored directly by our payment provider, Stripe, when the order is placed. The Publisher has no access to them and keeps only transaction references (technical identifiers, plan purchased, amount, date) and the corresponding invoice.
  • signup origin: the source, channel and campaign named in the link you arrived through (for example an ad or a partner site) or, failing that, the domain name of the site that referred you to Sipix, kept with the account to measure our acquisition channels (legal basis: legitimate interest);
  • a log of actions on your account and events: your account’s technical identifier, the date and nature of each action (creation, activation, archiving, settings changes, deletion, purchase), with counts (number of files, volume). It contains no content, no name, no e-mail address and no guest data;

Guests and data subjects

  • uploaded content: photos, videos and voice messages, together with their associated metadata (e.g. the date a photo was taken and, where the device records them, GPS location coordinates and device information). The original file you upload is kept unchanged and can be downloaded by the other guests who have the link. Its metadata, including any location data, is then accessible to them. Switch off location tagging in your camera settings before the event if you would rather not share it;
  • optional data: a first name and a short note accompanying an upload (photo, video or voice message). They may be shown to the other guests if the Organiser so decides;
  • “favourites”: when a Guest likes a photo or video, that reaction is recorded together with a random identifier generated on their device and specific to the event. This identifier cannot be used to identify the Guest and serves only to count reactions and avoid duplicates;
  • the likeness and voice of the people who appear in uploaded content;
  • the email address a Guest leaves voluntarily in order to be told when the full album is available, together with their device’s display language. That single email announces that the album is available and may also mention the Sipix service.

Website visitors

  • anonymous traffic statistics: pages viewed, referring site or link, country, device and browser type, compiled without cookies and not linked to any account (legal basis: legitimate interest).

3. Purposes and legal bases

Provision of the Service
collection, hosting, display, slideshow and download of content. Legal basis: performance of the contract (and, for the people photographed, the Organiser’s legitimate interest in preserving the memory of their event).
Automatic enrichment
thumbnail generation and image-quality estimation (technical processing performed locally, always active) and, when the Organiser enables automatic analysis, moderation of explicit or violent content, addition of scene tags and transcription of voice messages. Legal basis: legitimate interest (quality and security of the Service).
Security and abuse prevention
rate limiting, bot protection (Cloudflare Turnstile, a component that loads without any visible interaction on the organisers’ sign-in and sign-up forms, see the cookie policy) and the prevention of misuse. Legal basis: legitimate interest.
Account management and legal obligations
account creation and, where applicable, invoicing. Legal basis: performance of the contract or legal obligation.
Service monitoring and support
keeping the log of organisers’ actions (see section 2) to understand how the Service is used, answer your support requests and detect abuse. Legal basis: the operator’s legitimate interest in running, securing and improving the Service.

4. Automated processing (AI)

Thumbnail generation and image-quality estimation are technical processes performed locally, without artificial intelligence, and are always active. Analysis by artificial intelligence (detecting explicit or violent content for moderation, adding scene tags and transcribing voice messages), on the other hand, takes place only when the Organiser enables it for their event. When it is disabled, no content (image or sound) is sent to an analysis model. The purposes and means of this analysis (models used, categories detected, moderation rules) are determined exclusively by the Publisher. The Organiser merely enables or disables this predefined feature for their event. This processing is not intended to identify individuals, and no facial recognition is used. No decision producing legal effects is taken solely on the basis of automated processing. Automatic moderation may hide content provisionally, but any permanent measure requires human review (article 22 of the GDPR). Should a facial-recognition feature ever be introduced, you would be informed of it specifically and it would require your explicit consent.

5. Recipients and processors

Your content (photos, videos, written and voice messages) is hosted in the European Union. Your data is never sold or used for advertising. It is processed on the Publisher’s behalf by the following technical processors:

  • Vercel Inc.: Application hosting (FR region) and cookieless audience measurement.
  • Cloudflare, Inc.: Storage of photos, videos and voice messages (EU region).
  • Supabase Pte. Ltd.: Database and authentication (FR region).
  • Scaleway SAS: AI enrichment when the Organiser enables it, namely photo analysis (moderation and automatic tagging) and voice-message transcription. Processing takes place in France (European Union) and the provider keeps no content.
  • Cloudflare, Inc. (Turnstile): Bot protection (Turnstile) on the organisers’ sign-in and sign-up forms, when active, by analysing technical browser signals (including the IP address) to tell legitimate visitors apart from automated programs, with no advertising purpose and no cross-site tracking.
  • Resend, Inc.: Sending of transactional emails (authentication emails and archive download reminders). Transfers outside the EU are governed by a data processing agreement (DPA) that includes the standard contractual clauses.
  • Infomaniak Network SA: Hosting of the contact mailbox. Messages sent to the Publisher (requests, exercise of GDPR rights, reports) are received and stored by Infomaniak. Transfers to Switzerland are covered by the European Commission’s adequacy decision.
  • Stripe Payments Europe, Ltd.: Payment processing when a paid plan is purchased. Payment data (card details) and billing data (name, address) are collected and stored directly by Stripe, which also processes them as a data controller for its own obligations (in particular fraud prevention). The Publisher never has access to the card number and keeps only transaction references.
  • Indy (Indy.fr SAS): Invoicing and accounting when a paid plan is purchased, namely issuing invoices and archiving them as required by law (a platform accredited for electronic invoicing).

Some of these providers are based outside the European Union. Any transfers are therefore covered by appropriate safeguards within the meaning of Chapter V of the GDPR (in particular the European Commission’s standard contractual clauses).

6. Retention period

An event’s content is kept for as long as the event is active. The event is archived two (2) months after activation (or earlier if the Organiser archives it manually), and its content is then permanently deleted ten (10) months after archiving. Some plans may provide for different periods. The periods and deadlines that apply to an event are shown to the Organiser in their dashboard. These periods are set in light of the purpose of preserving memories and the principle of data minimisation. Reminders invite the Organiser to download their archive before the deadline. Account data is kept for as long as the account is active.

Billing data (invoices and transaction references relating to purchases) is kept for ten (10) years in accordance with article L123-22 of the French Commercial Code, including after the account is deleted. This retention meets a legal obligation (article 17(3)(b) of the GDPR) and does not prevent the erasure of all other data. Payment data itself is kept by the payment provider in accordance with its own policy.

When an item of content is deleted individually, a copy may remain for up to seven (7) days in a downloadable archive that has already been generated, until that archive is automatically purged. Deleted content and data may also persist for up to thirty (30) days in our technical backups (database and file storage), which are kept solely for disaster recovery. They are not processed in any other way there and are permanently erased at the end of that period.

Operational logs are kept at two levels. The log of organisers’ actions (technical identifiers of the account and the event, date and nature of the action, counts; never any content, name, e-mail address or guest data) is kept for thirteen (13) months. When an account is deleted, its identifier is erased from this log: the remaining lines can no longer be linked to anyone. Purely technical logs (monitoring of the Service, aggregated counters, system events and anonymised error reasons) are kept for at most 30 days for routine events and 90 days for errors.

The email address left in order to receive the full album is kept until that single email is sent, which happens when the event is archived, and is then deleted from our servers. That email contains an unsubscribe link. The address is also deleted if the event is erased before the email is sent.

7. People appearing in content

Where a person appears in content uploaded by a Guest, their data is collected indirectly (article 14 of the GDPR). The data comes from the Organiser and their Guests. In practice, these people are informed by the Organiser, who undertakes to obtain their consent (see the terms and conditions). As informing each person appearing in content individually proves impossible or would involve disproportionate effort (article 14(5)(b) of the GDPR), that information is provided by this policy, which is publicly accessible, and relayed by the Organiser. Anyone may ask for content in which they appear to be deleted by writing to contact@sipix.eu or via the Report content page.

8. Your rights

You have the rights of access, rectification, erasure, restriction, objection and portability, as well as the right to withdraw your consent at any time where processing is based on consent. Where processing is based on legitimate interest, you may object to it at any time on grounds relating to your particular situation (article 21 of the GDPR). To exercise these rights, write to contact@sipix.eu. You may also lodge a complaint with a supervisory authority, in France the CNIL (www.cnil.fr). If you live in another Member State of the European Union, you may contact the supervisory authority of your country of residence or place of work (article 77 of the GDPR).

9. Security and access to content

Access to an event’s gallery relies on links containing random identifiers that cannot be guessed and are specific to each event. Only people who have the link can view the content. The Organiser may also enable an access code, which protects the upload and gallery-viewing features. However, the direct address of a file that has already been passed on (for example the URL of a photo that has been copied or reshared) remains accessible to anyone who holds it. Sharing links should therefore be given only to the people invited to the event.

10. Cookies

The use of cookies is described in the cookie policy.

11. Contact

For any question about your data, write to contact@sipix.eu.