Last updated: October 20, 2026
PartyUp is an entertainment mobile application offering party games for adults, published by Sensa Network. This Privacy Policy explains what data the app processes, why, for how long, and with whom it is shared.
Most of the app works entirely offline: the solo and local game modes send nothing to any server. Data is only transmitted when you use the online multiplayer mode, the music quiz mode, or when the app reports anonymous usage statistics — all described below.
| Data | When | Why | Kept for |
|---|---|---|---|
| The nickname you type | When you create or join an online game | To show you to the other players in the room | Deleted with the room, at most 6 hours after it ends |
| Your answers, drawings and votes during a game | Online multiplayer only | To run the game and compute scores | Deleted with the room, at most 6 hours after it ends |
| A device identifier generated by the app | Online multiplayer, usage statistics, referral reward | To reconnect you to your game after a network drop, to count usage without accounts, and to remember an unlocked referral reward | 6 hours for games; see section 4 for statistics; as long as the referral reward remains unlocked |
| Purchase events (that a purchase or restore happened, and which product) | When you buy or restore the optional Premium content | To know whether the purchase flow works and how often it is used | See section 4 (14 months) |
| Web purchase record: a random key stored in your browser, the offer, the amount, Stripe's payment references, the date you waived the withdrawal right | When you buy in the web version (/app/) | To unlock what you paid for, to remove it after a refund, and to keep the accounting records the law requires | 10 years (section 4) |
| Your email address, when you ask for a restore code | Web version, "I already bought" | To send you a 6-digit code and find your purchases at Stripe | Not stored: we keep only a one-way hash of it, deleted after 24 hours |
| Anonymous usage events (screen opened, game started, …) with app version and language | While using the app | To understand which game modes are used and fix problems | See section 4 (14 months) |
| Feedback and reviews you send from the app: the category, your text (optional for a review), a rating from 1 to 5 (reviews in the web version), with app version, language, platform and the device identifier | When you use “Your opinion matters” in the settings, or rate the web version | To read and act on what you tell us; the identifier only limits repeated sending. A review, good or bad, may be shown on our website, without your name or identifier | 14 months (section 4) |
| The search text you enter in the music quiz mode | Music quiz mode only | To search for a matching playlist | Not stored by us; forwarded to the YouTube API (section 5) |
The app does not create user accounts and does not ask for your name, phone number or postal address. It asks for an email address only in the web version, if you request a restore code (section 3.2); the address you give on Stripe's payment page is collected by Stripe, not by us. It does not collect location data, contacts, photos, or any special-category data (health, opinions, orientation, and so on).
The device identifier is generated by the app itself. It is not your advertising ID and not a hardware serial number, and it is not used to build an advertising profile. However, because it is persistent, it is treated as personal data under the GDPR and covered by the rights described in section 8.
The app sends a small number of anonymous usage events to our own server: which screen was opened, which game mode was started, whether a purchase was completed and which product it concerned, the app version and the interface language, together with the device identifier described above and a timestamp.
To detect malfunctions, the app and the web pages also send technical diagnostics: error reports, crash or forced-close detection, display smoothness (how many frames were slow, in milliseconds), start-up and loading times, slow or failed network calls (the name of the request and its duration, never its content), the Android version and a rounded memory size (for example “4 GB”) — never the device model. These diagnostics never contain anything you typed or said.
On purchases specifically: we record only that a purchase happened and which product it was. We never receive a payment method, a card number, a billing address or a transaction amount — the payment itself is handled entirely by Google Play (Android) or by Stripe (web version, section 3.2).
The page you are reading is served from the same server as the app's API. When a visitor opens our home page, or clicks the button leading to the Google Play listing, we record a single anonymous counter line: the event name, a timestamp, the interface language, a coarse platform family (for example ios, android or windows) derived from the browser's user-agent string, and — when the visit came from another site — the host name only of the referring site, never the full address.
Links to PartyUp shared in a message or a post (/play.php) record a
different line when they are opened. It holds exactly: the event name; the game named in
the link, if any; the src and ref labels written in the link
(see below); a platform family (ios, android or other)
derived from the user-agent string; where we send the visitor (play for the
Google Play listing, web_app for the web version); the indicator
“visit by a link-preview robot”; and two timestamps set by our server.
It holds neither the interface language nor the referring site: your browser's language
only chooses the language of the page you see, and is not stored.
The labels come from the link itself. src says where the link was shared
from (for example card_share for a card shared from the app). ref
is, for an invitation to an online game, the code of that game room (for example
room_ABCD), and otherwise empty or a fixed word such as web. A room
code is four letters drawn at random: it names a game room, not the person who opens the
link. The room is deleted 6 hours after its last activity, and the same code can then be
given to a new room.
A link-preview robot is the program a messaging app, social network or search engine sends to read a link and build its preview (for example WhatsApp, Discord or Googlebot). The indicator holds only the short name of that service (for example whatsapp), derived from the user-agent string; for a visit by a person it is empty. The user-agent string itself is never stored. The indicator is used to leave these robots out of our counts, and when a robot opens a room invitation link, no invitation is recorded.
The game and the two labels also travel on with the link: to Google Play, which hands them to the app when it is installed from that link, or in the address of the web version. If usage statistics are on, the app then reports them with its own statistics (section 3): that is how we know which shares bring new players. When a person opens a room invitation link while the room still exists, we also note, apart from the counter line, that the host of that room had an invitation clicked: the room code, the host's device identifier and the time. This note is kept for 30 days and used only to credit the host's referral reward if the friend installs the app (section 4, “Referral progress”).
When the app is installed from a room invitation link, it tells our server as soon as it has read the invitation from Google Play (usually the first time it is opened), whether usage statistics are on or off. It sends exactly: the room code received from Google Play (for example room_ABCD), the app's device identifier (section 2), and the time at which Google Play says the link was clicked. This message is kept apart from the statistics on purpose: it credits a reward to someone else — the host who invited you — and that reward should not depend on the statistics setting of the person invited. Three distinct friends unlock a reward for the host that lasts 7 days.
Our server uses the click time only to find which host had that room code at that moment (a code can be reused), and does not store it. If it finds the matching invitation note, it records that the host's device and yours are linked as host and invited friend: that is the “Referral progress” of section 4. If it finds none, nothing is stored. If our server cannot be reached, the app keeps the room code and the click time on your device and tries again at the next openings, five times at most, then forgets them.
What it is for: we want to know how many people see this page and how many of them go on to the store, and in particular how many arrive on an iPhone — the app is Android-only today, and that number is what tells us whether an iOS version is worth building.
In the web version, payment happens on a page hosted by Stripe. Stripe collects your card details and the email address you enter there, and sends you the receipt. We never receive your card details. We keep a purchase record (see the table above) tied to a random key stored in your browser — not to your name.
To restore purchases on another device, you type the email address used at payment. We ask Stripe whether that address paid, and if it did we email you a 6-digit code. The answer shown in the app is the same whether or not the address paid, so nobody can use it to find out who is a customer. We store neither the address nor the code: only one-way hashes of them, deleted after 24 hours. The email is sent through Infomaniak, our mail provider; neither the address nor the content is written to our logs.
The page /jeux/question-du-jour/ asks one dilemma a day and shows how other visitors voted. When you vote, the page sends our server the date, the question, your choice (A or B) and a random identifier generated by your browser and kept in its local storage. No cookie is used, and the identifier is not tied to your name, your IP address, the app or anything else.
The page /jeux/qui-me-connait/ (in English: /en/games/who-knows-me-best/; also Spanish, Portuguese, German and Italian) lets you answer 10 questions about yourself and send a link to friends, who guess your answers. When you create a challenge or answer one, the page sends our server the first name or nickname you type, your answers, and the same kind of random identifier generated by your browser as in section 3.3. No cookie is used, and nothing is tied to the app or to your IP address.
In the app, a host can pick a date for their next game night and send one invitation link
(join.html?soiree=…). Our server then stores only the date and time,
a random identifier for the night, and a random secret drawn by the host's device so that
only the host can link a room to it or cancel it. On the night, it also stores the
room code the host opens. No nickname, no name, no device identifier and no
contact is sent: the app's share sheet sends the link, our server never sees to whom.
We do not sell data and do not share it for advertising. Data reaches third parties only in these cases:
Data described in this policy is stored on a server hosted by OVHcloud in France (European Union). Requests to the YouTube API and to Google Play are processed by Google, and web payments by Stripe; both may transfer data outside the European Union under their own safeguards.
The app does not request access to contacts, camera, microphone, location, files or SMS. It uses the internet connection only for the features described above.
If a future feature requires an additional permission, it will be explained clearly and this policy will be updated before that feature ships.
Under the GDPR you may request access to your data, its correction, its deletion, a copy of it, or object to its processing. Because the app has no accounts, we identify your data by the device identifier: send it to us and we will act on it.
You can sever the link at any time yourself: clearing the app's data or uninstalling the app resets the identifier, and a new one is generated. Data recorded under the previous identifier can then no longer be connected to you or to your device.
Step-by-step instructions are on our dedicated page: Delete your data. In short: write to contact@sensanetwork.com with the approximate dates and the game modes you used, so we can locate your records. We answer within one month. You may also lodge a complaint with your national data-protection authority (in France, the CNIL).
PartyUp contains adult-oriented content and is intended for users aged 18 and older.
Communication between the app and our server is encrypted in transit (HTTPS/TLS). Access to the server is restricted to the publisher. Online game data is short-lived by design, which limits what can be exposed.
This policy may be updated to reflect changes to the app or to legal requirements. The “Last updated” date at the top indicates the most recent revision. Material changes affecting how your data is used will be reflected here before the change takes effect.
Publisher: Sensa Network — contact@sensanetwork.com