PartyUp
Bitte melde dich an.
Kein Konto? Neuen Namen und Password eingeben, dann Anmelden tippen – ist der Name frei, wird dein Konto erstellt.
Personalisierte Werbung ist aktiviert.
GPS ist aktiviert.
Block users completely to stop seeing messages and events from that user.
Password wurde erfolgreich geändert.
Kein Standort - keine Verbindung oder keine
Onlinezahlung ist grade nicht möglich. Bitte versuche es später erneut.
Noch keine Follower.
Streak: 0
Eingehender Anruf
Es klingelt…
Gerade keine Freunde auf dieser Party.
Link kopiert
An Chatpartner senden
Noch keine Chatpartner. Öffne zuerst einen Chat.
Share moment
Vorschau
Agree to cookies by choosing Accept below, or by any other action on this page. Otherwise close it. This also lets PartyUp read the contacts on this device to find friends, recognize mutual friends, and make more suggestions. The privacy policy is available at the following link:
As of October 29, 2026
Service: PartyUp (web application / Progressive Web App)
Public domain (planned or productive): partyup.pro
This Privacy Policy informs you in accordance with Articles 13 and 14 of Regulation (EU) 2016/679 (General Data Protection Regulation – "GDPR”) as well as the additional applicable regulations Federal Data Protection Act (BDSG) and – where relevant – the Telecommunications Digital Services Data Protection Act (TDDDG, formerly TTDSG) on the processing of personal data when using PartyUp. To the extent that provisions of the former TTDSG continue to apply in terms of content, they are to be read as provisions of TDDDG.
The person responsible within the meaning of Art. 4 No. 7 GDPR is the operator of the respective PartyUp instance:
[Full name/company of the person responsible]
[Street, house number]
[ZIP code city, country]
Email: [datenschutz@example.de]
Telephone: [optional]
Person(s) authorized to represent you: [if legal entity]
If a data protection officer has been named (Art. 37 GDPR), you can reach him at: [Name and contact details of the data protection officer – if available].
Note for the operator: The above placeholders are before productive operation to be replaced completely and truthfully. Without specifying the identity and accessibility of the Those responsible have not fulfilled their obligation to provide information pursuant to Article 13 Paragraph 1 Letter a of the GDPR.
PartyUp is a platform for presenting and organizing parties, for communication between Users (chats, comments), for rating parties, for the optional use of location functions, to use audio/video calls, route planning (including navigation to parties and Evening routes from chat plans) for creating shared evening plans in private chats Multilingual interface (including optional machine translation from third parties Party descriptions in the language of the viewer), for private caching Experience drafts, saved to the account-related watch list Shorts paid extensions (Pro, Ad-free, paid party release, an account balance called PartyCash, and – when a host offers it – an online ticket for that one party) as well as for Display and billing of advertising. Users can optionally add an email address to their account (including for password recovery and, when an address is stored, delivery of a purchased ticket). Buying a ticket does not require an email address. Users can use a Secret mode, which increases the visibility of your own Content temporarily restricted for other users (can be activated in the Settings and in Account deletion dialog; see § 8, § 23). PartyUp personalizes the order of Parties in the area list and the play of Shorts based on interaction, popularity, Time, place and - if available - friendship or situation signals as well as from the Anonymous groups of two derived from user and behavioral data (see § 18.4). PartyUp consciously combines the behavior in the app (especially Shorts and party detail) with actual party behavior in the real world (including saving, route/navigation, GPS Visit): Signals from one area can improve recommendations in the other area (Cross-Feature Learning). There are real interactions with the function displayed Priority over preferences derived only from the other area (see § 18.4). As far as GPS presence is shared, PartyUp can show registered chat partners which friends are currently at a party, and one expected remaining length of stay treasure; the model learns from completed GPS stays and continually improves (see § 14.1, § 18.6). Users can on site moments (Photos/Videos) record and use the button "Share moment” publish; thus grant you consent to the public display, among other things. in the party media gallery and in Shorts feed (see § 9, § 12). Registered users can also publish general shorts that are not party moments and are not attached to a party. In Settings and under Your parties they choose whether the general Shorts feed shows all shorts, only original party moments, or lets Auto decide from the situation (see § 9). Friends and people who follow the author can see those published moments from the last 48 hours again as a story (see § 9). If the user allows it, PartyUp accesses the contacts stored on the device in order to find friends who already use PartyUp, to suggest friends more accurately, to recognize mutual friends more reliably, and to make further suggestions (see § 14.4). PartyUp distances itself from the content and circumstances of such Publications (see § 29). Party operators can optionally connect live cameras; Live image, live shorts and live image analysis as well as ongoing operation during the registered use of PartyUp are described in § 9a. Party operators can publish Crew Rewards (Crewcards); after publication they must honour the promised perk under all circumstances and provide it on the release page (see § 9b). A host can mark a party as private, so that only the host and the friends they select can see it, and those friends receive one chat invitation (see § 9, § 11.4). Additionally builds PartyUp parallel and ongoing, completely anonymized preference profiles as general ones wealth of experience; these only serve as a starting hypothesis for the assessment of new ones or little-known users and remain separate from the personal user profile (see § 18.5). Additionally, PartyUp decides Depending on the situation, whether and which advertising is shown in optional advertising spaces (see § 16); You can display personalized advertising under Settings → Advertising deactivate (then advertising remains context-related). PartyUp captures aggregated Usage and activity metrics (including a protected statistics interface /api1), stores payment data that is legally required to be retained, Billing and contract proofs are permanent and application-side protective measures are implemented abusive network requests. Users can use the home page to personalize Suggestions and wishes to the Operators send by tapping the font "PartyUp” (often displayed as "PARTYUP”) in the top left (see § 18.7). Data transmitted via /api1 can be controlled by the person responsible and be stored permanently by the authorized user (see § 18.2, § 21.1). This explanation describes the processing of personal data that takes place, the legal basis, Storage periods, recipients, rights of those affected and other information required by law.
Insofar as the terms "personal data”, "processing”, "data subject”, "Controller”, "processor” or "consent” are used, the following apply Definitions of Art. 4 GDPR.
In particular, the following categories of personal data may be processed within the framework of PartyUp:
partyup-last-geo, pseudonymous activity identifier, local identifiers for reconnecting a live camera);Neither email address nor telephone number are required for standard registration. One You can optionally store your email address in the Settings (among other things password recovery). No separate email address is collected for advertising; Stream and billing details appear in the app. Payment details (e.g. card details). processed via the payment service provider Rapyd.
Unless otherwise stated in the following sections, we base processing on:
Legitimate interests within the meaning of Article 6 Paragraph 1 Letter f GDPR are in particular: Provision a functioning community platform, protection against misuse, ensuring IT security as well as the traceability of technical faults.
PartyUp is operated as a server application. Unless otherwise stated, personal data will be used described - stored on the server operated or commissioned by the person responsible (including structured data sets in file or database form, activity and statistics storage and uploaded media files). With online hosting, this data remains on the Server or the processor and are available regardless of whether an individual The operator's device is offline.
If the person responsible uses a hosting or infrastructure service provider, this provider acts usually as a processor in accordance with Art. 28 GDPR. In this case there is an order processing contract to complete; The specific recipients should be added here:
[Name of host/cloud, address, place of data processing]
For certain functions (including your own parties, chats, comments, account management, subscriptions, Advertising) a user account is required. Sign-in and registration use the same form (username and password) under Settings. When registering and logging in, the following are processed:
Registration via the login form: If the entered username is not yet assigned, PartyUp does not immediately create the account. Instead, a short-lived pending registration is stored in the session (username, password hash, expiry – currently about 10 minutes). The user confirms with "Create account”. Cancelling discards the pending data. If the name is reserved by the system (currently "anonymous”) or already taken, no account is created.
Feedback on failed sign-in: If the username exists but the password is incorrect, PartyUp highlights the password field. If the username is not found or is reserved, the username field is highlighted. This processing shows whether a chosen name is already assigned; it is used only to complete sign-in or registration on the same form. Passwords are not stored in plain text and are not shown again after a failed attempt.
After successful login or registration: The session is regenerated (see below). The user is taken immediately to the home page in the logged-in state (personal greeting, account-related navigation). The user-interface language is the language stored on the account if the user has set one in Settings; a language used only in guest mode does not overwrite that account setting (see § 14.2). Sign-in and registration screens themselves do not show advertising (see § 16.2).
Registered users can change their password under "Password & Security”. This will be the case The previous password is checked and the new password is saved again only as a hash.
If an email address is stored in the account, a time-limited email address can be entered using "Forgot password”. Confirmation code via email via Brevo (transactional mail API, TLS) be sent (sender noreply@partyup.pro; see § 16.4 / § 19.2). The code or a corresponding hash is only stored on the account for a short time and after successful use or expiration invalid. The emails are written in the app language set by the user and indicate that no reply should be sent to the sender address. Without deposited This recovery is not possible for the email address.
Purpose: Identification and authentication, providing personalized Features, protection against unauthorized access, optional account recovery.
Session function (technical): After successful login or registration
The server session is regenerated and the user ID and a timestamp of the authentication
(authenticatedAt) saved. The authenticated session is subject to a
absolute maximum term currently 7 days from this point in time; a mere cookie refresh
does not extend the login term beyond this absolute (see § 17.1). Session data
are stored on the server side in a session store (SQLite); expired sessions
cleaned periodically. If you log out or delete your account, the session will be destroyed.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR; for sending emails as part of the Password recovery also Art. 6 Para. 1 lit. b GDPR.
The user name "anonymous” is blocked by the system and cannot be used as an account name. This name is reserved for displaying anonymized comments after account deletion (see § 23).
Registered users can change their username in the Settings. The new name must be between 2 and 40 characters long, must not contain spaces, must not be reserved by the system (currently "anonymous”) and must not already belong to another account. Changing only the capitalization of the same name is allowed.
The new name replaces the previous one. PartyUp does not keep a separate history of earlier usernames. The replacement is written to the account, the public handle in the form "@PartyUp.[username]”, the current session, parties created by the user, the author name on that user's media, chat participant and sender names, mentions of the previous handle in chat texts, the display name stored with block entries, and the name on stored user feedback. Share graphics of the user's own parties are generated again so that they show the new name.
Purpose: keeping the public identity the user has chosen.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR.
After logging in, a public handle in the form "@PartyUp.[username]” as well as a associated QR code can be displayed, which refers to the user profile or a user-related link refers. The purpose is to be discoverable and contactable within PartyUp.
Users can optionally store a profile picture on the account. The picture is shown together with the username, including in chats, party cards, the friends list and stories. Uploading a new picture replaces the previous file. If no picture is stored, the first letter of the username is shown instead. The picture is removed when the account is deleted (see § 23).
Purpose: recognizable profile within PartyUp.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR.
Users can have one Secret mode activate or deactivate – in the Settings as well as in the account deletion dialog on the home page (switch under the information text; see § 23). Activation via the delete dialog saves the same account status as the Activation in the Settings and closes the dialog; There is no account deletion instead. Deactivation can be done using the same switch in the delete dialog and at any time in the Settings possible.
As long as the Secret mode is active, PartyUp saves the status on the account and applies server-side Visibility filter on: your own parties do not appear in other people's feeds/lists; Direct chats with the affected user will be hidden from others; Party comment chats for your own parties cannot be found by third parties; Proximity/presence notifications to chat partners are not triggered; Your own advertising content will be removed from the playout pool. They remain for the user himself Functions basically usable. There is no physical deletion of the content – after deactivation they are visible to others again. The Secret mode is one reversible restriction of visibility and no alternative to deletion under data protection law according to Art. 17 GDPR; the irrevocable account deletion remains separate via the same dialog or the intended deletion function is possible and requires a two-stage confirmation (§ 23).
While Secret mode is on, other people also do not see the ON FIRE badge on the profile (see § 11.3). The person themselves can still see it.
Purpose: Protection of privacy and against unwanted discoverability or visibility within the platform (including situations where users want to avoid social conflict or bullying) without deleting their own data.
Legal basis: Art. 6 Para. 1 lit. b GDPR, supplementary Art. 6 Para. 1 lit. f GDPR (Interest in usable social/community functions and in protecting the user's privacy from unwanted visibility). The status "Secret mode” is used as the inventory date on the account stored (see § 4, § 21.2).
Registered users can create, edit and delete parties. In particular, processed: name of the party, optional location/area information, geo-coordinates of the party on the Map of set location, description, external link, date/recurrence information, media attachments as well as assignment to the creating user account (user ID and user name). Additionally can Payment metadata is stored for publication (e.g. amount paid, Rapyd checkout session).
The event location is primarily determined by coordinates set by the user on a map. An optional search field is for orientation purposes only (area and address suggestions); the selection of a suggestion does not set a location marker, but rather focuses the map.
Without an active Pro subscription, publishing certain schedule periods may be subject to a charge (currently one-off: €1 daily, 75 cents weekly, 55 cents monthly, 50 cents annually; fixed data free of charge). With Pro you can have corresponding parties without this Publishing fee go live. Unpublished drafts can be saved on the server remain until they are paid for, published or deleted.
Party content may be displayed to other users of the application (including indication of the Creator in the form "@PartyUp.[username]”), unless the host has limited that party to selected friends (private party, below). This also includes the Shorts feed (vertical sequence of party and experience media) as well as the display of how many have been released Chat partners are currently at a party ("Friends” button on party cards and in Shorts; the list of names with expected remaining time only for registered users, see § 18.6).
Registered users who are physically located at a published party location after GPS verification stop, can find one there moment (Photo or video; in the application too referred to as an experience) and assign it to the party. The recording sets GPS sharing and the server-side presence test is required (see § 14.1). In Secret mode the sharing of Moments prevented. Filters and automatic image enhancement can be used before sending applied on the client side and burned into the uploaded original (see § 12).
Publication and consent: Shared moments become published. They are assigned to the party (uploader ID and User name, timestamp, file metadata) and can be used by other users in the Party media gallery and appear in the Shorts feed. By pressing the button "Share moment” the user gives express consent (Art. 6 Para. 1 lit. a GDPR) in this publication and the associated one Processing. Without this actuation, the moment will not be published. The user At the same time confirms that he has the necessary rights and - to the extent that required – has obtained the consent of the people depicted. PartyUp is exclusively technical service provider and distances itself from the content, recording context and all circumstances that arise in connection with moments (see § 29).
Friend stories: Moments that were published in the last 48 hours can be shown again as a story to the author's chat partners (friends) and to users who follow that author. A story is not a second copy of the file. It is a view of moments that are already published, with the photo or video, an optional caption, the party name, the time, and the author's current username and profile picture. At most 20 items are shown. Secret mode, a block between the two users, and unpublished or expired parties hide the story. Opening a story stores on the server the time at which that viewer last opened that author's story (viewer user ID, author user ID and timestamp), so the highlight can remain until the story has been opened. When that viewer's Shorts content mode includes general shorts, a general short from the last 48 hours can appear in the same story (see below). Friends and followers can receive an in-app notice and, if push permission was granted, a web push that a new story is available (see § 17.4). The notice contains the author's current username.
Following: A registered user can follow another user or a party location. PartyUp stores the follower's user ID together with the followed user or the location (label and, if available, approximate coordinates) and the time of the follow, so that new parties and new stories can be shown to that person. Unfollowing removes that entry.
Moment streak: When a user publishes a moment, PartyUp stores a streak count and the time of the last share for that user. A further share within 7 days continues the count and moves the window forward. After 7 days without a share, the displayed streak returns to 0. The count can be shown with the profile.
Legal basis for stories, following and the streak: Art. 6 Paragraph 1 Letter b GDPR. The publication of the underlying moment remains covered by the consent in this section (Art. 6 Paragraph 1 Letter a GDPR). The seen timestamp is stored only so that the viewer can tell which stories are still new.
Private experience designs: Registered users can have a recorded experience first save it as a private draft without pressing the "Share moment” button. There File and metadata (including assignment to the user account and the party, timestamp, MIME type, optional filter identifiers) stored on the server side. Such drafts do not appear in the public party media gallery and not in the public Shorts feed; they are dem saved user in a private folder or feed. The publication and the The associated consent (Art. 6 Para. 1 lit. a GDPR) only takes place with the later pressing "Share moment”. The Secret mode is for saving drafts prevented. Legal basis for private temporary storage: Art. 6 Para. 1 lit. b GDPR.
Saved Shorts: Registered users can use Shorts in an account-related Save to watchlist and watch again in a private feed. References to are saved existing party/experience media (identification, party reference, time of storage), not one additional public display. Other users do not receive any new visibility. Legal basis: Art. 6 Paragraph 1 Letter b GDPR.
Saved parties: A registered user can save a party to a private list and open that list again. PartyUp stores the party identifier and the time it was saved, not a further public copy of the party. Other users do not see that list. A successful ticket purchase adds that party to the same list (§ 15.1). Removing the save, or deleting the account, removes the entry. Legal basis: Art. 6 Paragraph 1 Letter b GDPR.
General shorts: A registered user can create a short that is not a party moment and is not assigned to a party. In the application this is "Short erstellen", reached with the button "+ Short +" under Your parties. The user records or uploads one photo or video, may add a short caption, and publishes it. PartyUp stores the file, the uploader's user ID and current username, the time, the MIME type, an optional caption, an optional display filter applied on the device before upload, and any codes the device recognized in the picture (for example a QR code). A published general short can appear in the general Shorts feed when the viewer's content mode is "all" or when Auto has selected that feed. It is not placed in a party gallery. Friends and followers can also see it in the author's story for 48 hours when that viewer's feed includes general shorts. Secret mode blocks publishing and blocks saving a draft. The user can first keep the recording as a private draft without a party; that draft is not public (see private experience drafts above). At most 200 general shorts are kept per account; files beyond that limit are deleted. Legal basis: Art. 6 (1) (b) GDPR for providing the feature, and Art. 6 (1) (a) GDPR for publication, because the short becomes visible to other users only when the user publishes it.
Shorts content mode: Under Settings → Shorts and under Your parties a
signed-in user chooses what the general Shorts feed shows: party (only
original party moments; this is the stored default), all (party moments and
general shorts), or auto. The choice is stored on the account and in the
cookie partyup_partys_content_mode (see § 17.5). If the user explicitly selects
party or all, PartyUp may store that choice together with a short situational note so that
Auto can later prefer the feed this user chose in a similar situation. The note contains
whether a party location was detected, a time-of-day bucket, weekday or weekend, a rough
location cell (about 0.1 degree), an activity bucket, a heartbeat-cadence bucket, the
anonymous group of two already described in § 18.4 (g0 or g1,
without a gender name), and a short intent label. Private chat texts are not read for this.
At most 64 such notes are kept per account. Separate from the account, PartyUp keeps
aggregated counts for similar situations and for anonymized preference profiles (§ 18.5),
without the user ID. Before any personal notes exist, Auto starts with all shorts while a
party location is detected, and with party moments otherwise. Legal basis: Art. 6 (1) (b)
GDPR for storing and applying the mode the user selected, including the situational notes
that exist only to carry out Auto; Art. 6 (1) (f) GDPR for the aggregated counts without a
user ID. The personal notes are deleted with the account (§ 23). The aggregated counts have
no personal reference and can remain.
Displaying party descriptions: For multilingualism, PartyUp published party texts (especially descriptions) in the surface language of the machine translated by the viewer. For this purpose, the relevant text excerpts are used PartyUp server transmitted to external translation services and cached results (see § 19.11). Party names are not machine translated.
For sharing parties, PartyUp can choose from the existing party details and media Generate prepared share kit graphics (e.g. formats for Instagram stories/posts, WhatsApp, Posters, QR codes and links, possibly in several versions). Function: The Generation takes place on the server side (image processing, including with an image pipeline and QR code generation) and places the files under the party media; they will be on the Detail page below Share kits provided. In terms of content, they correspond to those already published Party information and, if necessary, a cover image. Users can download them or use the pass on the end device's native sharing function (if available); which apps or The operating system controls the contacts selected. That share action does not hand PartyUp the device address book. Access to device contacts for finding and suggesting friends is separate and is described in § 14.4. The share assets are removed with the party or when the account is deleted.
Search information or map retrievals can be used for the area suggestion function and map display external geoservices are transmitted (see § 19).
Optionally, up to four can per party Live cameras be connected (device's own front camera, connection or WLAN/LAN). function, data processing, Role distribution, distancing and duties of the party operator - including Installation regardless of the connection route - can be found in § 9a.
Optionally, party operators can publish Crew Rewards (Crewcards) for guests who bring friends. Publication creates a binding duty to fulfil the promise on the release page; details are in § 9b.
Private parties: Under Visibility in the party form the host can switch on Private Party and select friends. The people who can be selected are the host’s existing chat partners. People the host has blocked, and people in Secret mode, are not offered in that list. PartyUp stores with the party whether it is private, the user IDs of the selected friends (at most 500), and the user IDs of friends who have already received the invitation. The host always sees their own party. A selected friend sees it as well, including on the home list, on the host’s profile, on the map, in Shorts, in comments and on the detail page. For everyone else the party is not shown. Opening a link, a share, a comment thread, a live camera, a ticket page or a crew-reward page does not reveal it: that person is sent to the home page. A guest is also asked to log in. PartyUp then keeps that party ID in the server-side session until the next home page after login, only so the party card can be placed at the top and highlighted in the app colour if that person is then allowed to see the party. If they are still not allowed, the ID is discarded and no card is shown. The highlight is not saved on the account.
The line under the switch says that a party can otherwise be shared by its public link once it has been created, and links to this Privacy Policy. That link does not by itself make a private party public. While Private Party is on, the public link does not open the party for anyone who was not selected.
When the private party is published, each newly selected friend receives one direct message: the host’s username, a sentence in that friend’s language that they were invited to a private party, and the party name as a link to the detail page (§ 11.4). A draft does not send this message; it is sent when the party is published, including after payment. Saving again does not send it again to someone already invited. Switching Private Party off clears the memory of who was invited, so switching it on again can send a new message. Removing a friend and selecting them again does the same. The invitation text is not read in order to personalize recommendations.
Secret mode of the host still hides the party from other people, including selected friends (§ 8). A block still hides it between those two people (§ 11.2). An automatic arrival or leaving notice (§ 11.3) can name a private party in a chat when the person who is there has that notice switched on. Opening that link still does not show the party to a chat partner who was not selected.
Legal basis for the private audience, the invitation and the temporary session entry: Art. 6 Paragraph 1 Letter b GDPR, because the host asked PartyUp to limit who can see the party and to tell the selected friends. The session entry is also technically necessary session data (§ 17.1, § 25 Paragraph 2 No. 2 TDDDG). The two ID lists are kept with the party until the party or the host account is deleted, until the host changes the selection, or, for the list of friends already invited, until Private Party is switched off (§ 21.2). The chat message follows the storage rule for chat messages.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR; for public display within the platform additionally Art. 6 Para. 1 lit. f GDPR; for the publication of Moments about "Share moment” Art. 6 Paragraph 1 Letter a GDPR (consent); for friend stories, following and the moment streak Art. 6 Paragraph 1 Letter b GDPR; for the private one Caching of experience drafts and the watch list of saved Shorts Art. 6 Para. 1 b GDPR; for publication of general shorts Art. 6 Paragraph 1 Letter a GDPR and for storing them Art. 6 Paragraph 1 Letter b GDPR; for the Shorts content mode and its situational notes Art. 6 Paragraph 1 Letter b GDPR, and for aggregated counts without a user ID Art. 6 Paragraph 1 Letter f GDPR (see the paragraphs above); for the machine translation of party descriptions Art. 6 Paragraph 1 Letter b or lit. f GDPR (see § 19.11); for a private party and its invitation Art. 6 Paragraph 1 Letter b GDPR (see above).
The creator of a party ("party operator”) can have up to four live cameras in the party form connect. The connection is made via the connection paths offered in the application (WLAN/LAN, connection or device's own camera / front camera). A mere connection without Activation of the playout options described below does not lead to public play Display of the live stream.
The connection path is selected in the party form via the Connect popup. Only after A conscious action by the party operator causes the browser to access camera or microphone interfaces to (see § 14.3, § 25 TDDDG). In detail:
The device list and preview only run on the party operator's device. The Preview is not transmitted to PartyUp servers and not to viewers. Only with that When you take over a device (double click or confirm the front camera), the stream will be like this signaled and processed as described below - depending on the playout options set. Technical device identifiers and names usually remain locally in the browser (session-related and – for reconnecting after reopening PartyUp – user-related in local storage of the end device) and are not stored as hardware inventory on the PartyUp server saved.
Equal treatment of all connection routes: As far as these Privacy Policy from Live cameras, live streams, setup, operation, sound, playout, analysis or highlight media Speaking of this, this applies equally to the device's own camera without mitigation and without exception / Front camera, for devices connected via a port (especially USB-A, USB-C, HDMI and comparable capture devices) and for IP/network cameras connected via WLAN/LAN. A different legal distancing, responsibility or liability distribution There is no connection.
Each live camera can have the following playout and processing options independently of one another can be set:
Technical transmission: PartyUp provides the signaling for a WebRTC live broadcast ready (including Session Description Protocol Offer/Answer, ICE candidates, viewer identifiers, heartbeats to determine whether a publisher is active). The audiovisual media stream is usually peer-to-peer between the end device Party operator and the viewers' devices and not permanently as a raw stream recorded on the PartyUp server. Third-party STUN servers can be used for NAT traversal (see § 13, § 19.5). TURN relaying is currently not part of the Default configuration. The signaling is kept in the main memory and is no longer necessary End of transmission, timeout or server restart, unless mentioned below Analysis or highlight data is created.
Access to the camera and, if applicable, microphone is only possible after approval the party operator at the browser or operating system level (see § 14.3, § 25 TDDDG).
Operation during registered use of PartyUp: After the party operator If a live camera is connected in the form and not explicitly disconnected, access remains on camera and possibly microphone active as long as it is in PartyUp logged in and uses PartyUp in this browser - even when switching between pages of the application (e.g. Home Page, Shorts, Chats, Party Detail, Form). The live stream will be in this Status continues to be signaled and, as long as playout options are set, continues to be played out. Technically, the browser can interrupt camera access if the tab or window is closed, the browser is closed or the page is completely unloaded; that is one Restriction of browser and operating system, not a shutdown by the party operator. The same logged in user then opens PartyUp again, without the live camera first disconnected or logged out, the application requests the already shared Immediately reconnect the camera and continue the transmission (reconnect).
To maintain the live image, the application can be installed on the party operator's device operate a small preview element that is not visible to viewers, at short intervals check whether an image is still being delivered and - if the browser allows this - one Request screen wake lock so that the device does not stop the stream alone Interrupts inactivity. These processes remain on the end device; an additional one This does not create a raw stream to the PartyUp server. If the device still falls asleep or withdraws The operating system will automatically retry the PartyUp camera after returning to the application as long as the live camera is not disconnected and the user is not logged out.
Automatic shutdown after 30 minutes (optional): In the party form the can Party operators activate the "Switch off after 30 minutes” switch for each camera. Is it active, The live broadcast ends automatically 30 minutes after the time of connection or continued; the server-side connection labeling is terminated and stored locally Reconnection data removed. If the switch is off (standard), the transmission runs - as described under "Operation during registered use” – continue until the party operator the camera disconnects or logs out.
Express separation and deregistration: The party operator ends the live camera in the form (disconnect), the camera access is terminated, the server-side connection identification deleted and locally stored reconnection data removed. An automatic one Reconnection then does not occur until the camera is reconnected in the form. If the party operator logs out, all of their connected live cameras become technical disconnected, the transfer ended and the reconnection data removed. After logging out The camera remains off, even if he logs in again later, until he sees it in the form again activated. An expired login without explicitly logging out terminates local camera access (no more access without a session), but leaves the server-side connection label exist; After logging in again, the camera can be reconnected automatically, unless she has been separated in the meantime.
In connection with live cameras, the following can in particular be processed:
The live image analysis is not used to identify individual people, not to create it biometric templates and not automated decisions with legal effect in the sense of Art. 22 GDPR. It creates relative, comparative key figures (occupancy and mood in the... Relation to previous measurements of the same party, especially the previous peak and the typical workload at comparable times). The one shown on the details page Percentage "utilization” is one such derived key figure.
Purposes: Providing the live functions chosen by the party operator; continuous operation and automatic reconnection during registered use of PartyUp, until express separation or deregistration; Display on the detail page and/or as a live short; optional creation of utilization/mood metrics; optional creation and publication of highlight media; Operation, limitation of abuse and technical stability of the transmission.
Legal basis for platform processing by PartyUp: Art. 6 Paragraph 1 Letter b GDPR (provision of the live function requested by the party operator); Art. 6 Para. 1 lit. f GDPR (operation and display within the platform, insofar as users Call Party or Shorts); for end device access to camera/microphone Art. 6 Para. 1 lit. a GDPR i. V. with § 25 TDDDG, as far as relevant. The legal basis for this The third party has the right to film, transmit and publish images at the event location party operators themselves (sections 9a.4 and 9a.5).
If "Analyze live image” is activated, the application evaluates the live image at short intervals on the client side (in particular motion, edge and image energy features) and transmitted raw numerical values at PartyUp. PartyUp saves time-related samples from this, leads High points and hourly comparison values and calculates the displayed relative utilization. With comparatively high utilization and mood (measured against the previous high point and the typical load of the same party for the respective time) PartyUp Automatically generate a photo and a short video from the live stream and use it as party media save. These media are then ordinary party media: they appear in the Media gallery of the detail page and can be played, liked, commented on in the Shorts be shared.
Highlight media may contain personal data from third parties. Your storage period follows the other party media (§ 21.2). Analysis samples are kept for a specific purpose and removed when the party or operator account is deleted, unless legally required conflict with retention obligations.
PartyUp is a technical platform (digital service / hosting and transmission service). PartyUp provides the infrastructure with which a party operator can connect cameras Can signal the live stream, optionally play it out and optionally have it analyzed. PartyUp does not monitor live images systematically and in real time for legality, and PartyUp does not make the decision as to whether, where, whom and with which camera the party operator films. PartyUp does not supply, assemble, set up or operate the camera hardware; this applies expressly also for devices connected via connection or WLAN/LAN.
The party operator is responsible for the live camera - including the device's own front camera, via connection of connected cameras and IP/network cameras connected via WLAN/LAN – the Live stream, the camera position and orientation, the sound, the playout options, the Highlight media and all people and content depicted or heard thereby alone responsible. This includes in particular the role in data protection law Guests, employees, artists, passers-by and other third parties pictured (usually own responsibility within the meaning of Art. 4 No. 7 GDPR for filming and the Publication at the venue; to the extent that there is shared responsibility in individual cases with the platform operator in accordance with Art. 26 GDPR, the party operator remains nevertheless for the legality of the recording and publication in relation to the persons pictured).
The party operator bears full responsibility for all disputes, claims, official procedures, warnings, cease and desist, information, deletion and Claims for damages as well as for all material and immaterial damages resulting from the Installation, connection, network connection, operation, alignment, the Transmission, storage or other use of the live cameras arise – including but not limited to violations of the right to one's own image, the GDPR, Domestic law, personal rights, copyright and ancillary copyright law Criminal law, youth protection and neighboring law positions. This applies without distinction for front camera, connection cameras and WLAN/LAN cameras. PartyUp is just that technical service providers for signaling, optional playout, optional analysis and Storage of the content triggered by the party operator and assumes no responsibility for this Responsibility, liability or guarantee towards the party operator, persons depicted or other third parties. PartyUp expressly distances itself from the choice, installation, The orientation and content of every live stream conducted via PartyUp, regardless of the connection path. Mandatory legal liability conditions remain unaffected to the extent that they are not effective can be waived (in particular liability for intent and - if unavoidable - gross negligence Negligence as well as for damages resulting from injury to life, body or the health). PartyUp is not obliged to check each live image in advance; If there are specific indications of illegal content, it may be checked, blocked or deleted (see § 29).
By publishing a party with live cameras, the party operator confirms in the form that to have taken note of and agree to the information in this § 9a, including the installation and responsibility instructions for the front camera, connection and WLAN/LAN.
The party operator has every live camera before commissioning and throughout operation responsible for ensuring that recording, transmission and publication are lawful are. These installation, alignment and operating specifications apply expressly and Completely also for cameras that have a connection (USB-A, USB-C, HDMI or comparable local connections) or via WLAN/LAN (IP/network cameras), not only for the device's own front camera. A network or wired camera is not allowed be set up, hidden or aligned in the same way as the device's own camera would be inadmissible. To this end, he has in particular - without any claim to completeness - in each case Subject to the regulations applicable in each individual case – the following must be observed:
The above list does not replace legal advice in individual cases. The party operator has the regulations applicable to its venue, its guests and its camera work check yourself and, if necessary, seek expert legal advice. PartyUp owes no check as to whether the party operator fulfills these obligations and no check of the Installation or image field of the front camera, connection camera or WLAN/LAN camera.
Legal basis for platform processing: see section 9a.2.
The creator of a party ("party operator”, "host”, "organizer”) can publish one or more Crew Rewards (in the application also called Crewcards). A Crew Reward is a perk promised to a guest if that guest brings a stated number of friends (for example a free drink or snack). PartyUp stores in particular: the published description of the perk, the required number of friends, assignment to the party and to the operator account, time-limited invitation or QR tokens, status of the crew (invited / present / unlocked) and whether the release page has already been used.
If the conditions shown in the application are met, the guest receives a time-limited QR code on PartyUp. This code must be scanned when presented. A successful scan opens the release page (Freigabeseite). That page states the published promise and that the organizer is now obliged to fulfil it.
Binding obligation of the organizer: As soon as a Crew Reward has been published, the organizer must under all circumstances honour the published Crew Reward and provide / pay it out on the release page (Freigabeseite). Publication is a binding commitment toward the guest. Later deletion of the card, a change of mind, absence of the organizer, a dispute with the guest or any other reason does not release the organizer from this duty for a Crew Reward that was already published and successfully unlocked. PartyUp does not physically hand over drinks, food or other perks; the organizer alone must fulfil the promise at the event when the release page is shown.
PartyUp is only the technical service for publishing the card, checking the crew and showing the QR code and the release page. PartyUp does not become a party to the organizer’s promise and does not guarantee that the organizer will in fact hand over the perk. The legal relationship for fulfilment is between organizer and guest. PartyUp distances itself from disputes about whether a perk was handed over (see § 29).
Purpose: Technical organisation of guest rewards for bringing friends,
verification of the crew and presentation of a scannable proof and a release page.
Legal basis: Art. 6 Para. 1 lit. b GDPR (performance of the platform
functions and of the organizer’s published promise toward the guest); additionally
Art. 6 Para. 1 lit. f GDPR (documentation of the published commitment and of redemption
as evidence).
Users can rate parties with a star rating (1-5). For logged in users the Rating assigned to the account (internal identifier). For users who are not logged in, a Anonymous reviewer identification can be set and stored via a cookie (see § 17). To technically limit or assign multiple evaluations.
Average values can be formed from ratings and displayed in the application. In addition, ratings (also in aggregated form) flow into the server-side Popularity and sorting logic of the party list (see § 18.4). The one on the party menu The rating displayed remains the actual average rating; for the internal Visibility weighting of parties with increased visibility (Pro) can be algorithmically adjusted limited valuation markup can only be used for sorting, excluding the displayed to change assessment.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR (registered use) or Art. 6 Para. 1 lit. f GDPR and – if necessary – Art. 6 Para. 1 lit. a GDPR / § 25 TDDDG for the reviewer cookie for guests.
PartyUp enables direct messages between users as well as comment-like posts to parties. In particular, the following can be processed: participant IDs and user names, message content (text), message type, attachments/URLs, reply references, flags, reading status as well user-related chat settings (for example pinned, archived, blocked, marked as unread, and whether auto party notices are on for that chat). Location and live-location messages can also be stored (coordinates, map link, and, for a live location, when it expires). Automatic party notices in chats and on the profile are described in § 11.3. The same presence can be shown, without reading private messages, in a list of which chat partners are at a party and how long they are expected to stay (see § 18.6).
Registered users can create an evening plan together in private chats. Add to this them one Location (with address suggestions) and one Length of time (1-24 hours) on. PartyUp creates a suggestion on the server side from real PartyUp events nearby, under Taking into account the preferences of both chat partners (including distance, time, behavior, friendships). Among other things, the following are processed: the location entered, the duration, the chat ID, internal user IDs of both partners, selected party IDs, coordinates of the stops and the generated plan text. After sending, the plan text and stoplist are saved as a chat message; the stop list enables the evening route map. PartyUp can be used to vary repeated plans Maintain a limited server-side history (chat, location, duration, party IDs used) – without external AI services. Private chat content outside of this plan feature will be used for the Plan creation not evaluated for content.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR.
The contents of private chats are generally only intended and intended for the chat partners involved for personalization not evaluated for content. From private chats Only metadata from the participant graph is used for recommendations (e.g. direct Chat partners / "friends” as well as mutual acquaintances / mutuals) as well as the fact that a Party link was shared, opened or subsequently used (see § 18.4). If the user has allowed contact access, matches with device contacts are used in addition, so that mutual friends can be recognized more reliably and further friend suggestions can be made (see § 14.4).
Comments on parties may be visible to authorized users of the respective comment function. Text from party comment threads can be used to improve popularity and recommendations are evaluated (including rough mood indicators and topic terms); private direct messages are excluded from this.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR; in abuse prevention, Maintaining functionality and personalization/findability Art. 6 Para. 1 lit. f GDPR.
A notice: Users are responsible for ensuring that there is no illegal content and not to provide personal data to third parties without a suitable legal basis transmit.
Processing function: Registered users can view other users block chat-related or completely. The blocker ID, blocked ID, Username of the blocked person and timestamp. The technical effect is bidirectional for the Visibility: When completely blocked, parties and chats of the other party are hidden; If a chat is blocked, the conversation in question is suppressed. There is no automatic one expiration time; Entries are no longer valid if the account is deleted (§ 23) or manually unlocked.
Purpose / legal basis: Protection against unwanted communication and Content contact (Art. 6 Para. 1 lit. b and lit. f GDPR).
What this does: When a signed-in person has GPS switched on in PartyUp and the device shares a location, PartyUp checks whether they are physically at a published party. “At the party” uses the enter and leave radii in § 14.1 (currently about 0.25 km to count as arrived, and about 0.55 km before a leave is noticed, so small GPS jumps do not send a new notice every few metres). From that presence PartyUp can do two separate things: a short automatic line in a chat, and an ON FIRE badge on the profile. The chat line works the same in a private chat, a group, and a party comment thread. Secret mode stops chat notices and hides the badge from everyone else. A block between two people stops both for those two. Chat texts are not read in order to write these notices.
In a chat. Private chats, groups and party comments each have a switch labelled Partys in the location menu. It stays off until that person opens the chat. Opening it turns the switch on for that chat. They can turn it off again for that chat alone. Creating a chat, or being added to one, does not turn it on. While it is on, PartyUp can place an automatic message in that chat when they arrive at a party, and another when they leave or move on to a different party.
An arrival message is sent only if someone else in that chat has a location of their own on
the server and the party is no more than 10 km from that location. In a private chat
that person is the chat partner. In a group or a comment thread it is the nearest other
person in that chat. People in Secret mode, and people who are blocked, are left out of that
check. The distance in the message is the distance between the party and that person. It is
not a live trail of the person who arrived. The message uses the arrival line saved on the
account. The placeholders
{name} and {distance} are filled with the party name and that
distance in kilometres. The message links to the party and can store the coordinates of the
person at the moment they arrived. One arrival notice is sent per party and chat until they
leave. The leaving line saved on the account is used when they leave the venue or change party.
If nobody else in that chat is within 10 km, no arrival message is sent. Turning the switch
off stops further notices in that chat.
On the profile. Under Settings → Auto-Partymitteilung there is a separate switch labelled Öffentlich. It stays on until the person turns it off. While it is on, and they are at a party that is currently live, their profile can show ON FIRE. The badge links to that party. It does not repeat the arrival or leaving text. They see it on their own profile. Other signed-in people who can open the profile see it too, including people they do not chat with. If the two of them do have a private chat and the person at the party has turned Partys off in that chat, or that chat is blocked, the other person does not see the badge. The badge goes away when they leave, when the presence has not been updated for a while (currently about 20 minutes), when the party is no longer live, when Öffentlich is off, or, for everyone else, while Secret mode is on.
The arrival and leaving lines are written by the person (up to 280 characters) and stored on the account until they change them or delete the account. An empty line falls back to a short default: “Bin auf der Party „{name}“ ({distance} km)” on arrival, and “Hab die Veranstaltung wieder verlassen” on leaving.
The friends list on a party card (who is there, and the estimated time left) is a separate view of the same presence. It is described in § 18.6. That list follows the per-chat Partys switch. It does not follow the profile switch Öffentlich.
Purpose: so chat partners can see, in the person’s own words, that they have
arrived at or left a party within 10 km, and so the profile can show which live party they
are at when they have left Öffentlich on.
Legal basis: Art. 6 (1) (b) GDPR for these chat and profile functions;
Art. 6 (1) (a) GDPR and § 25 TDDDG for the device location that GPS sharing requires
(see § 14.1). GPS off, Secret mode, the Öffentlich switch, the per-chat Partys switch, a block,
and account deletion are the practical ways to stop it.
When a host publishes a party with Private Party switched on, PartyUp places one message in the existing direct chat with each newly selected friend (§ 9). The message contains the host’s current username, the sentence that the friend was invited to a private party (in that friend’s language setting), the party name, the party ID and a link to that party’s detail page. It is an ordinary chat message: the same storage, deletion and block rules apply as to other direct messages. It is not sent while the party is still a draft, and it is not sent again to a friend who is still on the list of people already invited. The text is not evaluated for recommendations. For a recipient who was not selected, the link opens the home page and does not show the party.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR.
In connection with parties, chats, moments (experiences) and advertising, images, videos and Audio files (including voice messages) can be uploaded. These files are stored on the Stored on servers and made available via protected or application-specific URLs. To the Metadata can include: File name, MIME type, size, storage path, source (e.g. party media or moment/experience), uploader identifier and timestamp.
Moment camera ("Share moment”) and burned-in filters: When recording one Moments the user can choose a visual filter in the preview or an automatic one Trigger image enhancement (magic wand). Processing takes place in the end device; the result will be burned into the original file before uploading. The medium created in this way is the stored one Original and appears in this form for other users (party gallery, Shorts) as soon as the User the button "Share moment” operated. He thereby gives consent for publication (Art. 6 Para. 1 lit. a GDPR). A later account-related one Further processing in Shorts does not take place. Registered parties can visit the party details page Users for the own view additionally save CSS display filters; the The original file remains unchanged, other users continue to see the saved original (see also § 21.2). Moments that you posted at a strange party remain usually exist there until this party is deleted; an account deletion removes everything own parties and their media (§ 23).
Private Experience Drafts and Saved Shorts: Experience designs become like Other uploads are stored on the server as media files, but not account-related published until the user uses "Share moment”. Saved Shorts are account-related references to existing party/experience media (identification, party reference, storage time); They do not create additional public exposure, but rather enable it the user a private folder or feed. Other users will not receive a new one Visibility.
In addition, share kit graphics can be automatically generated from party content and as image files stored on the server side (see § 9). In terms of content, they correspond to those anyway published party information and, if applicable, the cover image; there will be no additional ones personal data of third parties is collected for this purpose.
If live image analysis is activated, highlight photos and Short videos are generated and saved as normal party media (source: live analysis; see § 9a.3). The same principles apply to these files as to other party media.
Media may contain personal data (e.g. people depicted, voices, Location information in pictures). The uploader is obliged to provide the necessary rights and Obtain the consent of third parties yourself, if necessary. Technical features and Names of uploaded media as well as party descriptions can – in derived, tokenized form – are included in the personalization of the party list (see § 18.4).
Legal basis: Art. 6 Paragraph 1 Letter b GDPR; for published moments additionally Art. 6 Para. 1 lit. a GDPR (consent by "Share moment”); for private Experience drafts and saved Shorts Art. 6 Para. 1 lit. b GDPR.
Processing function: If the call function is in a private chat is used, PartyUp only provides the Signaling ready so that two End devices can establish a WebRTC connection. The following are temporarily processed, among other things: Setup, acceptance and termination processes as well as technical connection parameters (SDP offer/answer, ICE candidates, call status: e.g. E.g. ringing → connecting → active → ended). The signaling is maintained in the server's memory (no permanent call database). Terminated calls are removed from storage after a short retention period (currently around 30 minutes). removed; a server restart also deletes them. Party comment threads do not provide calls.
The actual audio/video transmission (media stream) usually takes place peer-to-peer the participants' end devices and does not run permanently via the PartyUp server. To Third-party STUN servers can be used to establish the connection (NAT traversal). (see § 19.5). Technical connection data (particularly IP addresses) can be sent to the STUN provider. TURN relaying is currently not part of the standard configuration; If a TURN service is added later, this declaration must be updated accordingly. The same signaling and STUN infrastructure can be used for live cameras (see § 9a).
For calls, the end device accesses the microphone and – for video – the camera. The release takes place via the permissions of the browser or operating system. The call is without release technically not possible; remaining chat functions remain usable.
Purpose: Establishing and terminating a real-time audio/video connection between chat partners; no evaluation of conversation content by PartyUp.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR; for device access consent / Authorization at the end device level (Art. 6 Para. 1 lit. a GDPR, § 25 TDDDG where relevant).
Optionally, the application can query the device position to sort parties by distance or display distance information. The position query only takes place if the user does so in the Application activated and the device/browser grants location approval. The Nearby list can provide personalization and rating in addition to distance and rating Consider visibility signals (see § 18.4), including increased visibility from Partys Pro subscribers, as long as the distances are comparable.
With shared GPS, users can also show their current location or a location in private chats Send live location (limited time, up to 2 hours by default) to chat partner. Coordinates are transmitted to the PartyUp server and sent as a chat message the chat partner involved is saved. The same positions are checked on the server so PartyUp can send the automatic party notices in chats the user has opened and show the profile badge described in § 11.3. For that check the current position can be stored for a limited time as GPS presence (coordinates, party reference, timestamp). Whether someone is “at the party” is detected using a GPS buffer (currently typically entry radius approx. 0.25 km, exit radius approx. 0.55 km, to account for GPS inaccuracy). For statistical/engagement purposes, a visit can only be made counted after a minimum stay at the location (currently approx. 10 minutes for "visited” metrics; shorter thresholds may apply for internal job/activity counters). Stale presence data will no longer be available after a limited period of time (currently up to 24 hours). used or cleaned for the function. When leaving a party location (or changing to another party) can be the actual length of stay - provided it has a minimum threshold reached and does not exceed an upper limit – are included in the length of stay model, so that later estimates become more accurate (see § 18.6).
The current device position is usually used locally in the browser for distance calculations used. In addition, the last known user location (coordinates and timestamp) are stored on the server side of the account, among other things. for card alignment in the party form if GPS is not currently active, as well as for the GPS presence functions. Become independent of it Event locations (coordinates of parties) are stored and displayed on the server side (§ 9). Shared location/live location messages and party proximity notifications are considered chat content saved. For routing, the user location is transiently sent to the server and from there Routing services are transmitted without creating a permanent location chronicle.
The "GPS on/off” preference can be saved locally in the device (localStorage); the last one
The known location is managed on the server side and also briefly locally
partyup-last-geo (coordinates and timestamps) are cached, among other things. with that
Distance information and optional location signals to activity or promo requests
(see § 16.2, § 18.1) can be used without having to query the position again.
Users can choose a user interface language from a list of European languages in the Settings
or leave it in "Automatic (Location)” mode. The last selection (language and mode
manual/automatic) is saved in the session and - when you log in - in the user account
led; In addition, it can be stored locally in the end device (localStorage), so that the choice
can be reliably restored after session changes. A manually selected language
takes precedence over automatic derivation and is not overwritten by GPS.
The user interface texts are included in the HTML of each page as a language catalog.
If that catalog is missing, the client may request it from an application-specific
interface (/api/i18n). These catalogs do not contain any
personal content of other users. The machine translation of other party texts
(particularly descriptions) is separate and described in § 19.11.
Guest mode and login: In guest mode, language may follow a local preference or automatic location mapping (see below). After a successful login, the language stored on the user account (manual Settings choice) applies immediately, including the welcome message on the home page. A language chosen only as a guest is not written over an existing account language. Guest localStorage language preference is not applied to a logged-in account. New registrations may take over the language used during sign-up if the account does not yet have a stored language.
Under Settings → Design Users can choose one of several colored
Choose surface appearances (e.g. neon purple, dark blue, neon red, neon green).
The selection only controls display elements (colors, glows, background coloring)
and is stored locally on the device (partyup theme). There won't be any
server-side personal profile data derived from the design choice.
In automatic mode, PartyUp can - if GPS is enabled - via reverse geocoding (see § 19) derive and set appropriate language from the approximate location, also in the Guest mode. If GPS is switched off in the app, English is the default language Automatic mode. Without appropriate mapping and without GPS, a standard language (currently English) can grab.
Camera and/or microphone can - only after approval by the user - for the following purposes Functions can be used: recording chat media, voice messages, video recordings, QR code scan, audio/video calls, the experience camera at a party location (photo/video, optional filter/image enhancement before upload, see § 12) as well as live cameras Party operator (live stream, optional live shorts and live image analysis, see § 9a).
For live cameras, the browser can be activated after a corresponding click in the connect popup (camera, Connection or WLAN/LAN) determine a list of the video devices known to him and a local one Show preview. Only devices that already have an operating system or browser are identified provide camera; PartyUp does not scan the local network independently. The device query for Connection or WLAN/LAN only takes place after the respective button is clicked, not in the background just by opening the form. Sound is only included if the selected device is on A microphone or an audio channel is provided and the party operator takes over the stream. Once connected, camera access for live cameras remains active as long as the party operator is registered in PartyUp and does not separate the camera in the form (see § 9a.1). A closed tab or browser technically terminates access; when reopening PartyUp When logged in without prior disconnection or logout, access becomes automatic requested again. Signing out will disconnect all live cameras on the account. As far as the browser is concerned allows, a screen wake lock can be requested during live operation exclusively for the ongoing stream on the party operator's device to maintain.
Legal basis: Art. 6 Para. 1 lit. a GDPR and/or Art. 6 Para. 1 lit. b GDPR; Device access according to § 25 TDDDG (consent), unless there is an exception for technical reasons necessary storage/accesses intervene.
If the user allows cookies, PartyUp asks the browser for the contacts stored on the device. The operating system or browser then lets the user choose which entries are shared. Depending on what the contact book provides, this can include a contact's name and identifiers such as a telephone number or an email address. While cookie consent remains in place, PartyUp asks again about once a day, because the contact book can change. Switching cookies off in this Privacy Policy removes the stored matches.
Purpose: PartyUp uses these contacts to find people who already use PartyUp, to suggest friends more accurately, to recognize mutual friends more reliably, and to make further suggestions. A contact is compared with PartyUp accounts. Where there is a match, that person can be shown as a possible friend, and shared contacts can show that two users have friends in common. Current matches are stored in the personal taste profile as a higher creator rank, so Shorts, party moments and party cards from those people are ranked higher. People who are no longer among the shared contacts lose that rank on the next check. Suggestions that already come from chats, taste and behaviour (§ 11, § 18.4) can therefore include more people and rank mutual friends more clearly. PartyUp does not use the contact book to send messages to people outside PartyUp, and it does not use it for advertising.
Contacts of people who do not have a PartyUp account are not kept as a separate address book and are not used to contact those people. Matches and the suggestions derived from them are stored with the account only for as long as contact access remains allowed. They are removed when the user withdraws that access or when the account is deleted (§ 21.2, § 23). Without this permission, finding friends by username or QR code, and the suggestions already described in § 18.4, remain available.
Legal basis: Art. 6 (1) (a) GDPR for the permission to access contacts on the device, and Art. 6 (1) (b) GDPR for using the matches to provide friend finding and friend suggestions. Device access also follows § 25 TDDDG (consent). The permission can be withdrawn in the operating system or browser; withdrawal stops further access.
PartyUp uses the payment service provider for paid services Rapyd (Rapyd Europe UAB or affiliated companies). The Payment form appears embedded in PartyUp (embedded Rapyd checkout); the actual payment processing – including card, wallet and Installment services – via Rapyd. These include in particular:
Depending on availability and your device settings, Rapyd may include, among others, the following Payment methods offered: payment by card, Apple Pay, Google Pay, Amazon Pay, Klarna, Link, PayPal or SEPA direct debit. Rapyd controls which options are displayed based on your region, the order context and the procedures activated in your Rapyd account. When selected One of these methods may direct you to Rapyd or the respective payment provider forwarded or use a wallet on your device; PartyUp does not receive a complete one Map data.
In particular, the following can be transmitted to Rapyd: technical payment information, amount, Currency, product/meta data (e.g. user ID, party or advertising ID, purpose identifier such as Pro, Ad-free, party publication, ticket purchase, PartyCash top-up or ad setup) as well as - as far as in the checkout or at the Payment facility collected - contact details such as an email address and required Billing/address information. Sensitive payment data (e.g. full card number, CVC) are usually entered directly into Rapyd components (iframe) and not permanently stored on the PartyUp server. PartyUp saves to account typically Rapyd customer and subscription identifiers, plan status (Pro/Ad-free) as well Payment status information. Status changes (checkout completed, subscription updated/deleted) are reported to PartyUp via Rapyd webhooks and result in the Activation or deactivation of the corresponding features on the account; can at the same time Evidence of payment/contract that must be retained in the statutory retention store (§ 21.1) be updated in encrypted form.
Rapyd and the payment method partners offered may process data in third countries (see § 20). The data protection information of Rapyd also applies as well as - if you Select Klarna, Apple Pay, Amazon Pay or other methods - see the instructions for each one Provider. Rapyd: www.rapyd.net/privacy-policy.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR; Art. 6 Paragraph 1 Letter c GDPR for tax and accounting-relevant storage in accordance with § 21.1.
A host can offer online tickets for one specific party. The offer appears only when that party has an entrance price and an uploaded ticket file. Guests then see the option to buy one or more tickets for that party (a quantity from 1 to 99). The amount charged per ticket is the entrance price plus €0.25, multiplied by the quantity. Buying requires an account. It does not require an email address, and PartyUp does not ask for one before payment.
The host’s uploaded file is stored with the party. It can be shown on the party page and as a preview in the purchase window. It does not yet contain the buyer’s ticket code. The buyer can pay with the Rapyd checkout described above or, if the PartyCash balance covers the charge, from that balance (§ 15.2). After a successful Rapyd payment, the charged amount is paid out to the payout account the host stored for that party. A PartyCash payment debits the full charge from the buyer, credits the host’s PartyCash with the entrance price times the quantity, and leaves the €0.25 per ticket with PartyUp. PartyUp does not keep full card data.
Only after successful payment does PartyUp create a random 25-digit code for each ticket. The code is stored privately with that ticket, is not shown as text in the app or on public pages, and is not issued again for another sale. The same ticket keeps the same code, including if the email is sent again. PartyUp keeps a copy of the host’s file with the sale and can rebuild the ticket file from it: the first page is that file, and the second page is added by PartyUp with the party background, a QR code and the party name under the QR code. The QR code contains the unique code for that ticket, a second code so PartyUp can recognize its own tickets, and the identifier of that party.
If the account has an email address, PartyUp sends one email to that address with one attached ticket file per ticket. The email names the party; the codes are only in the attached files. If the account has no email address, no email is sent and no address is collected for the purchase. In either case the buyer can open each ticket that has not yet been redeemed from the party page. The list shows “Ticket 1”, “Ticket 2” and so on, in purchase order. A ticket that has been redeemed is left out of that list.
A successful purchase stores the party on the buyer’s saved-parties list (§ 9). The Tickets control on that party stays available while the buyer still has a ticket that has not been redeemed, even if the host later removes the entrance price or the ticket file. New tickets can then no longer be bought. The stored copy is what the buyer opens.
When the ticket is shown, the host can scan the QR code for that party. PartyUp compares the unique code with the private sale record and can mark that ticket as already used. The check returns only whether the ticket is valid, already used or unknown. It does not publish the code.
Purpose: offering, paying for, delivering and checking a ticket
for one specific party, paying the host, letting the buyer open a ticket that
has not been redeemed, and preventing the same ticket code from being used
twice.
Legal basis: Art. 6 (1) (b) GDPR for the purchase, delivery
and in-app access to the ticket and for saving the party; Art. 6 (1) (c) GDPR
for payment records that must be kept (§ 21.1); Art. 6 (1) (f) GDPR for
storing the unique code and the ticket-file copy so a sold ticket can be
recognized once, opened by the buyer, and is not issued again.
Recipients: Rapyd for a card checkout and for the payout to
the host’s account (§ 19.1). Brevo only if a ticket email is sent (§ 16.4,
§ 19.2). A PartyCash payment stays inside PartyUp (§ 15.2).
A registered user has a PartyCash balance, shown on the parties page. The user can load an amount through the Rapyd checkout in § 15. The credited amount is the amount paid. The user can send an amount to someone they already have a direct chat with. PartyUp then reduces the sender’s balance, increases the recipient’s balance by the same amount, and places a message in that chat stating the amount sent. The movement list in the app shows top-ups, amounts sent and received, ticket payments and ticket-sale credits, each with the amount, the time and, where relevant, the other person’s username or the party name.
A ticket can be paid from this balance when it covers the charge (§ 15.1). The buyer is debited the full charge. The host is credited the entrance price times the quantity. The €0.25 fee per ticket is not credited to the host. If the balance is too low, nothing is transferred and no ticket is created.
Purpose: keeping an account balance, loading it, sending it
to a chat partner, and paying for a ticket.
Legal basis: Art. 6 (1) (b) GDPR. A top-up paid through Rapyd
is also a payment under § 15; Art. 6 (1) (c) GDPR applies to any payment
record that must be kept (§ 21.1).
Recipients: Rapyd for a top-up (§ 19.1). A transfer or a
ticket payment from the balance is processed by PartyUp. The chat message is
visible to the participants of that chat.
Registered users can upload their own advertising content (image or video) under "Advertising”. switch. In particular, the following are processed: medium, selected advertising duration (display duration), associated CPM pricing model (cost per 1,000 impressions; starting price currently Uniform €7 CPM, prices may vary based on offer and actual effect develop further), monthly budget, fixed monthly billing period as well Rapyd payment details (customer/payment method identifier). A separate email address for There is no charge for advertising placements. The display can generate impressions/clicks and thus Record associated costs (billed typically at CPM/1,000 plus VAT; this amount is the advertising value). Periodically (monthly) amounts can be debited via Rapyd become. Stream and billing details can be viewed in the app under "My Ads”; it No advertising billing emails will be sent. The applicable charges will be applied to each debit Payment service provider fees Rapyd added (currently 3% of the withdrawal amount plus €0.25 per transfer) so that the advertising value and fees are debited together.
Processing function: PartyUp treats advertising spaces as optional Slots / Opportunities with named contexts (e.g. opening a party card, Entering the party details page). The technical function is for each slot to decide algorithmically (1) whether advertising is shown at all (often: no / emptier slot), (2) which creative is chosen from the active pool and (3) which Performance/Skip/Accept signals flow back in order to update the playout and pricing model. The aim is not to maximize advertising frequency, but rather to display it as appropriate to the situation as possible little disturbance.
Whether and which advertising is played can depend on the current situation and - if activated Personalization – depends on previous behavior, especially:
Personalized vs. contextual display: Under Settings → Advertising Users can use the option "Personalized advertising” switch on or off (default: active). Additionally The advertiser can determine for each campaign whether it should be displayed in a personalized/context-related manner should be. If the viewer option is active and the campaign is personalized, slots and Creatives selected taking into account personal behavioral/situational signals (see List above). If the viewer option is deactivated, the playout continues contextual (e.g. based on slot prior and aggregated creative/performance metrics), but without adaptation to the individual usage behavior of the viewer; the probability a playout is then typically significantly lower. Personalizing party lists (§ 18.4) and the anonymized preference profiles (§ 18.5) remain from this switch untouched. The setting is saved in the session and – if logged in – in the user account.
Ad-free sign-in and registration: The login and registration screens (including the confirmation step to create an account) are an advertising-free zone. PartyUp does not offer promo/advertising slots there and does not retrieve a promotional medium for those screens. Navigation that only leads to sign-in (for example a guest tap on "Friends”) likewise does not play an interstitial advertisement before the form. After a successful login, advertising may appear again on other screens according to the rules in this § 16, unless Ad-free or Pro status applies. Settings, the ads manager, Pro, checkout and similar account/billing screens stay advertising-free.
For unknown users, the advertising is deliberately kept low and only gradually expanded ("cold start” / slow ramp). Users with active Ad-free or Pro status can be excluded from advertising. Advertising content from users in Secret mode is for other users are not shown (filter via the advertiser user ID).
When retrieving the next promo/advertising medium and reporting the viewing time,
PartyUp can be skipped or viewed completely - provided a current or local one
cached location exists - the approximate coordinates (lat/lon)
together with slot identifier and signal data to the server. The purpose is that
Situation-related selection and evaluation of the play (e.g. proximity), not the structure
a permanent location chronicle from these inquiries.
Billing and CPM learning logic: Billing is based on played games Impressions (also recorded internally in the system as "clicks”/periodic counters; relevant The basis for assessment is the recorded playout/impression, not the mere watch time). Costs per period are Impressions × (CPM/1,000), plus sales tax. Watch time, skip and completion are used for statistics and learning logic, not for direct purposes Individual pricing per second. The CPM applicable at the time of booking will be determined at the respective Campaign held ("Price Lock”); the prices shown in the duration dropdown reflect that reflect the current status. The starting CPM is currently a uniform €7; for Personalized campaigns may have a surcharge (currently +€5 compared to Base CPM of the sustained level). Aggregated information about which duration/pricing models Advertisers choose and how advertisements work (full view vs. early Skip), flow into a server-side adaptation logic (adaptation steps limited, currently typically in the cent range, with cooling time and minimum sample) in order to achieve continuous level and updating matching prices. When the optional budget is reached, the campaign marked as exhausted and no longer played.
Advertising/information media (videos or images) can optionally be sent via the protected interface (/api1). be transmitted. These are stored on the server and can be accessed by users in the following § 16.2 can be displayed in the advertising spaces described. Viewing times and skip/accept signals can be captured for aggregated metrics and learning logic.
Transactional emails from PartyUp are sent via Brevo (Sendinblue), a third-party mail delivery service, over TLS. The sender is noreply@partyup.pro. Password recovery emails (confirmation code) are sent if an email address is stored on the account. After a successful ticket purchase (§ 15.1), PartyUp sends the ticket files to that same account email only when an address is stored. One email can attach one file per ticket. If no address is stored, no ticket email is sent and PartyUp does not ask for an address. Processed, when a mail is sent, are recipient address, subject, email content and, for a ticket, the attached files; the texts follow the user’s language setting. Promotional billing or stream detail emails will not be shipped.
Legal basis: Art. 6 para. 1 lit. b GDPR (account/authentication functions, password recovery, and delivery of a purchased ticket); for the playout and optimization of information media as well as the Advertising billing via Rapyd in addition to Art. 6 Para. 1 lit. b GDPR or Art. 6 Para. 1 lit. f GDPR (legitimate interest in the most appropriate and least disruptive advertising display possible and in the further development of the price/matching logic).
PartyUp uses cookies and similar storage technologies. As far as cookies are not technical are required, the use is based on consent (§ 25 Para. 1 TDDDG, Art. 6 Paragraph 1 Letter a GDPR). Consent to cookies is also the permission to read device contacts for finding and suggesting friends (§ 14.4). Switching that consent off deletes the stored contact matches. We base technically necessary cookies on Section 25 Paragraph 2 No. 2 TDDDG i. V. with Article 6 Paragraph 1 Letter b and Letter f GDPR.
authenticatedAt);
you will then need to register again. The session also ends when you log out
Account deletion or when the server no longer holds the session. Expired store listings
are periodically cleaned up.
partyup-language-pref; used in guest mode; after login the account language
takes precedence, see § 14.2), interface design/color theme (partyup theme),
last known location (partyup-last-geo: coordinates and timestamp),
pseudonymous activity identifier (partyup activity id) to assign
Activity reports and interaction reports (see § 18),
page paths prepared for background loading (partyup-prefetch-plan-v1;
typically discarded after a few hours),
User-related identifiers for reconnecting a live camera
(partyup-front-camera-armed, partyup live camera source,
partyup live camera device, each supplemented by the user ID; see § 9a.1)
When installed or used as a progressive web app, a service worker can store static assets in the browser (style sheets, scripts, self-hosted fonts, icons, and the decorative backdrop photos of the screens). The purpose is performance and offline or installation capability. Content data from chats and parties is not kept in this cache as a substitute for the server database. HTML of frequently used screens is prefetched in the background together with the backdrop photos that belong to those screens, and both are stored in the browser Cache API. On a first visit, before personal habits are known, PartyUp fills that cache continuously in the background with the common screens and with pages that friends and users with similar interests open. After about five visits the cached set follows the user's own recent preferences. The photos are the same decorative images for every user and do not contain personal data. After login or logout, the home page and Settings are loaded from the network so that a previously cached guest view is not shown as if the user were already signed in (or the reverse). The Guide "To the home screen” uses the information provided by the browser or Installation function provided by operating system; PartyUp does not save anything beyond that own installation telemetry data. After you grant notification permission, PartyUp sends Web Push messages for new chats, incoming calls and new friend stories via the browser push service (Apple, Google or Mozilla). The push subscription endpoint is stored with your account until it expires or you remove it.
You can delete cookies and local storage content via the Settings of your browser or restrict. Blocking technically necessary cookies can affect the registration function affect.
When a signed-in user chooses a Shorts feed (party moments only, all shorts, or Auto),
PartyUp stores that choice in the cookie partyup_partys_content_mode
(duration one year, SameSite=Lax, path /) and on the account. The purpose is
to keep the chosen feed across visits. The cookie contains only the mode name. It does not
contain the situational notes; those stay on the server (see § 9). Legal basis: Art. 6 (1)
(b) GDPR and § 25 (2) No. 2 TDDDG, because the cookie stores a setting the user has chosen.
Processing function: While the web interface is visible, the Client an activity alert at regular intervals (currently approximately every 30 seconds). ("Heartbeat”) to the server. The technical function is (a) active usage time to accumulate per day and identifier, (b) hourly activity markers for peak analysis to set and (c) optional situation signals (approximate coordinates, date filter of the Party list) to personalization (§ 18.4) and advertising decision (§ 16.2). Between two heartbeats, the active time is updated on a delta basis (top cover currently approx. 90 seconds per message) to avoid unrealistic delays with delayed clients to create jumps.
The following can be processed:
lat/lon), provided GPS is enabled
or a last known location is available locally (partyup-last-geo);
Location and date filter information on the heartbeat is used for situation-related personalization and behavioral observation (see § 18.4) as well as context-related advertising decisions (see § 16.2); they do not replace a permanent location chronicle. Global ones are separated from this Usage counters (e.g. party visits, route retrievals, navigation starts, promo watch times) updated in an aggregated and non-personally keyed manner.
Purpose: Determination of aggregated usage metrics (particularly active time overall and per user/identification, times with a particularly large number of active users), operation and Further development of the platform, traceable utilization and – as far as location/filter signals be sent along – situation-related sorting and playout.
Legal basis: Art. 6 Para. 1 lit. f GDPR (legitimate interest in functional operation, statistical evaluation of platform usage and abuse/ capacity observation) as well as – as far as the local storage of the activity identifier is concerned is – Section 25 Paragraph 2 No. 2 TDDDG i. V. with Art. 6 Para. 1 lit. f GDPR (technical required storage for the assignment of activity messages).
PartyUp provides a secure interface for querying aggregated operational statistics (including number of registered users, new registrations on the respective day, number advertised parties, comments and chat messages, active usage times, times with Most active users or registrations, party visits determined via GPS (Arrival only after staying at the venue for at least 10 minutes), number calculated routes, navigations started in the map area, viewing time of over Advertising videos and images provided via the interface in MM:SS format, usage frequencies individual interface functions, typical usage processes, dependency quota consumption as well as calculated final income). Access requires a day-dependent API key and is not intended for the general public.
The answer is structured as numbered plain text: Every key figure, every reported one Surface function, every typical usage process, every dependency with consumption and Remaining quota in percent, every documented income and the labels "Data required to be retained by law”, "User feedback:” and "Current final revenue” appear in each with its own numbered lines; below, a compact ASCII coordinate diagram can be used Visualize the progression of the respective key figure. Intermediate statuses are shown if there is no retrieval cached every minute and placed in front of the next valid retrieval (see § 18.3).
The key figures issued are mostly aggregated. Insofar as they arise from personal or If pseudonymous activity data is derived, the processing takes place for the same purposes and on the same legal basis as described under 18.1, in addition to Art. 6 Para. 1 lit. f GDPR (legitimate interest of the person responsible in a protected retrieval of Operational overviews and information media transmitted during the playout).
Permanent storage of API output: All submitted via /api1 Content – including current key figures, any interim statuses, labeling "Data to be retained by law” and the data sets issued thereunder – may be used by The person responsible and the authorized user permanent and indefinite stored, copied, archived and further processed to the extent that this corresponds to the purpose of the retrieval statutory retention obligation (Art. 6 Para. 1 lit. c GDPR in conjunction with Section 257 HGB, § 147 AO, GoBD) or the legitimate interest in documentation, operation and Legal defense (Art. 6 Para. 1 lit. f GDPR) serves. The person responsible archives each one successful /api1 response on the server side permanently. When the person retrieving it takes it storage option to note; a later deletion of those stored by the user A copy by the person responsible is not technically owed and is not guaranteed.
At the end of every successful /api1 answer, the block follows after a blank line "User feedback:” with all user requests stored on the server (cf. § 18.7) and below in another numbered line the "Current Final revenue” in euros including those below The invoice (Total income in euros and cents as well as number of payments; Deduction of 3% Rapyd with interim result; Deduct checkout fees from €0.25 per receipt or successful Rapyd checkout; Final revenue result in euros and cents). The final revenue is calculated from the documented revenue (Total income less 3% and less €0.25 per income or successful Rapyd checkout).
At the end of the numbered core report, all records required to be retained by law, which are stored encrypted on the server side, expressly stated in the form: "Data to be retained by law: [records]”. If such data records are missing, "none” is displayed. issued. All saved data records are always sent, not just since then added last retrieval. The data sets are part of the API output and are subject to same permanent storage option. On the server side, this data as well as the /api1 archives encrypted (AES-256-GCM) stored permanently.
If the statistics interface is not called up at least every ten seconds, it saves The server usually provides an interim status every minute until the next valid retrieval aggregate statistics. These interim results are stored in a server-side database (SQLite). At the next valid retrieval, the current status and all saved intermediate statuses since the last retrieval are output; then they will Intermediate statuses in the interim status database are deleted. The total as part of the retrieval The submitted response, including interim status, will nevertheless become permanent in accordance with § 18.2 archived.
Purpose: seamless documentation of key figures between calls; permanent Archiving submitted API outputs; Fulfillment of legal retention obligations.
Legal basis: Art. 6 Paragraph 1 Letter f GDPR; for those legally required to keep records Contents Article 6 Paragraph 1 Letter c GDPR i. V. with § 257 HGB, § 147 AO and GoBD.
Storage period: Interim results in the interim results database only up to next valid API call; the overall response submitted and those to be retained by law Data sets permanently or at least for the statutory retention period in accordance with Section 21.1; Activity/duration of use data in accordance with Section 21.
Processing function: PartyUp runs a server-side Interaction and recommendation system ("Engagement”). It is used to (a) interact with To log parties as events, (b) turning them into a personal one to create and update a taste/context profile for each user or identifier, (c) to maintain aggregated popularity metrics per party and (d) when calling up the The environment list assigns a numerical ranking score ("Boost”) to each visible party calculate the sort order in addition to distance, displayed average rating and Pro visibility influenced, as well as the order of Shorts based on Party Boost, Personalize media affinity and cross-feature transfer. In parallel, the same signals – if enabled – feed the situation-related advertising decision (§ 16.2). It is an automated one Profiling to present content, not a decision with legal effect in the sense of Art. 22 GDPR (see Section 25).
Storage form: Events are stored in a server-side relational database
(SQLite) stored in an event history (time stamp, user ID, party ID, creator ID,
Event type, optional numeric value and metadata JSON). Aggregated profiles
("Button”) and party aggregates are stored in a separate structured data set
updated. The assignment is made via a user ID of the form
user:[internal user ID] (registered), client:[pseudonymous client ID]
(local activity identifier) or anon:[session identifier] (Guest without Client ID).
Event types and relative weighting (current system configuration): Detail call (weight 1), Shorts call (1), Shorts skip (−1,2), dwell time on the Details page (0.02 per second view time, top lid currently 30 minutes), Shorts dwell time (0.025 per second), share to a chat partner (4), open a shared Links (3.5), follow-up reaction after share (6), save (5), unsave (−2), star rating (3), Like/Unlike media (3 / −1.5), comment (4), route retrieval (3.5), start navigation (5), Evening plan with event (4.5), party visit recorded via GPS (8). The weights are used to indicate relative strength when learning the personal profile and the party popularity; They are configured by the system and can be used within the framework of the Further development can be adapted without changing the processing purpose.
In particular, the following signals can be processed:
g0/g1) as a further learning basis
time and place. PartyUp does not store or ask biological or social gender
off. Each user ID is created based on existing user and behavioral data (including account details).
and preference features, learned genre/time/place cues) of one of two unnamed groups
assigned. The groups learn their own contextual preferences and activity baselines;
If your personal profile is thin, you can use it softly in ranking, search, length of stay estimation,
Chat and share suggestions are included. A change in assignment is rare and only occurs when
clearly different pattern provided; When you delete an account, the assignment is no longer applicable
aggregated group patterns remain without personal reference;
Profile update: The events become, among other things: Affinities to Creators, parties, tokens/genres/languages, day/time/context preferences, distance vs. Rating bias, media and mainstream/niche bias, own stars, avoidance lists, Impressions/approaches, share circle information and assignment to an anonymous Group of two updated with group-related context patterns. Creator Affinities are subject to a temporal decay factor (currently approx. 0.997 per update cycle), so that older preferences gradually lose weight.
Ranking function (Boost): When building the environment list, a score is created for each party calculated, which is approximately based on personal fit, normalized party popularity and one visibility share (including Pro). The personal fit is taken into account in particular creator/party affinity, token/genre match, own stars, schedule fit, Context fit (day/time/location as well as anonymous group of two), friend/circle signals, avoidance penalties, novelty vs. Familiar weighting from the behavior model and – if your personal profile is thin – optional an initial hypothesis based on anonymized preference profiles (§ 18.5). Soft preferences (e.g. distance vs. evaluation) are also included. Visible cards in the viewport should if possible, avoid jumping; Rearrangements usually affect outside the visible area lying entries. The star ratings displayed on party cards remain unchanged real average values; Any rating premium for Pro visibility only affects the internal sorting weighting (see § 10).
Order on Your parties for Pro: For an account with Pro, PartyUp stores two running totals under the internal user ID: seconds spent on Shorts surfaces (watching, creating or the tip flow) and seconds spent on party lists, plus the time of the last update. The larger total decides only whether that user's own shorts are listed above their parties on Your parties. Other users do not see the totals. The current account-deletion routine does not clear this record, so the totals can remain under the former internal user ID after the username has been removed. Legal basis: Art. 6 (1) (b) GDPR, limited to providing this order for Pro.
Cross-feature learning (Shorts ↔ parties): PartyUp links signals from the digital use (in particular Shorts: views, skips, length of stay, media likes). Signals from the party context in the app and – if approved – from the real one Party behavior (including saving, route/navigation, chat evening plan, recorded via GPS visit). This creates a learning cycle: party behavior influences recommendations and Shorts playout; Shorts and app interactions can reverse the party recommendations improve. Technically, preference signals become domain separated updated (Shorts- vs. Party Crowd/Trust). When ranking a function, the respective factors flow from each Preferences derived from another function only with one dampened transfer weight a. This weight is higher as long as there are few interactions in the target function (cold start / thin profile) and decreases as soon as real usage increases (current system configuration: transfer in the range of a few percent when warm Target domain up to a maximum of about half of the derived affinity with a cold target domain and warm source domain; Specific coefficients can be adjusted as part of further development become). In addition, the affinity transferred from Shorts is upper-limited for each party, so that intensive scrolling alone does not influence party recommendations excessively. For sorting Shorts, the boost derived from the party flavor profile remains an essential signal; As Shorts's own history grows, media-related affinities (likes, skips, length of stay) relative to weight. The real interactions remain decisive with the displayed function (party list or Shorts feed); Cross-feature signals are used for advance personalization and the linking of app and real-world behavior but not the directly observed usage.
Purpose: Personalize and improve discoverability of parties and Shorts ("What is right now, here, in this situation and with this goal for this user relevant – and what plausibly follows from previous app and party behavior?”), Measurement and control of visibility/popularity, further development of recommendation and Advertising logic, abuse and quality observation - not the psychological analysis of the person and not the automated justification of contract rejections.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR, insofar as the processing is for Providing the core functions of "find/view parties in the area” and "relevant Shorts play out” is required; In addition, Art. 6 Para. 1 lit. f GDPR (legitimate interest in a relevant, secure and usable party list and Shorts playout as well as one as little disruptive advertising as possible). Balancing of interests: The interest of the controller and the users in relevant recommendations (including the Linking app and real-world signals) regularly outweighs the interest in complete Omission of sorting/transfer logic because without ranking and without limited cross-feature learning the core function of the platform would be significantly impaired and the processing would be platform-related Interaction signals are limited (no evaluation of private DM content, no legal consequences i. S. v. Art. 22 GDPR). As far as local identifiers in the end device for the assignment of Interaction reports are stored, Section 25 Paragraph 2 No. 2 TDDDG also applies.
Storage period: Event history and personal button profiles basically up to to account deletion or until anonymization/cleaning (§§ 21.2, 23). party popularity Aggregates without personal reference can continue to exist. Share allocations: see above (currently approx. 14 days).
Contradiction: Against processing based on Art. 6 Para. 1 lit. f GDPR You can lodge an objection in accordance with Art. 21 GDPR (see § 27.1). Practically you can Reduce interactions (e.g. GPS off, no shares/comments), at Settings → Advertising deactivate the personalized advertising display, use Ad-free/Pro and your delete account; already formed aggregated popularity figures that can no longer be linked to individuals or market key figures as well as completely anonymized preference profiles (§ 18.5). remain preserved. The switch "Personalized advertising” only restricts the display of advertising, not party list personalization. For estimating the length of stay, see separately § 18.6.
Processing function: Parallel to the personal user/taste profile (§ 18.4), PartyUp maintains storage completely separate from the account anonymized preference profiles ("wealth of experience”). Its technical function is to to condense recurring behavioral patterns without personal reference and to create new or thin ones profiled users as mere Initial hypothesis for personal Use sorting logic - not as a fixed assignment and not as an identity replacement.
Content/anonymization measures: The profiles do not contain any personal data and no identifiers that can be traced back to a specific person, an account, party ID, creator ID, precise geo cells or others Enable identifiers. Only aggregated patterns are saved (e.g. relative genre/style weights, day of week and time of day preferences, coarse preferences on distance vs. evaluation, media affinity, mainstream vs. niche bias, size preferences). Technical and organizational measures to avoid the Re-identification includes in particular: waiver of user/party/creator/geo identifiers, Limitation of the set of characteristics to aggregated weights, storage separately from the account and Taste Store as well as no storage of the post origin after acceptance.
Structure and matching: The anonymized profiles are already during normal use continually built and developed – not just when an account is deleted. Posts from your personal profile in the Experiences are subject to a system cool-down time (currently approximately 8 minutes between posts) to limit multiple entries. Detects PartyUp on a current User behavioral signals that are sufficiently similar to an existing anonymized profile (Similarity measure, currently cosine similarity with a minimum threshold of approximately 0.72, and only if your personal profile is still thin), this profile can be used as a starting hypothesis ranking calculation (§ 18.4). It is not adopted unchanged: This personal user profile then continues to learn independently based on the actual one behavior. Two users can start with the same anonymized profile and then connect develop completely differently. Deviations from the hypothesized picture are again anonymized in the further development of the wealth of experience. If account deletion can occur before removal a final anonymous contribution is made to the personal profile; After that, any reference to the deleted account (§ 23).
Purpose: faster and more efficient assessment of new or little-known ones User ("Cold Start”), reduction of repeated full calculations based on individual behavior, improvement the recommendation quality as well as long-term preservation of anonymized learning experience regardless of individual accounts – without equalizing all users and without reference to identity.
Legal basis / personal nature: As far as the saved ones Preference profiles are actually anonymized and not a re-identification of a natural one person, they are not subject to the scope of application of the GDPR personal data (see Recital 26 GDPR). The upstream derivation off Behavioral data on the personal profile is governed by § 18.4 (Art. 6 Para. 1 lit. b and/or lit. f GDPR). In individual cases, re-identification should be technically possible If it becomes possible, the affected data sets would again be treated as personal; the The person responsible takes the above measures to avoid this.
Storage period: The anonymized preference profiles can be stored permanently remain part of the general learning system, even if the original one User account is deleted (see § 21.2, § 23). They then contain no information more about which user the original behavior came from.
Objection/information: Since anonymized data has no personal reference, There are no claims to information or deletion in this regard in accordance with Art. 15/17 GDPR regarding individual profile entries. Against personal personalization User account remains unaffected by § 27.1.
Processing function: As far as a user shares GPS presence and chat partners If you have not disabled notification of nearby parties, PartyUp can contact these partners show a list of who is currently at a particular party (profile picture or first letter, username). Instead of the previous duration of attendance, the list shows a estimated remaining length of stay (phrasing: "probably still [duration] on site”). The estimate is an automated, heuristic forecast. She unfolds no legal effect and does not create an obligation to actually stay that long (see § 25).
Recipients / Visibility: The list and estimate are not public. They are only displayed to registered direct chat partners ("friends”) who have the respective Open party friends list, and only to the extent that the person concerned shares presence (GPS on, nearby notification not off in the chat, no Secret mode, no blockage on both sides, fresh presence data). Contents of private direct messages are not read and are not included in the estimate included.
Input data and logic (current system configuration): The model mixes User-, location- and time-related average stay times with contextual factors and learned ones weights. In particular, it can use the following observable signals:
The individual values are weighted, averaged and multiplicatively adjusted using context factors. Missing values are replaced by neutral assumptions (cold start, currently typical a base stay time in the range of approximately 45-180 minutes depending on the time of day and weekend). The remaining time displayed has a lower and upper limit (currently typically at least about 5 minutes, at most about 8 hours).
Learning / updating: When leaving a party (or moving to one others) the actual length of stay is stored, provided it meets a minimum threshold reached and does not exceed an upper limit (currently typically around 4 minutes up to approximately 16 hours; shorter GPS jitters and extremely long errors are discarded). The model compares prediction and reality, writes average values (also with stronger ones weight of recent stays) and adjusts personal and – more slowly – global weights and a bias. A limited history of completed stays is maintained per user (currently up to approx. 40 entries with duration, forecast errors, travel route and Social mode, without chat texts). During an ongoing stay can be at longer intervals (currently about 5 minutes) an internal estimate snapshot is saved to the presence so that learning knows the last status shown.
Purpose: To give friends an everyday orientation as to how long someone has been is expected to still be on site; Improving the quality of estimates over time; none Monitoring outside shared GPS presence, no personality assessment and none Decisions about access, prices or contract conclusions.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR, insofar as the notification the friend's presence including a remaining time estimate for the contractually offered one Social/GPS function included; Furthermore, Art. 6 Para. 1 lit. f GDPR (legitimate Interested in a useful orientation limited to already shared presence for chat partner). The underlying GPS survey requires approval on the end device (Art. 6 Para. 1 lit. a GDPR in conjunction with Section 25 Para. 1 TDDDG, see § 14.1). Balancing of interests: The estimate is only shown to partners who allowed to see presence anyway; she does not use private chat texts; it is as an estimate marked and without legal consequences. Interest in this orientation regularly prevails the interest in complete omission, especially since the function is disabled by GPS off, nearby off, Secret mode, blocking or account deletion can be switched off.
Storage period: Personal length of stay profiles, weights, biases and the limited residence history until account deletion or cleanup (§§ 21.2, 23). Ongoing presence snapshots only for the duration of the current stay. Aggregated Local/global resources without user identification can also continue to exist and then allow no conclusions can be drawn about the deleted account.
Contradiction and control: Against the provisions of Article 6 Paragraph 1 Letter f You can object to the GDPR-based estimate in accordance with Art. 21 GDPR (see § 27.1). In practice, you do not appear in the friends list when GPS is turned off Nearby notification is disabled in chat, Secret mode is active, there is a blockage or you leave the party location. When the account is deleted, the personal information no longer applies Duration of stay profile.
Accuracy: The duration shown is an estimate and may vary from the actual length of stay may vary. It does not establish any statement about intentions or health or personality and no obligation to leave the place at a certain time.
On the Home page Users can tap on the brand font "PartyUp” top left (depending on the representation and font often as "PARTYUP” readable) a dialog window Wish open. There you can personal ideas, suggestions for improvement and wishes as free text (currently up to 2,000 characters). The entered text and a timestamp are processed Submission and – for registered users – the internal user ID and user name; without After registering, the entry can be sent anonymously.
Purpose: Receiving personal suggestions and product ideas; Evaluation by the operator; Output in the protected statistics interface /api1 under "User feedback:” (see § 18.2).
Legal basis: Art. 6 Para. 1 lit. f GDPR (legitimate interest in user-oriented further development); as long as the entry is voluntary and without registration is sent, in addition to Art. 6 Para. 1 lit. a GDPR (voluntary notification).
Storage period: Entries are stored permanently on the server and for everyone valid /api1 retrieval is output in full under "User feedback:” until it is received from those responsible will be deleted. It is currently not possible for users to delete individual entries intended as self-service; The rights of those affected pursuant to Section 27 remain unaffected.
Personal data will only be passed on to third parties if this is necessary to fulfill the contract is necessary, there is a legal basis, you have consented or we have consented by law are obliged to do so. As part of PartyUp, the following external bodies in particular can receive personal or technical data:
Rapyd Europe UAB or affiliated companies – processing subscriptions and One-off payments via the checkout interface embedded in PartyUp (Rapyd Checkout Toolkit), including optional methods such as Apple Pay, Google Pay, Amazon Pay, Klarna, Link, PayPal or SEPA, loading PartyCash, payout of a ticket purchase paid through Rapyd to the payout account stored for that party, as well as storage of payment methods for advertising billing (see § 15, § 15.1, § 15.2). A ticket paid from PartyCash is not paid out through Rapyd. Map data is processed in Rapyd components and not persistently at PartyUp saved. Further information: Privacy Policy of Rapyd.
Sending password recovery emails and, after a successful ticket purchase, the ticket email with its attached files via Brevo (Sendinblue SAS, France), transactional mail API over TLS (sender noreply@partyup.pro; cf. § 7.1, § 15.1, § 16.4). The ticket email is sent only when the account has an email address. Recipient address, subject, message content and, for a ticket, the attached files are transmitted to Brevo so the mail can be delivered. Replies to the sender address are not expected or evaluated. Advertising billing emails will not be sent. Further information: Privacy Policy of Brevo.
Legal basis: Art. 6 Para. 1 lit. b GDPR (necessity for correct party location information, Chat evening plans / voice function) or Art. 6 Para. 1 lit. f GDPR. The data protection information also applies respective provider.
Bebas Neue and DM Sans are delivered by PartyUp itself. Loading the typefaces does not open a connection to Google (fonts.googleapis.com / fonts.gstatic.com).
STUN servers from Google can be used to establish connections for calls and live cameras (stun.l.google.com / stun1.l.google.com) can be used. IP addresses and technical connection data is processed. Legal basis: Article 6 Paragraph 1 Letter b GDPR.
For the recognition of QR codes and barcodes (chat scan as well as clickable codes in Shorts). Scripts can be reloaded from a CDN (cdn.jsdelivr.net, including jsQR and possibly ZXing). For the route map, Leaflet can be loaded via a CDN (unpkg.com). This creates Technically common connection data (especially IP address). The evaluation of the Shorts frames takes place locally in the browser; Recognized links/codes are only displayed in an external after the user clicks App or opened in the browser. Legal basis: Art. 6 Para. 1 lit. f GDPR or Art. 6 Para. 1 b GDPR.
If users leave external links to parties, the server can do accessibility checks to the target system. Technical retrieval data is generated. Content and Data protection practices of the target pages are not subject to the controller of PartyUp.
For the route view to a party as well as for evening routes from chat plans, map data and Routing services used. The current device location (after approval) as well as Destination coordinates (party or stops of an evening plan) can be transmitted to the following services:
Once the device location has been approved, you can use turn-by-turn navigation in the route map Voice announcements can be used; PartyUp processes maneuver and position data locally. Triple-clicking on the map leads to the Pro page; no additional ones are involved personal data transmitted.
Legal basis: Art. 6 Para. 1 lit. b GDPR (route function) and Art. 6 Para. 1 lit. a GDPR / § 25 TDDDG for access to the device location. The location is used for route calculation transmitted to the PartyUp server and from there to the respective routing service; a permanent one The user location is stored on the PartyUp server as part of the pure Route function not (unlike GPS presence for chat messages, see § 14.1).
Authorized daily API key holders receive aggregated via /api1 Operational statistics and the data sets required to be retained by law. These recipients may permanently store the data received (§ 18.2). Legal basis for transmission: Art. 6 Para. 1 lit. f GDPR or Art. 6 Para. 1 lit. c GDPR, if required to be retained content is affected.
It may be passed on to authorities or third parties if this is necessary to fulfill a legal obligation Obligation (Art. 6 Para. 1 lit. c GDPR) or for legal defense (Art. 6 Para. 1 lit. f GDPR) is required.
To display party texts (especially descriptions) in the selected interface language
The viewer can PartyUp text excerpts of user-generated content via the interface
/api/content-translate send to external translation services. The primary becomes
Translation endpoint used by Google ("gtx” client); in the event of failure, error or
Overload can alternatively be MyMemory (api.mymemory.translated.net) used
become. The text to be translated (shortened if necessary) and the target language are transmitted; the
Providers receive the usual technical connection data (in particular the IP address of the
PartyUp server). Party names are not machine translated.
Translation results can be saved on the server side in a cache (currently file
contentTranslateCache.json) under one derived from the text and target language
Keys must be kept available to avoid repeated calls. The cache is used for
functionality and performance; it is not designed as a personal user profile.
Purpose: Comprehensible presentation of party information that has already been published in the
language of the viewer.
Legal basis: Art. 6 Paragraph 1 Letter b GDPR or Art. 6
Paragraph 1 lit. f GDPR (legitimate interests in multilingual use of the
platform).
The data protection information of the respective providers also applies. As far as processing in
Third countries, see § 20.
As far as services with headquarters or server location outside the European Economic Area are used (in particular Rapyd, Google services for machine translation and STUN, MyMemory and possibly CDN providers depending on the processing location) may be transferred to third countries take place. Such a transfer only takes place provided that the requirements of Art. 44 ff. GDPR are met (e.g. adequacy decision according to Art. 45 GDPR or appropriate guarantees according to Art. 46 GDPR, including standard contractual clauses).
The operator has the specific transfer mechanisms used and - if necessary - Additional measures must be documented and disclosed upon request.
Personal data is only stored for as long as it is necessary for the respective purposes or as long as there are legal retention requirements. In particular:
The person responsible is obliged to document certain documents and data to keep. This applies in particular to:
Legal basis: Art. 6 Paragraph 1 Letter c GDPR i. V. with § 257 HGB, § 147 AO and the GoBD; additionally Art. 6 para. 1 lit. f GDPR (legal defense, traceability, operational documentation).
Storage period: at least for the respective statutory retention period (Typically ten years under commercial law; under tax law in accordance with Section 147 AO currently typically eight or ten years for each type of document), starting with the end of calendar year in which the document was created or the last entry was made; Furthermore, as long as the storage is necessary to fulfill legal obligations or for It is necessary to assert, exercise or defend legal claims. One premature deletion at the request of the person concerned does not apply, insofar as Article 17 Paragraph 3 lit. b and/or lit. e GDPR conflicts.
This data is encrypted on the server side (AES-256-GCM) in a separate permanent Memory led. Every time /api1 is successfully retrieved, all saved ones are saved Data sets under "Data to be retained by law:” are also output. The person calling up is allowed to do so save permanently (§ 18.2).
The person responsible takes appropriate technical and organizational measures in accordance with Art. 32 GDPR to protect personal data, in particular:
Despite measures, absolute security cannot be guaranteed. Users should have strong, Use unique passwords and keep access data confidential.
Users can permanently delete their account using the delete function provided in the application (logged in in particular via the "Delete Account” dialog on the home page). Processing function: The deletion routine runs a specified one on the server side Cleanup sequence to remove account-related personal data or - as far as the integrity of ongoing public discussions is required - to anonymize, and at the same time to obtain aggregates that are legally required to be retained and have already been anonymized.
Secret mode as a reversible alternative in the delete dialog: In the same dialogue before final deletion Secret mode pointed out and a switch offered (see § 8). If the user activates the switch, only the Secret mode status set on account (visibility-related filters as in § 8); the dialogue is closed, the remaining usage functions remain available to the user. It finds no Account deletion and no cleanup consequences of this paragraph will take place. The Secret mode can be deactivated using the same switch in the reopened dialog as well as in the Settings.
Two-step confirmation of deletion: The irrevocable account deletion is technically tied to a two-stage confirmation in the deletion dialog. The first time you press the Buttons "Delete Account” will cause deletion not executed; instead will the information area with the Secret mode switch (red information lettering and switch line immediately above the button) is visually highlighted - analogous to marking an unfilled one Mandatory field – to point out the reversible alternative again. Only on the second one Pressing the same button within the same dialog session sends the deletion request to the server and the subsequent cleanup sequence is executed. Will be the dialogue closed in the meantime, the interim confirmation is no longer required; when you open it again it starts Two-stage from the front. The deletion remains an explicit, repeated one Action is bound and does not occur through the mere activation of the Secret mode.
The deletion involves the following steps in particular:
Activity identifiers and useful life values formed from them, those of the internal user identification can be assigned as part of the account deletion or a subsequent cleanup be removed or anonymized; already aggregated and no longer related to individuals Overall statistics can be retained. Required to be retained by law Payment, billing, contract and API archive data will remain unaffected and will not deleted (Art. 17 para. 3 lit. b and lit. e GDPR in conjunction with § 257 HGB, § 147 AO, GoBD; see § 21.1). Payment and billing details at Rapyd can be made from legal reasons exist longer. advertising and statistical data sets can be retained - provided they are not personally identifiable be cleaned up subsequently. As far as individual secondary stocks (e.g. global counters without User reference) are not technically attached to the delete path, they do not contain any for identification the identifiers required for the deleted user.
Legal basis for anonymization/preservation: Art. 6 Paragraph 1 Letter f GDPR (Integrity of existing discussion and evaluation statuses; avoidance of loss of context for remaining users) as well as compliance with the deletion requirements in accordance with Art. 17 GDPR in such a way that which takes into account the rights of other users and the purpose of the platform (see also Art. 17 Para. 3 GDPR, where relevant).
After account deletion, the session ends. Settings and cookies stored locally in the browser are not automatically completely removed by the server; the user can do this themselves Clear browser.
The provision of username and password is for the use of account-related functions required. Sign-in and registration use the same fields; without both values neither login nor account creation is possible. An email address is not required for standard login, for advertising, or for buying a ticket. If one is stored, it is used for optional password recovery and, after a ticket purchase, for sending the ticket files. The information requested by the payment service provider is for payments required. The use of certain optional functions (GPS, camera, microphone, calls, device contacts) requires a release on the device beforehand; Without approval, the remaining functions basically remain usable. The activity measurement and the interaction messages for personalization/statistics are for the Operation of the corresponding functions is technically intended; without local activity ID or Without a session, individual key figures and recommendations can be restricted or only anonymized be recorded.
There is no automated decision-making, including profiling in the sense of Art. 22 Paragraphs 1 and 4 GDPR, which has legal effect on you or you similarly significantly impaired (e.g. no automated rejection of a Conclusion of the contract, no blocking of an account and no price fixing solely on the basis of this a score without human verification, if required by law).
Technical classification: PartyUp uses interaction, context and Situation signals to determine the order of displayed parties and the play of Shorts personalize (ranking score / "boost”, cross-feature transfer Shorts↔Parties, see § 18.4), To weight popularity/visibility and – if "Personalized "Advertising” is active – to decide whether and which advertising will be shown in optional slots (see § 16.2). Anonymized preference profiles (§ 18.5) can be used as The initial hypothesis is incorporated without equating users and without personal reference in an anonymous manner Store. Additionally, PartyUp estimates one from GPS presence and observable context signals expected remaining length of stay and only shows it to authorized chat partners (see § 18.6). This represents a form of profiling for the presentation of content, the advertising display and a social orientation aid. The consequences are limited to the order or visibility of party cards and Shorts, on which Shorts feed Auto shows (all shorts or only party moments; the user can choose the feed directly, see § 9), on optional commercial breaks and on a time marked as an estimate in the friends list; Users can have parties continue to search, open, save, rate, comment and - if activated - Complete paid services via Rapyd. There will be no scoring decisions about creditworthiness, access to essential services outside the Platform representation or comparable legal positions have been taken.
Aggregated usage statistics and the further development of permanent/price offers serve this purpose Operation and also do not make a decision with a comparable effect in the sense of Art. 22 GDPR. As far as personalization or advertising selection is based on Art. 6 Para. 1 lit. f GDPR is supported, you have the right to object in accordance with Art. 21 GDPR (see § 27.1). You can practically display personalized advertising under Settings → Advertising deactivate; The party list personalization remains unaffected and can be objected to, Interaction reduction, Ad-free/Pro or account deletion can be restricted or terminated.
PartyUp is not specifically aimed at children under 16 years of age. Provided that a child has consent would be necessary in relation to information society services, Article 8 GDPR must be observed. Guardians are requested to supervise the use of minors.
According to the GDPR, depending on the requirements, you have the following rights in particular:
You have the right to object at any time for reasons arising from your particular situation the processing of personal data concerning you, which is based on Art. 6 Para. 1 lit. e or lit. f GDPR, to lodge an objection; this also applies to a reference to these provisions supported profiling. The person responsible then no longer processes the personal data, unless he can prove compelling legitimate reasons that protect your interests, rights and Freedoms prevail, or the processing serves to assert, exercise or defend of legal claims. This particularly applies to activity measurement Interaction/personalization processing for party list sorting (§ 18.4), which Personalized advertising display (§ 16.2) and key figures derived from this, insofar as they still relate to a person. Completely anonymized preference profiles (§ 18.5) are excluded from this if there is no longer any personal reference. The "Personalized” option Advertising” in the Settings limits the advertising display to a purely contextual one selection on; party list personalization remains unaffected.
The data protection supervisory authority responsible for the person responsible depends on the location of the person responsible. A list of the German supervisory authorities is, among others. about the Federal Commissioner for Data Protection and Freedom of Information (BfDI) and the websites available to the state representative. Additionally:
[Responsible supervisory authority – name, address, contact]
To exercise your rights, please use the contact details mentioned in Section 1. To We may request an identity check if this is necessary and is proportionate (Art. 12 Para. 6 GDPR).
PartyUp stores and transmits content posted by users. The person in charge is not obliged to monitor all content in advance (see also the Telemedia law principles on the responsibility of service providers). For specific ones References to illegal content can be checked and - if necessary - blocked deletion takes place.
PartyUp expressly distances itself from all disputes, conflicts, insults, Harassment, abuse, mistreatment, threats and violence among users – whether online in the application or outside of it - as well as from all circumstances that arise, in connection with the use of PartyUp, with parties, chats, Shorts, live cameras or published moments can arise. PartyUp is a technical one Platform for organizing and presenting parties and for communication; the The person responsible assumes no responsibility, liability or guarantee for the behavior of individuals Users among themselves, for personal disputes, for damages from contacts between Users, for content of moments (including people, places and actions depicted) or for actions taken by users in connection with parties or the use of PartyUp make. Each user is responsible for their own behavior, for the moments they share and for the Responsible for compliance with applicable laws. In case of danger to life, limb or freedom please contact the relevant authorities (e.g. police).
The following also applies to published moments: Consent to publication is granted by the User by pressing "Share moment” (see § 9, § 12). PartyUp does not check the content of moments in advance and distances itself from recording, content, distribution and all related circumstances, claims and disputes.
Applies to live cameras, live streams, live shorts, live image analysis and media generated from them additionally § 9a – equally for the device's own front camera, via connection Connected cameras and IP/network cameras connected via WLAN/LAN: The Party operator is responsible for setup, hosting, operation and for disputes and damages fully responsible in connection with the cameras; PartyUp is just that technical service and assumes no responsibility in this regard. PartyUp distances itself expressly from the content and setup of each such live stream.
For published Crew Rewards the following applies in addition (see § 9b): the organizer must under all circumstances honour a published Crew Reward and provide it on the release page. PartyUp is only the technical platform for the card, the QR code and the release page and distances itself from whether the organizer actually hands over the perk. Disputes about fulfilment are between organizer and guest.
We reserve the right to adapt these Privacy Policy if the legal situation changes Functions of PartyUp or the processing processes change. The current, Version available in the application. In the event of significant changes, further information will be required or require consent, we will indicate this in an appropriate manner.
Should a provision of this Privacy Policy be or become invalid, this remains the case The validity of the remaining provisions is unaffected. The invalid provision applies instead legally permissible regulation that comes closest to the purpose of the invalid regulation.
The law of the Federal Republic of Germany applies, taking into account the mandatory regulations GDPR. Mandatory consumer protection regulations of the country of residence remain unaffected, to the extent that applicable (Cookies: ).
End of Privacy Policy – PartyUp
Document version from October 29, 2026 (update: private parties and the chat invitation
to selected friends, §§ 2, 4, 9, 11.4, 17.1, 21.2; the ticket QR code also carries the
party identifier, § 15.1; previous version October 25, 2026: ticket purchase without a
required email address, in-app ticket files, PartyCash, and saving the party after a
ticket purchase)
Welcome to PartyUp. This short guide shows you what you can tap in the app and what happens next – so you can settle in and enjoy the night.
PartyUp is the place to discover parties near you – and to host your own. Browse the list, open a party, save it, leave a comment or share it with friends. If you host, you add a name, time, place and optional photos or videos.
You can also swipe through Shorts, post your own Short, chat with Friends, share an on-site Moment, and – if you like – show a live view from your own party. Pro users get a few extras. You can run your own ads if you want more people to see you.
Looking around works without an account. To host, save, chat or become a Pro user, tap Sign in in Settings.
Open Settings (the gear at the top right). There you sign in or create an account.
Your public name then looks like @PartyUp.yourname. Tap that name in Settings if you ever want to change it. Email is optional. You can add one later under Settings → Email if you ever want to reset your password.
To sign out, use Log out in Settings. If you ever want to delete your account, tap the icon to the left of “PartyUp” on the home page while you are signed in.
The bar at the bottom takes you to the main places:
At the top of the home page you will also find Search, Settings and the PartyUp name. Tap the name if you want to send us an idea – more in section 15.
Home shows published parties. Your unpublished drafts stay under Your parties. If you are at a party, Share moment appears on that card.
Tap the search icon at the top and type a party name, place or person.
Next to your name you can switch the list to match the evening:
Tap Date, pick a day and only see parties on that day. Tap the chip again to show every day.
Turn on GPS if you want to see how far a party is and put nearby ones first. You can leave this on in Settings so you do not have to switch it every time.
One tap on a card opens the party page: time, place, description, photos, comments and a route. A short clip may play before the page opens. Pro users and anyone with Ad-free do not see those clips.
Double-tap a card to jump into comments. A swipe can open sharing.
Under Shorts you swipe through short clips – like other full-screen video feeds. Swipe up or down for the next one. Tap through to the matching party whenever you like.
If a host has turned on a live view for Shorts, those clips can appear in the same feed.
You can like a clip, share it or save it. Saved shorts live under Your parties → Saved parties & Shorts.
You can also post a Short that is not tied to a party. Under Your parties tap + Short +, then Record or Upload. Add a short line if you like, then share. That clip can show up in the general Shorts feed.
Under Settings → Shorts – and in the same place under Your parties – you decide what that feed shows:
Under the party name, tap 1 to 5 stars. With an account your stars stay and join the average.
The save button keeps a party for later. Find it again under Your parties → Saved parties & Shorts.
Share sends the party to a chat or copies the link. Shared shorts also land in your saved Shorts folder.
Hosts get ready-made pictures on the party page – for Instagram, WhatsApp, posters or a QR code. Share saves or sends the picture. A double tap opens a big preview.
If you like a location, you can follow it. The name then stays easy to spot in Shorts.
When you are at the party, tap Share moment. Take a photo or video, check the preview, add a short line if you like, then share. Your moment appears with the party’s photos and can show up in Shorts.
Route opens a map from you to the party. Pick car, bike, walking or transit, then tap Start route. The little flag closes the map again.
Every party has a comments thread – a shared chat just for that night.
If friends from your chats are at the same party, you can see that on the card and on the party page.
When a party offers tickets, you can buy one online for that party before you go. Look under the entrance price: the option to buy tickets is shown only then. The price is that party’s entrance fee plus 0.25 €. Open the option, check the preview, and confirm the purchase. You need an account and an email address on it. After payment, PartyUp sends the ticket to that address. If the party does not offer tickets, the option is not shown.
Go to Your parties. Here you add events and your own Shorts, see drafts, open ads and change how you look in the app.
Tap the round picture at the top. Take a new photo or upload one, move and zoom until the circle shows what you want, then tap Apply – or swipe left.
Next to your photo you see your followers and a flame for your Streak. Share a moment to start it. Share again within a week to keep the flame going. Tap the numbers to open the lists.
Tap Add party and fill in what guests should see:
Some repeating schedules have a one-off publish fee (daily 1 €, weekly 75 cents, monthly 55 cents, yearly 50 cents; fixed dates are free). A Pro user publishes repeating parties with no extra fee. Drafts wait under “Your parties” until you publish or delete them.
After you publish, Share Kits appear on the party page. People can view, save, comment or write to you.
On the party form, tap Reward your guests for bringing friends. You create a crew card: how many friends someone should bring, and what they get – a free drink, a snack, or whatever you promise.
When the guest has brought their crew, they show you a QR code in PartyUp. After a successful scan, the release page opens. That is the moment you hand over what you promised.
While you edit a party you can connect up to four cameras – your phone or another camera you have nearby. Nothing goes public until you connect a camera and switch on the options you want.
A green light at the top means your live view is on. You can turn it off anytime in the party form.
Under Settings → Extensions → Pro you can become a Pro user for 4.50 € per month. You can cancel whenever you like.
As a Pro user:
Your parties → Ads is where you run your own picture or video ads. If you would rather watch without ads, open Settings → Ad-free (2 € per month) – or become a Pro user, which already includes that.
The Friends tab is your inbox. Search for someone with @PartyUp. plus their name – or show your QR code from Settings, or scan theirs in the chat list. If you allow cookies, PartyUp also reads the contacts on your device. That is used to find friends who already use PartyUp, to suggest friends more accurately, and to recognize mutual friends so that more suggestions can be shown.
In a chat tap Plan, pick a place and how long the night should last, then Create. PartyUp suggests parties nearby. After you send the plan, Route opens the map for the evening.
When GPS is on and you are really at a party, friends can see that without a message you type yourself.
In a chat. A private chat, a group and party comments all work the same way. Open the location button. The switch turns on by itself the first time you open that chat. It stays off until then, also when someone else starts the chat or adds you. You can switch it off for that chat only. The switch is called Partys. That chat then gets a short message when you arrive, and another when you leave or go to a different party. This only happens if the party is within 10 km of someone else in the chat. In a private chat that is your friend. In a group or in party comments it is the nearest other person there. The arrival message can include the party name and that distance, and it opens the party.
On your profile. While you are at a live party, a badge can appear on your profile. The badge says ON FIRE. Tap it to open that party. Anyone who can open your profile can see the badge, even without a chat. You still see it on your own profile. A friend does not see it if you switched their chat off. Secret mode and a block hide it from other people.
In Settings, open the panel Auto-Partymitteilung. You write both messages there. {name} becomes the party name. {distance} becomes the kilometres. One switch shows the badge on your profile. That switch is called Öffentlich. Switch it off if you want the badge hidden.
Pin, archive or delete a chat whenever you like.
In a private chat you can start an audio or video call. Party comments do not have calls.
When you are signed in, Settings also shows your QR code and your @PartyUp name.
Have a wish, a small idea or found something that could be nicer? On the Home page tap the PartyUp name at the top left (sometimes shown as PARTYUP). Write a few words and tap Send.
You can send a wish while signed in or as a guest. Thank you – we are glad you wrote.
Open Settings → Blocked users. You can mute one chat or block a person completely. Then their messages and parties no longer appear for you.
PartyUp works in the browser. On many phones you can add it to the home screen and open it like any other app. If that is available, a short hint appears on Home. If you allow notifications, PartyUp can let you know about a new chat, a call or a new story.
Once published, it sits on Home with everyone else’s. Drafts stay under Your parties. When you are there, Share moment appears on the card.
A photo or video you share from the party. It shows with the party’s media and can appear in Shorts.
Under Your parties, tap + Short +. Record or upload a clip that is not tied to a party. It can appear in the general Shorts feed.
Ready pictures on the party page so you can post or print your event in a few taps.
In a chat tap Plan, choose place and duration, send it – then Route if you want the map.
With GPS on, two things can happen while you are really there. A private chat, a group and party comments all do this the same way. The switch turns on the first time you open that chat, and it is called Partys. The chat then gets a short arrival message if the party is within 10 km of someone else in it, and a short message when you leave. On your profile the badge ON FIRE can show the live party. Its switch is called Öffentlich, under Settings and Auto-Partymitteilung. A friend whose chat you switched off does not see the badge. Secret mode hides both from other people.
It shows how far parties are, sorts nearby ones first and helps with routes. You switch it on only if you want that.
Yes, when that party offers tickets. On its page, the option sits under the entrance price. The ticket is for that party. PartyUp emails it to the address on your account after you pay.
Go to the party page. After you buy a ticket, the party is also listed under Gespeicherte Partys. Then open the button Tickets kaufen. At the bottom of that window you see Gekaufte Tickets, as long as you still have tickets that have not been redeemed. Open that list. The entries are Ticket 1, Ticket 2, and so on. Each entry opens that ticket with its QR code. A redeemed ticket leaves the list. The button stays if the host stops selling, until none of your tickets are left. If the account has an email address, the same files are sent there as well.
Not just to look. For hosting, saving, chatting, becoming a Pro user and running ads, yes.
Settings → Language, then pick yours in the list.
Search @PartyUp. plus their name, show your QR code in Settings, or scan theirs in the Friends tab. If you allow cookies, PartyUp can also match people from your contacts, recognize mutual friends, and suggest more friends.
On Home, tap the PartyUp / PARTYUP name, write, tap Send.
Settings → Privacy Policy. Close it with × or by swiping right.
Have a good night – find a party, bring friends, or host your own.