Pellizz — Home

Privacy policy

Last updated: October 25, 2026

This policy explains which data the Pellizz mobile app and the pellizz.app website process, why, for how long, and what your rights are. Pellizz is published by Hexalgo (27 rue des Grandes Pannes, 49100 Angers, France). For any question about your data: privacy@pellizz.app.

1. Who is responsible for your data

  • Hexalgo, publisher of Pellizz, is the data controller for running the service: accounts, events, gallery, challenges, security and moderation by the publisher.
  • The organizer of an event is responsible for the data they bring and the choices they make: their guest list (the names they import or enter), the people they give the event code to, and the moderation of their event. For this processing, we act on their behalf.
  • Professional use: when a company organizes an event (seminar, team building…), it is the controller of the guest list and the event's photos, and we act as its processor. Our commitments are set out in the data processing addendum (GDPR article 28) included in the terms of use; it is also available on request at privacy@pellizz.app.

2. Data we process

  • Account, created in the app or on the pellizz.app website: the first name or display name you choose and your language. For a full account: your e-mail address and your password (stored only as an irreversible hash). A guest account contains no e-mail address.
  • Acceptance of the terms: each time the terms of use and this policy are accepted (creation or securing of the account, arrival in an event, new version of the texts), the date, the version accepted, the origin (app or website), the occasion and, for the arrival in an event, the event concerned; for a full account, a fingerprint (hash) of the e-mail address. No IP address and no phone model.
  • Sign-in with Google or Apple (if you choose it): the identifier of your account with that provider and the e-mail address it sends us (Apple may provide a relay address). With Apple, we also keep an encrypted token that lets us revoke this sign-in when you delete your account. We never receive your Google or Apple password.
  • Event participation: the events you joined, your role (organizer or participant), your table or team, the challenges completed and their times.
  • Photos and videos: the photos and videos (image and sound) you send (and an event's cover photo), their capture time (for a video, the time the recording started), their dimensions and the length of the videos. File metadata, including GPS location, is removed before sending by the app or, on the website, by the page that prepares the photo in your browser, then again by our servers, for videos as for photos, including for the cover photo. Photos and videos may show other people, and the sound of a video may pick up what they say: see the terms of use.
  • Reactions, when they are turned on: the reaction (❤️, 😂, 🤩 or 👏) you leave on a photo or a video and its date; one per photo, which you can change or remove.
  • Reports, blocks and moderation: photo reports, their reason and whether they were sent to the publisher; photos hidden by organizers; the people you have blocked; account suspensions decided by the publisher; the result of the automatic moderation of each photo and video (detections of the analysis program, any hold and the organizers' decision).
  • Guest list: the names organizers import or enter to prepare their event, and the link with the participant who recognizes themselves in it.
  • Co-organizer invitations: when the owner of an event invites someone to co-organize it, the e-mail address they enter, the event, the person who invites, the language of the e-mail, the dates of sending, expiry, acceptance or cancellation, the number of sendings, the status of the invitation and the account that accepts it. The link of the e-mail contains a single-use code of which we only keep a fingerprint (hash), never the code itself.
  • E-mails of ideas and offers (only if you accept them): your e-mail address, your language and the types of the events you took part in (birthday, offsite, party…), to write to you about what concerns you; the date and kind of each e-mail sent. Proof of your choice: for each consent and each withdrawal, the date, the version of the checkbox text and its origin (app, website or unsubscribe link).
  • Purchases (if you buy a plan or an extension): on the website, the plan, the amount, the date, the event name at the time of purchase, the link to the buyer's account while it exists, the Stripe identifiers of the payment and the invoice link, for a business invoice the company name, registration number (SIRET) and VAT number, and the date on which you ticked the box asking for the purchase to apply immediately and waiving your right of withdrawal (proof of this waiver, see the terms of use). Your card details are entered with Stripe and never reach us. In the app (App Store or Google Play): the plan, the product bought, the date, the event, the link to the buyer's account, the Apple transaction or Google order identifier and, with Google, the purchase token; the payment is collected by Apple or Google, and your payment details never reach us.
  • Challenge suggestions (organisers): the answers given to get challenge ideas (mood, whether children take part, number of challenges, first name of the guest of honour and, on a paid plan, a free description of the group and the guest of honour's age). They are only used to put the proposals together and are not stored; we only count the suggestions obtained per event. The first name is inserted into the texts by Pellizz and is never sent to our AI provider.
  • Notifications: your phone's notification token (Firebase Cloud Messaging) and its platform (Android or iOS).
  • Campaign measurement (only with your consent, on the website's presentation pages: see §7): the pages you view, the page you came from and the campaign parameters of the address (utm_… and, for Meta, the identifier of the click on one of our ads, fbclid, kept in the _fbc cookie), measured in your browser by Google Analytics and the Meta pixel. In your browser, Google Analytics and the Meta pixel also receive your IP address and information about your browser; if you are signed in to Facebook or Instagram, Meta may link the visit to that account. When you click through to a store from these pages, create an account or buy a plan or an extension on the website, our server also sends the event to Google (if you accepted audience measurement) and to Meta (if you accepted advertising): its time, the identifier of their cookies, the chosen store or the sign-up method (e-mail, Google or Apple) and, for a purchase, what was bought, its amount and a purchase reference; to Meta only, the page of the website you came from, your IP address and your browser. When you create an event on the website, our server reports it to Google only (if you accepted audience measurement), never to Meta: its time, the identifier of the Google Analytics cookie, the type of event (birthday, offsite, party…) and whether its challenges are on. Never your name, your e-mail address, your Pellizz account, the name, place or photos of your events, or an invitation code.
  • Store clicks: on the presentation pages, the clicks to the App Store and Google Play are counted per day, without any identifier, whether you accepted campaign measurement or not.
  • E-mail opening: the date and time our e-mails are opened, linked to the recipient's address, recorded by our e-mail provider (§7).
  • Log of the publisher's actions: every action of a Pellizz administrator (opening of an administration session, suspension, reactivation or deletion of an account, support e-mail sent, sessions of an account ended, photo hidden or deleted, reports dismissed…) is written to a log: the administrator and their e-mail address, the action, the account or photo concerned, the reason entered, the state before and after the action, the administrator's IP address and the date.
  • Technical data: IP address, date and time of requests and date of last activity, in our server logs.

The app uses the camera only when you take a photo, film a video or scan a QR code, and the microphone only while recording a video you started (if you refuse access to the microphone, your videos are recorded without sound); it only accesses the photos and videos you pick. On Android, the QR code is read directly on the phone (Google ML Kit): the image is not sent. Pellizz contains no advertising. The app and the account area load no audience measurement or advertising script; only creating an account or an event and buying on the website can lead there, with your consent, to a conversion sent by our server, which then reads the identifiers of the measurement cookies set by the presentation pages (§2 and §7). On the website's presentation pages, Google Analytics and the Meta pixel are only used with your consent (§7). We sell no data.

3. Why, and on what legal basis

  • Providing the service (account, events, gallery, challenges, leaderboard, photo and video export, event transfer, verification, password, export, co-organizer invitation, pre-deletion reminder and inactive-account warning e-mails): performance of the contract, i.e. the terms of use you accept (GDPR article 6.1.b).
  • Payment of plans and extensions: performance of the sales contract (article 6.1.b). Retention of purchases: our legal accounting obligations (article 6.1.c). Proof of the waiver of the right of withdrawal (purchases on the website): our legitimate interest in being able to show this waiver in case of a dispute (article 6.1.f).
  • Push notifications: your consent, given by allowing notifications on your phone; you can withdraw it at any time in the phone settings. They are service notifications, including the day after an event, when a notification offers the participants whose guest account is not secured yet to find the photos again (at most one every 30 days); they never contain an offer or a price.
  • E-mails of ideas and offers: your consent (article 6.1.a), given by ticking a box that is never ticked in advance, when you create your account or later. You can withdraw it at any time in the app ("Me" tab), in your account on the website or with the one-click unsubscribe link in each e-mail. At most 2 of these e-mails every 30 days; whether they are opened is measured as for our other e-mails (see below and §7). The proof of your choice is based on our legal obligations (being able to demonstrate consent, article 7.1).
  • Audience and campaign measurement on the website's presentation pages (Google Analytics, the Meta pixel and the conversions sent by our server, see §2 and §7): your consent (GDPR article 6.1.a and article 82 of the French Data Protection Act), given in the cookie banner, separately for audience measurement and for advertising. You can withdraw it at any time with "Manage cookies", at the bottom of these pages.
  • Proof of the acceptance of the terms: our legitimate interest in being able to show, in case of a dispute, that the terms of use and this policy were accepted, and in which version (article 6.1.f).
  • Measuring whether e-mails are opened (invisible image of our e-mail provider, §7): our legitimate interest in checking that our e-mails are delivered and, for the e-mails of ideas and offers, in measuring the interest they raise (article 6.1.f). You can avoid it by blocking the loading of images in your e-mail program.
  • Guest list: the organizer's legitimate interest in preparing their event (article 6.1.f). The organizer informs the people on their list; anyone can object: the organizer or we then remove their name from the list.
  • Co-organizer invitations: the legitimate interest of the event's owner in getting help to organize it, and ours in providing this service to them (article 6.1.f). The invited person can ignore the e-mail (the invitation expires after 7 days) or ask for their address to be erased by writing to privacy@pellizz.app.
  • Security, abuse prevention and moderation (request rate limits, reports, blocks, account suspensions, logs): our legitimate interest in protecting the service and its users (article 6.1.f).
  • Log of the publisher's actions: our legitimate interest in securing the administration of the service and in being able to show, in case of a dispute, what was done, by whom and why (article 6.1.f).
  • Automatic moderation of photos and videos (nudity detection before publishing, which organizers can turn off): our legitimate interest, and the organizers', in keeping nude photos and videos out of the gallery and off the big screen without their agreement (article 6.1.f). The analysis is done by a program on our servers, with no outside provider; it does not recognise people and decides nothing about you: a held photo waits for the organizers' decision.
  • Legal obligations: retention of connection data, answers to requests from the authorities and reporting of illegal content (article 6.1.c).

4. Who can see your data

  • The event's participants see your display name, your table, your photos, your videos and your reactions. There is no public gallery: the event code is needed to get in. You can block a participant: their photos and videos are no longer shown to you, and they are not told.
  • On the website (account area, pellizz.app/account), a full account finds the gallery of the events it takes part in, and a guest can join an event and take part in it from their browser, with a guest account created on the website: the same photos and videos and the same rights as in the app, nothing more.
  • The event's organizers can also moderate photos and videos (including those held back by the automatic moderation, which only they and the author can see), remove a participant, manage tables and the guest list, and download the export of all photos and videos.
  • The big screen: an organizer can show the event as a slideshow from the account space. Everyone in front of the screen then sees the published photos and videos, with their author's display name and table, and the challenge leaderboard and podium. Reported photos do not appear there, nor those an organizer published without showing them on the big screen after the automatic moderation held them back.
  • The publisher's moderation team sees a photo or a video, its event and the report when it is reported to it ("Also report to Pellizz" option, or automatically for the reason "My child / a minor is in the photo"); it handles the report as soon as possible, usually within 24 hours.
  • Our processors, only to run the service:
    • OVHcloud (OVH SAS, France): hosting of the servers, the database and the photo and video storage, in the European Union;
    • Brevo (Sendinblue SAS, France): sending e-mails and measuring whether they are opened (§7), in the European Union;
    • Google (Firebase Cloud Messaging): delivery of push notifications, including to iPhones through Apple's notification service (APNs);
    • Google (ML Kit), on Android: reading QR codes directly on the phone; the image is not sent, but the kit may send Google technical diagnostic and usage data (phone model and system, app version, performance, installation identifier);
    • Apple (Sign in with Apple) and Google (Sign in with Google): sign-in with your Apple or Google account, only if you choose it;
    • Google (Google Analytics, Google Ireland Ltd, Ireland), only if you accept audience measurement: traffic statistics of the website's presentation pages and of the conversions described in §2, with Google signals and ad personalisation turned off;
    • Anthropic (Anthropic PBC, United States), on paid plans only: adapting the challenge suggestions an organizer asks for. Anthropic receives the event type, the chosen mood and game mode, whether children take part, whether there is a guest of honour and their age group (child, teenager, adult or senior), the group description typed by the organizer, the titles of the challenges already planned and the organizer's rewriting instructions; never the guest of honour's first name, replaced everywhere before sending, nor any account identifier. Anthropic does not use these texts to train its models and deletes them after a limited retention period.
  • Meta (Meta Platforms Ireland Ltd, Ireland), only if you accept advertising: the Meta pixel and Meta's Conversions API measure the effectiveness of our ads on Facebook and Instagram, with the data described in §2. For their collection and transmission, Meta and we are joint controllers; under our arrangement with Meta, Meta is responsible for this data once received, and you can also exercise your rights with Meta (Meta's privacy policy).
  • Apple (App Store) and Google (Google Play), only if you buy a plan or an extension in the app: they collect the payment in their own name, as controllers of their own processing, and confirm the transaction to us.
  • Stripe (Stripe Payments Europe, Ireland), our payment provider, only if you buy a plan or an extension on the website: it processes your payment data on our behalf and remains responsible for its own processing for fraud prevention and its legal obligations. Pellizz never sees your card number; we only keep: the plan, the amount, the date, the event name at the time of purchase, the link to the buyer's account while it exists, the Stripe identifiers of the payment and the invoice link, for a business invoice the company name, registration number (SIRET) and VAT number, and the date of your waiver of the right of withdrawal.

5. Transfers outside the European Union

Your photos, your videos and your account are hosted in the European Union (OVHcloud). Google (notifications, QR code reader on Android, Sign in with Google) and Apple (iPhone notifications, Sign in with Apple) may process in the United States the data that goes through their services: notification tokens and contents, technical data from the QR code reader, sign-in identifiers; likewise, Stripe may process payment data in the United States, as may Apple and Google for a purchase in the app, and Anthropic processes there the information of a challenge suggestion request described above (paid plans); Google (Google Analytics) and Meta (pixel and Conversions API) may also process there the audience and campaign measurement data you accepted. These transfers are covered by the EU–US Data Privacy Framework for the companies that adhere to it and, for the others, including Anthropic, by the European Commission's standard contractual clauses in their data processing agreement.

6. For how long

  • Events, photos, videos and participation: until the event is deleted automatically, at the end of its plan's retention period counted from the event date: 60 days for the free plan (90 days for free events created before October 2, 2026), 12 months for the paid plans. A 12-month extension can be purchased on any paid plan. Organizers get an e-mail reminder 7 days before; deletion only happens at least 7 days after this reminder. An event's date cannot be set more than 7 days in the past. An organizer can also delete the event earlier.
  • Photo and video versions: when a photo or a video is deleted or replaced, the storage keeps the previous version for 30 days at most, to protect against accidental deletion, then erases it.
  • Reports: kept with the photo concerned and deleted with it.
  • Automatic moderation result: kept with the photo or video and deleted with it; the frames taken from a video to analyse it are erased as soon as the analysis ends.
  • Full account: until you delete it; deletion is immediate. A full account inactive for 3 years is deleted, after a warning e-mail sent 30 days before.
  • Guest account: deleted automatically when it no longer has a valid session or a participation in a still active event.
  • Proof of consent to the e-mails of ideas and offers: 3 years after the end of the consent (withdrawal or account deletion), then erased; after the account is deleted, it only keeps a fingerprint (hash) of the e-mail address. The log of the e-mails sent (date and kind) is deleted with the account.
  • Proof of the acceptance of the terms: kept as long as the account exists, then 5 years after its deletion (general limitation period), then erased; after the account is deleted, it only keeps a fingerprint (hash) of the e-mail address. A proof without an e-mail address (a guest account, for example) is deleted with the account.
  • Sign in with Apple token: kept encrypted until the account is deleted, then revoked with Apple.
  • Purchases (plans and extensions), with the proof of the waiver of the right of withdrawal: kept for the legal retention period of accounting records (10 years from the end of the financial year), even if the event or the account is deleted.
  • Database backups: kept 30 days at most, then erased.
  • ZIP export of photos and videos: link valid 7 days, then the file is deleted.
  • Sessions: 30 days (full account) or 1 year (guest account) without use. Links sent by e-mail: 1 hour to choose a new password, 24 hours to confirm the deletion of the account, 48 hours to verify the e-mail address, 7 days for a co-organizer invitation and for the ZIP export; the unsubscribe link of the e-mails of ideas and offers stays valid with no time limit.
  • Co-organizer invitations: link valid 7 days from the last sending, a new sending replacing the previous link; the invitation is deleted 30 days after it is accepted, cancelled or expired, and with the event.
  • Log of the publisher's actions: 1 year, then erased.
  • Cookie banner choice: kept 6 months in your browser, then asked again.
  • Campaign measurement: Google Analytics cookies 13 months from when they are set, never extended by later visits, data in Google Analytics 14 months; Meta cookies 90 days, extended on each visit, never more than 13 months. Our server only keeps conversions for the time it takes to send them; only those of a purchase on the website wait for the payment to be confirmed: their data (cookie identifiers, page of origin, IP address and browser) is deleted as soon as it is sent, when the payment expires or fails, otherwise after 48 hours. The database backups, kept 30 days at most, may contain a copy of it until they are erased.
  • Technical logs: 12 months at most.

7. Cookies and trackers

The website's cookies and trackers depend on its pages:

  • Presentation pages (home, how it works, pricing, event types, comparison, about, guides): two purposes subject to your consent, chosen separately. Audience measurement: Google Analytics counts visits and page views (cookies _ga and _ga_…, 13 months, not extended by your later visits). Advertising: the Meta pixel measures the effectiveness of our ads on Facebook and Instagram (cookies _fbp and _fbc, 90 days, extended on each visit, never more than 13 months). Before you consent, none of these tools is loaded and none of these cookies is set. Their identifiers also link the conversions sent by our server to a campaign (§2).
  • Your choice: the banner offers "Refuse all", "Customize" and "Accept all". Your choice is kept 6 months in the pellizz_consent cookie, which is strictly necessary, then asked again. You can change it at any time with "Manage cookies", at the bottom of the presentation pages and of this page; withdrawing a consent deletes the cookies of the tool concerned.
  • Invitation pages, account area and app: none of these tools is loaded there and none of their cookies is set; only creating an account, creating an event (to Google only) and buying on the website lead there, with your consent, to a conversion (§2). The account area (pellizz.app/account), which includes the web version for guests, only sets its session cookie pellizz_refresh, a strictly necessary cookie, when you sign in or when you join an event as a guest on the website, to keep you signed in: it expires after 30 days without use for a full account, 1 year for a guest account; it is only sent to our server, stays out of reach of the page's scripts and is never read by a third party. The website also keeps in your browser what is strictly necessary for it to work: the photos you picked that are waiting to be sent (IndexedDB), so that an interrupted upload resumes, until they are sent, removed or the account is deleted; the code of a co-organizer invitation (sessionStorage), for the life of the tab, until it is accepted or the tab is closed; the events whose invitation to secure your guest account you closed (localStorage), so as not to show it again, until you clear the website's data. This data is never read by a third party. The app contains no advertising, no audience measurement tool and no advertising tracker.
  • E-mails: our e-mails contain a small invisible image, placed by our e-mail provider (Brevo (Sendinblue SAS, France)), which shows whether an e-mail was opened: the date and time of the opening, linked to the recipient's address. It is used to check that our e-mails are delivered and, for the e-mails of ideas and offers, to measure the interest they raise; this information is kept for the retention period of our provider's sending logs. You can avoid it by blocking the loading of images in your e-mail program. Their links only let us count the visits they bring to the website, without any personal identifier.

8. Your rights

You have the right to access, rectify, erase, restrict, object to the processing of and port your data, and to set instructions for what happens to it after your death. You can change your name and language in the app ("Me" tab), accept or refuse the e-mails of ideas and offers in the app, in your account on the website or with the link in each e-mail, and delete your account in the app or from this website. If you own an event, you must first, for each event, transfer it to another participant or delete it. If your name is on an event's guest list, you can ask the organizer or us to remove it.

For other requests, write to privacy@pellizz.app: we answer within one month. For a company event, we forward the requests that concern the organizing company to it and help it answer them. If you believe your rights are not respected, you can lodge a complaint with the CNIL (www.cnil.fr) or your local data protection authority.

9. Security

Traffic is encrypted (HTTPS). Photos and videos are stored in a private space and can only be reached through temporary links given to the event's participants. Passwords are stored as irreversible hashes and session tokens are kept in the phone's secure storage; on the website, in a cookie out of reach of the page's scripts (HttpOnly), only sent to our server, the access token being kept in memory only.

10. Children

Pellizz is intended for people aged 13 and over. In France, a minor can consent alone to the processing of their data by an online service from the age of 15 (GDPR article 8 and article 45 of the French Data Protection Act). Between 13 and 15, using Pellizz requires the permission of a person with parental authority, and anything based on consent (notifications, for example) requires the joint consent of the minor and that person. Pellizz is not intended for children under 13: a child may appear in a photo taken by an adult, under that adult's responsibility.

A photo showing a minor is posted under its author's responsibility, who must have the parents' permission. Any parent can report a photo with the reason "My child / a minor is in the photo": the report is sent to the organizers and to the publisher, and the photo is removed quickly. You can also write to contact@pellizz.app.

11. Changes

We may update this policy; the date of the last update is shown at the top of the page. Every new version is submitted to you: with a full account, a screen asks you to accept it again, in the app or on the website, to keep using Pellizz; with a guest account, you accept the version in force each time you join an event.