Party Up is built so you can organize and join events with friends. Here is how we use data in the product today:
In short• Location is used only when you ask for nearby events or show a map. Device coordinates are sent as a query at that moment and are not stored on your account.
• Calendar sync in the phone app is optional. When you turn it on, the app adds events you're confirmed for to a calendar on your device and removes them when your plans change. Party Up never receives your calendar data; your calendar provider (for example iCloud or Google) syncs those entries like any other event.
• When you host, the exact event address or map pin you enter is stored encrypted. It is shown only under the same reveal rules as in the event form (for example to confirmed guests near event time). The exact address, map pin and guests' names are deleted 30 days after the event ends; the public place name stays with the event.
• Photos you choose become your profile avatar or an event cover image so others can recognize the event. If you sign in with Google, Telegram or Discord, we copy your profile picture from them once and keep our own copy; your picture is never loaded from their servers when others view it.
• Sign-in providers (Google, Apple, Telegram or Discord) create or link your account; Steam can only be linked. You can unlink any but your last way to sign in, and delete your account, from Settings. Each sign-in is kept as a session (app or browser, kind of device, sign-in method and dates; no IP address) so it can be signed out; a session is deleted 30 days after it ends.
• When you sign up you give your full name and date of birth, and you may give your gender. Your name is shown as the app describes; your date of birth and gender are never shown to other people. On a date poll, when you say yes to a time, everyone signed in who has the poll's link sees your name and profile photo next to that time, and the poll's creator also sees who said no. We use your date of birth to keep Party Up for adults and to check the age limits hosts set on their events. Giving your gender is optional: it lets a host open an event to women, men or a balanced mix, and, with your date of birth, it feeds statistics about Party Up as a whole. Only platform admins see them, as counts by gender and age band where any count from 1 to 4 is shown as "<5"; they are never public and never name anyone. Hosts see only the rules of their events and how many women and men have joined a balanced event. The app never shows anyone's gender or half. On a balanced event you tell us which half of the event each guest you bring takes, women or men; on any event with gender rules we keep each guest's half encrypted. The half a guest, or you, took is deleted 30 days after the event. Your name, date of birth and gender can be set once; to correct them, contact support and we will answer within a month. If an account is closed for being under 18, for each of its sign-in accounts we keep the provider, a coded marker and the month the person may join again (from which their birth month can be worked out) and when the record was made, and nothing else, until then.
• We also process push notification tokens, in-app notification history, reports you file, product feedback you send, reviews you write, follow relationships, host bans you set or receive, attendance marks hosts record about you (arrived or absent) with your reliability counters, group membership and group bans — each only as needed to run those features. We also record the day you last used Party Up — in the app, on the web or by answering through the Telegram or Discord bot, including Discord voice check-in — to know which accounts are still in use.
• Messages you send in Party Up chats (direct, event, and group chats) are stored encrypted and shown only to the people in that chat — and, for event chats, to the admins of groups the event is shared in. Event chats are deleted 7 days after the event ends, or straight away if the event is cancelled or deleted. Direct chats have no time limit: a message stays until its author deletes it or deletes their account. Group chats have no time limit either: a message stays until its author, a group admin or a moderator deletes it, its author deletes their account, or the group is deleted. A copy kept with a report is an exception: it stays with the report even after the message is deleted. When you delete your account, your messages are replaced by a "Message deleted" placeholder and your name is no longer shown in chats. The exception is a message of yours that was copied as context into a report someone else filed about another person: its text and your display name stay with that report until it is deleted, even after you delete your account. New-message push notifications on your device or browser may include a short preview of the message; we never send chat messages to Telegram. If you report a message, we keep an encrypted copy of it and of up to three messages before it with the report, for as long as we keep the report, even after the chat is deleted. Only platform moderators can read that copy, and it is not included in a data export.
• We share data with categories of recipients when required: sign-in and linked-account providers (Google, Apple, Telegram, Discord, Steam), map services (Google Places/Geocoding queries), push delivery (Expo and browser Web Push), hosting, photo storage and encrypted database backups (OVHcloud, in the EU), and event hosts or group admins when a feature requires it (for example revealing the exact event address to confirmed guests near the start time).
• You can request access to and a copy of your data (export), update your profile to rectify information, delete your account in Settings, and lodge a complaint with a data protection supervisory authority in your country. If an attendance mark or your reliability counters are wrong, tell us through Send feedback in Settings (or by email, if an address is shown below): we will review it and correct the record if it is wrong.
• Moderation: when we suspend an account, decline a public listing or dismiss a report, we keep a record of the decision, the reasons we gave and any appeal, to enforce the decision and to defend legal claims (legitimate interest, GDPR Art. 6(1)(f) and 17(3)(e)). We keep a decision for 12 months after it is taken or reversed, an active suspension while it lasts, and anything with an appeal still open until it is decided. If a suspended account is deleted, we keep a pseudonymous marker of its sign-in accounts for 12 months so the suspension cannot be escaped by signing up with them again.
• We keep your account data until you delete your account. In-app notification history records which event, group or person a notice was about, never message text, and is deleted after 90 days. Declined (NO) RSVPs on completed events are deleted after 90 days. Event chats are deleted 7 days after the event. Direct and group chat messages have no time limit: they are kept until they are deleted or their author deletes their account. Cancelled events are deleted 30 days after cancellation. Completed events, with their details, photos, RSVPs, attendance marks and reviews, are deleted 12 months after the event. We keep a text memory of events you hosted or attended (title, dates, type, category and hosts) until you delete your account. Host ratings are lifetime summaries. Attendance reliability covers only the last 12 months: the badge is recounted from the events we still hold, so a missed RSVP stops counting once its event is deleted. The number of events you attended stays an all-time total, and the participation counts on the home page are all-time totals. Device location used for nearby search is never stored on your user profile. Accounts that never accept the Terms are deleted after 7 days. Accounts that accepted an earlier version are never deleted for this reason; they are asked to accept the new one. Date polls: your votes and proposed times are deleted as soon as the poll fixes its date. If you said yes to the winning time and are added to the event, that answer is kept as an ordinary RSVP. A poll that never fixes a date expires once all its times have passed, or 180 days after it was created at the latest, and is deleted 30 days later. Encrypted backups of our database are kept for up to 14 days, so data you delete stays in them until they expire. If we ever restore a backup, accounts deleted since then are deleted again before the app reopens.
• There are no in-app payments or purchases in Party Up.
This notice explains how Party Up uses personal data. It covers the app, the website, the Party Up Telegram bot and the Party Up Discord bot.
The data controller is named at the end of this page. You can reach them at the contact address shown there, or through Send feedback in Settings.
For now, Party Up is run by a private individual, who is the data controller. When a company is set up to run Party Up, the service and the role of data controller will pass to it. We will tell you clearly before that happens. The purposes for which we use your data will stay the same.
Party Up does not collect your email address or phone number. There are no in-app payments. We use no third-party analytics or error-reporting tools, and no non-essential trackers or cookies.
You sign in with Google, Apple, Telegram or Discord. For your account we store:
• Sign-in — the provider you used and a coded form of your provider account id. For sign-in with Google or Apple we do not store the id itself.
• Telegram — if you use Telegram, your Telegram id and username, so the bot can reach you.
• If you sign in with Discord, or link Discord or Steam, your Discord or Steam account id (stored encrypted: Discord to recognise you on Discord, Steam to link to your Steam profile) and your Discord username or Steam name. Others see that name only if you turn on Show to people at my events, and then only the hosts of an event you share (at any time) and its confirmed guests (from 24 hours before it starts until it ends).
• Steam game check — if you link Steam, for a game night about a Steam game we ask Steam whether that one game is in your library. We keep the answer for at most 24 hours and never read or keep your whole library. Only you see your answer; once at least three guests are confirmed, hosts see only how many of them have the game. The count never names anyone, but "0 of 3" or "3 of 3" shows that none or all of them are known to have it, and comparing counts over time can hint at whether a guest who just joined has it; to blunt that, the count is refreshed at most every few hours (an incomplete "At least" count can update sooner). Turn off Check game ownership in Settings to stop it.
• Name — your first and last name, prefilled from the provider and confirmed by you at sign-up.
• Date of birth — required at sign-up.
• Gender — optional: woman, man or other.
• Profile — your picture, bio, time zone and language.
• Terms — which version of the Terms you accepted, and when. No IP address or device details.
• Sessions — for each sign-in, the app or browser, the kind of device, how you signed in, when it started and the last day it was used. No IP address or location. Signing out ends it.
• App settings — which first-time explanations you have already seen.
Your name, date of birth, gender, picture, bio and Telegram id are stored encrypted. Your date of birth and gender are never shown to other people.
Your name, date of birth and gender can be set only once. To correct them, contact support. We answer within a month.
You can unlink any account except your last way to sign in. When you unlink one, we keep a coded form of its id for 12 months, only so that a suspended account cannot come back with it.
An account needs your name and date of birth. Without them you cannot use Party Up. Gender is optional. Without it, you cannot join events a host has limited by gender; the app asks you once if you try.
If you sign in with Google, Telegram or Discord and have no picture of your own, our server copies your provider picture once. We keep our own copy, so others never load it from Google, Telegram or Discord.
Until the copy is made, we hold the picture's web address encrypted, normally for seconds to minutes. Accounts that never accept the Terms are deleted after 7 days.
We also record the day you last used Party Up: in the app, on the web, or by answering through the Telegram or Discord bot, including Discord voice check-in.
When you host, we store the event details you enter, its hosts and co-hosts, and co-host invitations. When you reply, we store your RSVP (yes or no) and any guests you bring.
A host can let the group vote on a date before fixing it. We store the event draft (with the exact address encrypted), the times people propose and each yes or no answer. Anyone with the poll's link can see the poll. When you say yes to a time, everyone signed in with the link sees your name and profile photo next to it, and the poll's creator also sees who said no. When the date is fixed, the votes and times are deleted, and people who said yes to the winning time and are added to the event keep an ordinary RSVP.
The exact address or map pin is stored encrypted. It is shown only under the event's reveal rules, for example to confirmed guests near the start time. Others see an approximate public location.
An online event's join link is handled like the exact address: stored encrypted, shown to hosts and to confirmed guests from 24 hours before the start until the end, and deleted 30 days after the event ends. When a host searches for a game, our server sends the search text to IGDB; no identifier of yours is sent.
When a host searches for an address, our server sends the search text to Google Places and Geocoding. No identifier of yours is sent.
Your device location is used only when you ask for nearby events or open a map. It is sent with that search and is not stored.
If you choose an area (a town, neighbourhood or postcode) for nearby searches, the app keeps its place name and an approximate point on your device only. It is cleared when you sign out or when another account signs in on this device, and it is never saved in your account.
To suggest places near you, our server may send Google Places only the centre of a 0.1° cell (roughly 10 km across) around a nearby group, a chosen area or a device position you already allowed, never your own position. This happens only while the feature is switched on. No identifier of yours is sent.
Hosts can tag an event with allergens or pets. These tags describe the event, not any person. We do not collect health data about you.
A host can ask for an event to be listed publicly. We review the listing before it is shown, to keep public listings to genuine events. The review is not a safety or legality check.
When an event ends, we keep a short text memory for each host and guest: title, dates, type, category, group and hosts. It stays until you delete your account.
A host can open an event to women only, men only, an age range, or a balanced mix of women and men.
When you join such an event, our server compares your stored gender and date of birth with the rules. It keeps only the outcome, never the values.
On an event with gender rules, we note which half you took, women or men. If you bring guests, you tell us each guest's half. A guest's half is stored encrypted.
Hosts see only the rules and, on a balanced event, how many women and men have joined. The app never shows anyone's gender or half.
On a balanced event, nobody sees who is waiting, not even the hosts. The counts change by one when someone joins or leaves, so a close watcher may sometimes guess a person's half.
The halves are deleted 30 days after the event ends. Notices about new events skip people whose stated gender or age does not meet the rules.
After an event, hosts can mark each guest as arrived or absent. From these marks we count how often you completed an event, left late or did not show up.
If a host turns on automatic check-in for an online event, our Discord bot also notes when confirmed guests who linked Discord are in the event's voice channel during the event. After 5 minutes there in total you are marked as arrived — never absent — unless a host already marked you, and a host can change it. The event page, the invite-link page and the event's post in Discord say so before you join. The bot keeps this presence until one hour after the event ends, and reads nobody else's.
You see all of your own counters. Others see only how many events you attended, a missed count, and whether any no-show exists. They never see late leaves and no-shows separately.
Platform admins see everything, so they can make corrections. Each correction is logged with a reason.
Late leaves and no-shows count for about 12 months, until their event is deleted. The number of events you attended is an all-time total.
If a mark is wrong, tell us through Send feedback in Settings or at the contact address. We review it and correct the record if it is wrong.
The counters are profiling. Section 15 explains what this means for you.
Chat messages (direct, event and group) are stored encrypted. Only the people in the chat see them. In event chats, admins of groups the event is shared in can read them too. If someone reports a message, platform moderators can read a saved copy of it and of up to three messages before it (see section 8).
Group admins, moderators and event hosts can delete messages in their chats. Deletions by group admins are logged.
We store who you follow, your groups and roles, join requests, invite links and group bans. A group ban records who was banned, the group admin who banned them and when. Group actions, including removals and bans, are recorded in a group audit log.
If a group's admins turn on “Show in search engines” (available only for groups listed on Discover groups), search engines such as Google may index the group's public page: its name, description, neighbourhood, cover photo, and the titles and dates of its upcoming events. The page has no member names. It stops as soon as the admins turn it off or the group is no longer listed; search engines may take a few weeks to drop pages they already stored.
You can review events you attended with stars and a comment. Hosts' ratings are shown to others. Reviews of invite-only events are shown only to people who can open that event.
Photos you upload become your profile picture or an event cover. They are stored with our hosting provider.
We keep an in-app notification history. It records which event, group or person a notice was about, never names or message text.
For push notifications we store your Expo push tokens (up to 10) and browser push subscriptions, encrypted. A push may include an event name or a short chat preview, which we do not store.
Calendar sync in the phone app is optional. It adds events you are confirmed for to a calendar on your device. Party Up never receives your calendar data.
If you use the Telegram bot, it receives your Telegram id, username, chat id and the commands you send. It can message you and post events in linked Telegram groups.
We never send chat messages to Telegram. Group posts can show participants' and guests' names. Messages already delivered in Telegram, such as an event address, stay there after we delete our copy.
If a group connects a Discord server, our Discord bot posts the group's events there: the title, times, description, game, seat count and the first names of participants and guests, as Telegram posts do. Each posted event also appears in the server's Events list, with no participant names.
When you answer from Discord, the bot receives your Discord user id, the server and channel, and your Discord display name. It uses your Discord id only to find the Party Up account you linked. With Discord linked, we can also send your notifications as Discord messages, which needs your Discord id. Server ids are stored encrypted.
In a connected server, Discord also tells the bot who joins or leaves its voice channels. The bot never reads, stores or logs this, except for confirmed guests of an event with automatic check-in, which it uses only as section 5 explains. It may hold it in memory for a moment while it reconnects to Discord.
You can report people or content. We store the report, with its details encrypted. If you report a chat message, the report also keeps an encrypted copy of that message and of up to three messages before it, with the names shown in the chat and the times. The copy stays with the report after the message or the chat is deleted, and goes when the report does. If you report a review or a group, the report keeps an encrypted copy of the review (its stars, text, event title, the reviewer's name as shown and its date) or of the group's name and description. It is kept and deleted the same way. Only platform moderators can read the copy, and it is not included in Download my data.
When we suspend an account, decline a public listing or dismiss a report, we record the decision, the reasons and any appeal. Decisions are taken by people.
The affected person receives a statement of reasons. A reporter learns only the outcome, never the sanction or the facts.
You can appeal a decision in the app within 6 months. A person reviews every appeal.
If a suspended account is deleted, we keep a coded marker of each of its sign-in accounts for 12 months, with no user id. It stops the person signing up again with them.
Lifting or reversing a suspension also deletes its markers.
Platform admins can see counts of users by gender and age band. The counts cover all users and people who attended an event in the last 90 days.
Any count from 1 to 4 is shown as "<5". The counts name no one and are never public. They are cached for one hour.
The message you send through Send feedback is stored encrypted; it goes with a category, your platform, the app version and language, and the screen you sent it from (its path only, never what you searched or typed). A message about an attendance mark also names the event.
To protect the service, we use your user id or IP address to limit request rates. We keep logs, traces, metrics and audit logs of privileged actions on our own servers.
We keep encrypted database backups in a second EU location for 7 to 14 days.
The GDPR requires a legal basis for each use of data. Some bases below are proposals still under legal review; we say so where that applies.
• Account, sign-in, names and Terms record — performance of our contract with you (Art. 6(1)(b)).
• Date of birth and the 18+ check — proposed: our legitimate interest in keeping Party Up for adults (Art. 6(1)(f)). Under legal review.
• Gender — under legal review: legitimate interest (Art. 6(1)(f)) or your consent (Art. 6(1)(a)), since giving it is optional.
• Under-18 markers — proposed: legitimate interest (Art. 6(1)(f)). Under legal review.
• Events, RSVPs, chat, groups, follows, notifications and writing reviews — contract (Art. 6(1)(b)).
• Event gender and age rules — proposed: contract (Art. 6(1)(b)), as you ask to join on those terms. Legitimate interest is the alternative. Under legal review.
• Event memories — contract or legitimate interest (Art. 6(1)(b) or (f)). Under legal review.
• Public-listing review — legitimate interest in keeping public listings to genuine events (Art. 6(1)(f)).
• Reliability counters — legitimate interest in helping hosts plan around who will come (Art. 6(1)(f)).
• Publishing host ratings — legitimate interest in helping guests choose events (Art. 6(1)(f)).
• Group audit log — legitimate interest in group admins' accountability (Art. 6(1)(f)).
• Group removals and bans — proposed: the legitimate interest of group admins in deciding who belongs to their group (Art. 6(1)(f)). Under legal review.
• Statements of reasons for moderation decisions — legal obligation under Art. 17 of the Digital Services Act (Art. 6(1)(c)).
• Reports, other moderation records, appeals and ban markers — legitimate interest in enforcing the Terms and protecting users (Art. 6(1)(f)).
• Retired sign-in markers — legitimate interest in stopping ban evasion (Art. 6(1)(f)).
• Steam game check — legitimate interest in helping a game night work, started by your own linking of Steam (Art. 6(1)(f)). You can turn it off at any time.
• Automatic check-in from Discord voice — legitimate interest in recording attendance without the host marking everyone by hand, with notice on the event page, the invite-link page and the event's post in Discord before you join (Art. 6(1)(f)).
• Admin statistics by gender and age — under legal review.
• Product feedback — legitimate interest in improving Party Up (Art. 6(1)(f)).
• Answering your data-protection requests — legal obligation (Art. 6(1)(c)).
• Security, logs and backups — legitimate interest in keeping the service secure and available (Art. 6(1)(f)).
We may refuse to erase moderation records and ban markers while they are needed to establish or defend legal claims (Art. 17(3)(e)).
Inside Party Up, other people see what each feature needs:
• Other users — your name, picture and bio, and the attended and missed counts on your profile, and, for the confirmed guests of an event you share, your Discord or Steam name if you chose to show it.
• Hosts and co-hosts — who replied to their events, and the attendance marks they record, and your Discord or Steam name if you chose to show it.
• Group admins — members, join requests, the people banned from their group, and the chats of events shared in their group.
• Platform admins — what they need to moderate, correct records and see the statistics above.
Hosts, co-hosts and group admins may use what they see about you only to run their events and groups. Our Terms forbid them to copy it out of Party Up or use it for anything else, such as advertising, unless they have their own legal basis. If one of them does, they answer for it as a controller in their own right; tell us and we can act under the Terms.
Outside Party Up:
• OVHcloud (OVH SAS, France) — our processor for hosting, photo storage and backups, all in the EU.
• Expo (650 Industries, Inc., USA) — our processor for mobile push. It receives your push token and the notice text.
• Browser push services, such as Google, Mozilla or Apple — chosen by your browser, not by us. They receive an encrypted notice.
• Google, Apple, Telegram and Discord sign-in — independent controllers under their own terms, for the sign-in you choose.
• Steam (Valve) — an independent controller. When you link Steam it confirms your Steam ID to us, and our server reads your public Steam name and, for a game night about a Steam game, whether that one game is in your library. We send no identifier of ours beyond your Steam ID.
• Google Places and Geocoding — an independent controller. It receives address searches and coordinates, with no identifier of yours.
• IGDB (Twitch Interactive, Inc., USA) — our server sends it the text of a host's game search, to find the game and its cover. No identifier of yours is sent, so it receives no personal data about you.
• Google, Telegram and Discord picture servers — our server fetches your provider picture once, sending no identifier of ours.
• Telegram — an independent controller for its platform. It carries bot messages and group posts.
• Discord — an independent controller for its platform. It carries bot posts, server events and bot messages.
Some recipients are outside the European Economic Area:
• Expo — in the USA. Its privacy policy states that it is certified under the EU-US Data Privacy Framework.
• Google — its terms use standard contractual clauses with Google Ireland. Google LLC is certified under the Data Privacy Framework.
• Telegram — says it stores EU users' data in the Netherlands, and uses standard contractual clauses for group companies outside the EEA.
• Discord — based in the United States; it relies on standard contractual clauses for EU users' data.
• Steam (Valve, USA) — an independent controller. Its own terms apply.
• Sign-in providers and browser push services — their own terms apply. You choose the provider and the browser.
• Account and profile, including date of birth and gender — until you delete your account.
• Accounts that never accept the Terms — 7 days.
• Exact address, map pin, guest names, private-invite labels and gender halves — 30 days after the event ends.
• Cancelled events — 30 days after cancellation.
• Completed events, with photos, RSVPs, attendance marks and reviews — 12 months after the event ends.
• Declined (no) RSVPs on completed events — 90 days.
• Date polls — votes and proposed times until the date is fixed. A poll that never fixes a date expires once all its times have passed, or 180 days after it was created at the latest, and is deleted 30 days later.
• Event chats — 7 days after the event ends, or at once if it is cancelled or deleted.
• Direct messages — no time limit. They stay until the author deletes them or their account.
• Group messages — no time limit. They stay until the author, a group admin or a moderator deletes them, the author's account goes, or the group is deleted.
• Reliability counters — late leaves and no-shows for about 12 months. The attended total is all-time. Corrections stay as an audit trail.
• Host ratings — reviews for 12 months. Their stars then join an anonymous lifetime total.
• Event memories — until you delete your account.
• Notification history — 90 days.
• Push tokens — up to 10 per account. Signing out on a device deletes that device's token; tokens the push service rejects are deleted.
• Sign-in sessions — 30 days after they end (sign-out, expiry, or sign-out from another device).
• Rejected group join requests — 90 days. Closed group invite links and the group audit log — 365 days.
• Group bans — until the ban is lifted, the group is deleted or the banned account is deleted. If the admin who banned deletes their account, the ban stays without their name.
• Reviewed reports and feedback — 90 days after review, longer while a dismissed report can still be appealed. Pending ones stay until reviewed. A reported chat message and the messages copied with it go with the report. A reported review's or group's copy goes with the report too.
• Moderation decisions and appeals — 12 months after the decision or its reversal. Active suspensions while they last. Never deleted while an appeal is pending.
• Ban markers — 12 months.
• Retired sign-in markers — 12 months.
• Steam game check answers — 24 hours at most (one hour for private game details, five minutes after a Steam error).
• Voice presence for automatic check-in — until one hour after the event ends; the attendance mark it leads to is kept like any other.
• Under-18 markers — until the 1st of the month after the person's 18th birthday.
• Profile corrections and other audit logs — 365 days.
• Admin statistics — one hour in cache.
• Failed system messages — at most 7 days. Message references — 90 days.
• Backups — 7 to 14 days.
• Deletion record — 30 days, holding only an account id and a time, so deletions can be redone after a restore.
When you delete your account, we delete or anonymise your data at once. Your chat messages are replaced by "Message deleted".
Groups you created pass to another member, or are deleted if nobody else is in them. Upcoming events with no other host are cancelled, and their guests are told.
A few traces remain. Your stars stay in hosts' anonymous rating totals. An event's title stays in other participants' memories. Notifications already delivered cannot be recalled. A message of yours copied as context into a report someone else filed about another person keeps its text and your display name until that report is deleted.
A sign-in session that is already open can stay valid for up to 15 days, but it no longer finds an account.
• Access and portability — use Download my data in Settings to get a copy of your data as a file. The file leaves out the copy of chat messages saved with a report, because it holds other people's messages. It also leaves out the copy of a review or a group saved with a report.
• Rectification — edit your bio and language in your profile. For your name, date of birth or gender, contact support. For an attendance mark, use Send feedback.
• Erasure — use Delete account in Settings. This works even while your account is suspended.
• Restriction — ask us to limit how we use your data, for example while we check a correction.
• Objection — you can object to uses based on legitimate interest. See section 14.
For any request, use Send feedback in Settings or write to the contact address at the end of this page. We answer within one month.
You can complain to a data protection supervisory authority. In Italy, this is the Garante per la protezione dei dati personali. You can also turn to the authority of your country of residence or work.
Where we rely on legitimate interest, you have the right to object at any time, on grounds relating to your particular situation.
This covers, for example, the reliability counters, public-listing review, published host ratings, group audit logs, moderation records, feedback, security logs and backups.
We then stop, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or need the data for legal claims.
The app has no objection button yet. Send your objection through Send feedback in Settings, or to the contact address at the end of this page.
The reliability counters are profiling: they evaluate how reliably you attend. No part of Party Up restricts anyone automatically based on them.
Hosts can ban a person from their own events, and group admins decide join requests and may remove or ban members. They may look at the counters, but these are human decisions.
Joins to events with gender or age rules are checked automatically. If your stated gender or age does not meet the host's rule, the join is refused.
A refusal affects only that event. Nobody reviews it by hand. If your stored data is wrong, ask support to correct it.
Moderation decisions and appeals are decided by people.
Party Up is only for people aged 18 or over. We check this with the date of birth you give. We do not check it against any document.
If a date of birth shows someone is under 18, we close and delete the account at once.
For each of its sign-in accounts, we keep the provider, a coded marker, when it was made, and the day the person may join again. Nothing else is kept.
That day is the 1st of the month after the 18th birthday, so it reveals the birth month. The marker is deleted once that day has passed.
We update this notice when the way we use data changes. The current version is always on this page.
Party Up sets no cookies and uses no analytics, advertising or tracking tools. The website and the app keep only a few items on your device that the service needs to work. The law does not require consent for these, but you have the right to know what they are:
• Your sign-in session — in the browser's local storage on the web, in the device's secure storage in the phone app. Signing out deletes it.
• Your settings — language, theme, in-app sounds, and which prompts you have dismissed or already answered, such as the offer to turn on notifications.
• A sign-in in progress — while you sign in or link an account with Google, Apple, Telegram, Discord or Steam, the security codes of that sign-in and the page to return to. On the web, this sits in the tab's session storage, which the browser clears when you close the tab. On the web we also note there whether you arrived from a Telegram link.
• Calendar sync in the phone app — whether it is on and which calendar on your device it uses.
None of these items is shared with anyone else. Only the sign-in session reaches our server, to prove it is you. You can delete them all by clearing the site's data in your browser or uninstalling the app.
Luca Santalucia is the data controller for Party Up.
Questions? Contact us at support@party-up.site
The summary above is a quick guide. Where it and the full privacy policy differ, the full policy applies.