Community & Content Guidelines for the PartySpot App
Status: June 2026. This version is undergoing final legal review; individual items marked in italics in parentheses are still being completed.
1. Purpose and Scope (supplementing the Terms and Conditions)
(1) These Community and Content Guidelines (hereinafter “Guidelines”) specify the rights and obligations relating to the posting, sharing, rating, and commenting on content in the “PartySpot” mobile app (hereinafter “App”). They supplement the General Terms and Conditions (hereinafter “T&C”), in particular §§ 8 (User Content), 9 (Prohibited Content, Moderation, and Deletion Rights), and 15 (Minors), and are, in case of doubt, to be interpreted in accordance with them. In the event of conflicts between these Guidelines and the T&C, the T&C shall prevail.
(2) The provider and the party responsible for the application of these Guidelines is:
SZuCO – Dr.-Ing. Piotr Szegvári (sole proprietor) Zum Weizenring 14 14469 Potsdam Germany Email: info@partyspot.app Fast electronic contact channel: Contact form in the PartySpot app (Settings → Help & Support) VAT ID No. pursuant to § 27a UStG [German VAT Act]: DE458930351
(hereinafter “Provider”, “we”, or “PartySpot”)
(3) These Guidelines apply to all users of the App — hosts (organizers of a party) as well as guests (participants in a party, including in the case of anonymous participation under a freely chosen alias). By creating or joining a party, you acknowledge these Guidelines as binding. A lack of registration (anonymous guest use) does not exempt you from compliance with these Guidelines.
(4) Active consent before posting content. Every user — including the anonymous guest joining without registration — must actively confirm these Guidelines when joining a party or, at the latest, before the first upload, rating, or commenting on content (confirmation step in the join/upload flow). Without this active confirmation, posting user-generated content is technically not provided for.
(5) The App is a pure mobile app (iOS/iPadOS and Android); no web version is offered. There is no chat function; interaction between users takes place via photo comments that are attached to the respective photo and not to a profile. These comments are nonetheless user-generated content, to which these Guidelines — including the reporting and moderation procedure (Sections 5 to 7) — apply in full.
(6) Closed vs. open parties. The photo and video gallery is limited to the respective group of participants of a party. A distinction must be made here:
a) Purely private/closed parties: Joining is possible exclusively via QR code or the eight-digit join code within a personally connected circle; the gallery thus forms a closed group.
b) Public parties and parties with the joining of strangers: The App additionally enables public parties as well as — when the opt-in-based “Parties Nearby” function (radius-based discoverability via geohash) is activated — the joining of persons who are not personally connected. In this case, user-generated content may become accessible to a group of persons who are not personally connected or potentially indeterminate.
(7) Classification as a hosting/platform service. Insofar as parties are accessible exclusively to a personally connected, closed circle, we treat the service as a hosting service. If, on the other hand, content becomes accessible to an indeterminate number of third parties via public parties or the radius-based joining of strangers, the service may in this respect be classified as an online platform within the meaning of Art. 3 lit. i of Regulation (EU) 2022/2065 (Digital Services Act, DSA). We design our procedures so that they also meet the more extensive platform requirements (in particular Art. 16, 17, 20 DSA). The final classification, as well as any exemptions for micro and small enterprises (Art. 19 DSA), must be clarified with a lawyer and kept consistent with the T&C (§§ 8, 9).
(8) You are solely responsible for all content you post and for your conduct in the App (§ 8 para. 1 T&C).
2. Permitted Use
(1) PartySpot serves to shape celebrations together: music control (remote control of a Spotify or Apple Music app installed on the host device, no streaming of our own), collaborative music voting, as well as a shared photo and video gallery with photo voting and comments.
(2) Permitted in particular is:
- posting your own photos and videos (videos up to a maximum of 30 seconds, compressed on-device) to which you hold the necessary rights and for which the consents required under Section 4 have been obtained;
- factual, respectful commenting and rating (thumbs up/down) of photos as well as voting on songs;
- suggesting music tracks within the scope of the voting and playlist functions configured by the host;
- choosing an alias or display name that does not infringe the rights of third parties and does not violate the law or public morals (cf. § 3 para. 4 T&C).
(3) Use must take place within the scope of the intended purpose. Use contrary to that purpose (e.g., posting advertising unrelated to the party, spam, mass uploads unrelated to the party, circumventing technical protective mechanisms) is prohibited.
(4) You are solely responsible for all content you post and for your conduct in the App (§ 8 para. 1 T&C).
3. Youth Protection and Minimum Age
(1) Minimum age / age rating. The App is intended for persons aged 16 years and older. The age rating stored in the Apple App Store and the Google Play Store (Apple Age Rating, Google Content Rating / IARC) must be kept consistent with this minimum age and must be definitively established before publication. The age-related consent and validity thresholds additionally follow from § 15 T&C (in particular: consent pursuant to Art. 8 GDPR from the age of 16; consent to the use of one’s own image from the point of capacity for discernment, as a rule from the age of 14; legal capacity for paid functions).
(2) Structural precautionary measures. To protect minors and to fulfill the precautionary obligations under the Youth Protection Act (JuSchG) and the Interstate Treaty on the Protection of Minors in the Media (JMStV), we maintain the following structural measures:
- a reporting and complaint system that is easy to find for all users (Section 6);
- moderation options for the host as well as provider-side removal and blocking powers (Sections 5, 7);
- the express prohibition of content harmful to minors, pornographic content, and other content impairing development (Section 3 — meaning Section 4), together with an assured prompt removal;
(3) Unchecked anonymous upload. Anonymous guests can post photos, videos, and comments without a prior age or identity check. We address the associated risk through the content prohibition (Section 4), the active confirmation of the Guidelines before the first upload (Section 1 para. 4), ongoing moderation/filtering (Section 8), and the assured removal of content harmful to minors as well as the blocking of the offending users within the period specified in Section 6. The specific scope of the JuSchG/JMStV obligations (in particular any thresholds dependent on user numbers, cf. § 24a JuSchG) must be aligned with the actual user base by a lawyer.
4. Prohibited Content and Conduct
(1) Content and conduct that violate applicable law or public morals or infringe the rights of third parties are prohibited. In detail, the following content in particular is prohibited (cf. § 9 para. 1 T&C):
a) Unlawful and criminal content, in particular child and youth pornographic content (§ 184b StGB [German Criminal Code]).
- Example: depictions of sexual acts by, on, or in front of minors — in any form. Such content will be removed without prior notice and reported to the competent authorities to the extent required by law.
b) Content harmful to minors and impairing development within the meaning of youth protection law (JuSchG, JMStV).
- Example: drastic depictions of violence or sexuality unsuitable for minors.
c) Pornographic content and other sexually explicit depictions.
- Example: explicit nude images without a legitimate connection to the party.
d) Content glorifying violence, cruel content, or content with a brutalizing effect.
- Example: glorification or trivialization of acts of violence, depiction of severe abuse.
e) Content inciting hatred, extremist content, and content hostile to the constitution (in particular §§ 86, 86a, 130 StGB).
- Example: use of symbols of unconstitutional organizations, incitement to hatred against groups of the population, denial or trivialization of the Holocaust.
f) Discriminatory, insulting, or degrading content directed at persons or groups.
- Example: racist, antisemitic, sexist, or sexual-identity-directed insults in a photo comment.
g) Infringements of copyright, ancillary copyright, trademark, or name rights.
- Example: uploading third-party, protected photos or works without the permission of the rights holder.
h) Infringements of personality rights and the right to one’s own image (§ 22 KUG [German Art Copyright Act], Art. 6, 7 GDPR).
- Example: publishing recognizable images of persons without their consent (see Section 5); covert or compromising recordings.
i) Malware and technical manipulation.
- Example: introducing malicious code or measures that impair the functionality of the App or the connected third-party services (Spotify, Apple Music, cloud storage).
(2) Also prohibited are:
- Harassment, bullying, and threats against other participants, in particular via photo comments;
- Impersonation, in particular choosing an alias/display name that purports to be another person, a brand, or an institution;
- Spam, advertising unrelated to the party, and commercial mass communication;
- the unwanted disclosure of the location, home address, or whereabouts of third parties as well as the misuse of the radius-based “Parties Nearby” function, for example to locate or harass strangers or minors;
- circumventing or undermining moderation, reporting, or security functions (e.g., re-posting banned songs by workarounds, circumventing blocks or the reporting/blocking function).
(3) This enumeration is not exhaustive. What is always decisive is whether content or conduct violates applicable law, public morals, or the legitimate interests of third parties.
5. Image Rights, Consent of Depicted Persons, and Protection of Minors
(1) Rights guarantee of the uploader. By posting a photo or video, you assure that you hold all necessary rights and that the content does not infringe the rights of third parties (§ 8 para. 1 T&C).
(2) Consent of recognizably depicted persons (§ 22 KUG / GDPR). You may post recordings in which persons are recognizably depicted into the party gallery only if the depicted persons consent to the storage and sharing within the respective party gallery, insofar as this is required (§ 22 KUG, Art. 6 para. 1, Art. 7 GDPR).
- Example: before you upload a group photo, make sure that the depicted guests consent to it becoming visible in the party gallery to the other participants.
(3) Public parties and joining of strangers — heightened requirements. In the case of public parties and parties that non-personally-connected guests can join via the “Parties Nearby” function, the group of participants is precisely not personally connected. The so-called household exception (Art. 2 para. 2 lit. c GDPR; cf. CJEU, “Ryneš”) regularly does not apply in these cases. The requirements for the consent of the depicted persons (§ 22 KUG) tighten accordingly, and a data protection responsibility of the host’s own is all the more readily to be assumed (para. 4; § 8 para. 3 T&C). Therefore, in these cases, take particular care to ensure that the necessary consents of all recognizably depicted persons have been obtained.
(4) Minors. In the case of recognizably depicted minors, the consent of all persons holding custody is required; in the case of joint custody — since the dissemination of photos is regularly not a matter of everyday life — the consent of both parents must be obtained. From the point of the minor’s capacity for discernment (as a rule from the age of 14), the consent of the minor themselves is additionally required (so-called dual competence; cf. § 8 para. 2, § 15 T&C).
(5) Responsibility of the host. If content is made accessible beyond the purely private, personally connected circle — in particular in the case of public or openly joinable parties — obtaining the necessary consents is the task of the host as organizer; the host may in this respect bear a data protection responsibility of their own (§ 8 para. 2, 3 T&C).
(6) Screenshot notice (no technical copy protection). If a screenshot is taken of content in the gallery, a technical notice may be displayed (“Screenshot Guard”); the host can deactivate this function (opt-out). This notice is merely information and not a technical protection: it neither prevents the taking of screenshots nor any further dissemination (e.g., by photographing with a second device) and does not effectively protect image rights. Responsibility for posting content only with the necessary consents remains entirely with the uploader; the taking or further dissemination of screenshots may nonetheless infringe the rights of third parties. The screenshot notice constitutes a separate processing of data; its purpose and legal basis (Art. 6 para. 1 lit. f GDPR) are described in the Privacy Policy (cf. § 2 lit. b, § 17 T&C).
(7) Withdrawal of consent. A depicted person may withdraw their consent with effect for the future. If you become aware of a withdrawal, the affected content must be removed without delay; the host and the photo owner can delete the content themselves at any time (Section 6). Independently thereof, removal can be requested via the reporting procedure (Section 7).
6. Rights and Obligations of the Host as Moderator
(1) The host moderates the party they have created and has the following functions for this purpose:
a) Deleting photos and comments. The host and the respective photo owner can delete individual photos at any time. Individual comments can also be reported and can be removed by the host or the provider.
b) Banning songs. The host can ban individual songs; banned tracks are added to the list of blocked tracks (bannedTrackIds) and cannot — including via search — be added again. Alternatively, the host can move a song to the end of the queue.
c) Controlling joining. Joining may require approval by the host. The host can remove and exclude guests from the party.
(2) Proportionality and objectivity. The host exercises their moderation powers appropriately and proportionately and takes into account the legitimate interests of the affected participants. The moderation powers serve to enforce these Guidelines and to preserve the party character; they may not be used abusively, in a discriminatory manner, or to infringe the rights of third parties.
(3) The host’s own responsibility. The host’s moderation powers leave unaffected their own legal responsibility for their event and the content posted there (cf. §§ 7, 8 T&C). The host’s moderation options do not replace the reporting and remediation procedure vis-à-vis the provider described in Section 7.
(4) Relationship to the provider’s powers. Independently of the host moderation, the provider remains entitled and, to the extent required by law, obliged to remove or block unlawful content or content violating these Guidelines and to block the offending user (Sections 7, 8).
7. Reporting and Remediation Procedure; Blocking and Removing Content and Users
(1) In-app reporting and blocking function. The App provides low-threshold functions on every photo, every video, and every comment as well as for every participant (alias):
- “Report content” on every individual photo, video, and comment;
- “Report user” and “Block user” for every participant alias — available to every user (including guests), not only to the host;
- a user-side hiding/blocking of the content of a particular alias. Since comments are attached to the photo and not to a profile, blocking technically ties in with the respective party alias.
In addition to the in-app function, reports can be made by email at any time:
Reporting contact: info@partyspot.app Additional contact channel: Contact form in the PartySpot app (Settings → Help & Support)
(2) Content of a report. Please state in the report as precisely as possible: (i) a justification why you consider the content to be unlawful or impermissible, (ii) the exact designation or location of the content (e.g., affected party, photo/video/comment, content ID), (iii) your contact details for a response (if possible), and (iv) a declaration that your information is, to the best of your knowledge, complete and correct. This procedure complies with the requirements for a reporting and remediation procedure pursuant to Art. 16 of Regulation (EU) 2022/2065 (Digital Services Act, DSA).
(3) Processing and response time. We confirm receipt of your report (for in-app reports by an automatic acknowledgment of receipt), examine it promptly, carefully, and non-arbitrarily, and inform you of the decision made. In the case of justified reports of abusive or unlawful content, we act without delay: we remove the affected content AND block the offending user (for anonymous guests via the binding to device, session, or token) within 24 hours of becoming aware. This commitment is underpinned by an actually operated intake and triage process (cf. Section 8). The blocking of the offending user can be carried out by the provider itself; it is not limited to host moderation.
(4) Blocking and removing users. To protect against unwanted content and interactions, the following options exist:
- every user can report and block content and other users in the App (paragraph 1);
- the host can remove and exclude individual guests from their party and make joining dependent on approval (Section 6);
- the provider can, upon a justified report, remove content and block the access of an offending user — including an anonymous one (Section 8).
(5) Abusive reports. In the case of repeatedly manifestly unfounded or abusive reports, we may appropriately restrict the processing of further reports by the user concerned after prior warning and only for manifestly abusive reporting conduct (cf. Art. 23 DSA). The obligation to substantively examine justified reports — in particular those concerning unlawful content — remains unaffected by this pursuant to Art. 16 DSA.
8. Measures, Statement of Reasons, and Consequences of Violations
(1) Possible measures. If we become aware of unlawful content or conduct, or content or conduct violating these Guidelines, we may, depending on the severity and frequency, in particular:
- remove the affected content or block access to it,
- change or block an unlawful or manifestly abusive alias/display name (§ 3 para. 4 T&C),
- block the user’s access temporarily or permanently (also for anonymous guests via device/session/token binding),
- terminate the user account (§§ 9, 11, 16 T&C).
(2) Proportionality and prior request. Before a block or termination, we will — except in cases of imminent danger or manifestly serious legal violations — first request you to remedy the matter within a reasonable period. We take into account the legitimate interests of the affected users and select the measure proportionately (§ 3 para. 4, § 9 para. 5 T&C).
(3) Obligation to state reasons (Statement of Reasons, Art. 17 DSA). If we remove or block content posted by you, we will inform you of the essential reasons. This obligation to state reasons exists as a matter of principle and applies to all hosting services (Art. 17 DSA). So that the statement of reasons does not fail due to a lack of a contact channel, we also provide anonymous users with a communication channel (in particular an in-app notice on the reported or removed content, which is assigned via the party and content ID).
(4) Appeal / internal complaint management. You can object to the decision informally — by email at info@partyspot.app or via the appeal channel provided in the App (which can also be used anonymously). We examine your objection and inform you of the result (§ 9 para. 4 T&C). Insofar as the service is to be classified as an online platform, the internal complaint management is governed by Art. 20 DSA.
(5) Paid functions / unjustified measures. If a block or termination of paid functions (e.g., party tier, storage add-on, party recap) occurs for good cause attributable to you, § 16 T&C applies. In the case of an unjustified measure, your claims for reimbursement and damages remain unaffected (§ 9 para. 6, § 16 para. 2 T&C).
(6) Statutory obligations. The shifting of substantive responsibility to the respective user leaves unaffected our own statutory obligations as a service provider and as a data protection controller (§ 9 para. 7 T&C). Our responsibility and the applicable liability privileges are governed by §§ 7 et seq. DDG in conjunction with Art. 4 to 8 DSA; the reporting and statement-of-reasons obligations (Art. 16, 17 DSA) remain unaffected by this.
9. Notice on the UGC Requirements of Apple and Google
(1) The App contains user-generated content (“UGC”) and is in this respect subject to the requirements of the app store operators. In order to ensure the protective mechanisms required for approval and continued presence in the Apple App Store (in particular App Store Review Guideline 1.2) and in the Google Play Store (UGC Policy), we provide the following functions:
a) Active consent to these Guidelines before the first posting of content (Section 1 para. 4) — also for anonymous guests;
b) Filtering and ongoing moderation of objectionable content: In addition to the content prohibition (Section 4) and the host’s moderation functions (Section 6), we employ host moderation functions (deletion of individual content, optional join approval), a low-threshold veto/hide function for guests, and the prompt removal of reported content by the provider. The mere content prohibition does not replace this moderation component;
c) In-app reporting and blocking mechanism on every piece of content and for every user (Section 7 para. 1) with a prompt response — removal of abusive content AND blocking of the offending user within 24 hours of becoming aware (Section 7 para. 3);
d) Ability to block or remove users — the host can remove and exclude guests and make joining dependent on approval; every user can report and block other users; the provider can block offending (including anonymous) users (Sections 6, 7);
e) published contact details of the provider for reports and inquiries (Section 1, Section 10).
(2) These protective mechanisms simultaneously serve to fulfill the statutory requirements (in particular the reporting and remediation procedure pursuant to Art. 16 DSA, the obligation to state reasons pursuant to Art. 17 DSA, and the youth protection precautionary obligations pursuant to JuSchG/JMStV). In addition, the terms of use and other conditions of the respective platform operators (Apple, Google) apply; these Guidelines do not create any rights or obligations of the platform operators.
10. Contact
PartySpot — SZuCO – Dr.-Ing. Piotr Szegvári (sole proprietor) Zum Weizenring 14 14469 Potsdam Germany
Reports, complaints, and appeals: info@partyspot.app as well as the in-app reporting/appeal function Additional, fast contact channel: Contact form in the PartySpot app (Settings → Help & Support) VAT ID No. pursuant to § 27a UStG: DE458930351 Competent supervisory authority / Digital Services Coordinator: not applicable
Communications in connection with these Guidelines may be made in text form, in particular by email to info@partyspot.app. The complete provider identification (§ 5 DDG, § 18 MStV [German Interstate Media Treaty]) follows from § 19 of the T&C; the mandatory data protection information is contained in the separate Privacy Policy (§ 17 T&C).
11. Version, Incorporation, and Amendments
(1) Version: 1.0 — As of: 18 June 2026. These Guidelines are an annex to the T&C (Version 1.0, as of: 18 June 2026) and are to be applied jointly with them; the paragraph cross-references to the T&C (in particular §§ 8, 9, 15, 16, 17, 18, 19) must be maintained in the event of changes to the T&C numbering.
(2) Incorporation and amendments: The incorporation as well as amendments to these Guidelines are governed by § 18 of the T&C. We provide information about amendments in the form provided for therein; the version applicable at any given time is made available in the App.
In the event of discrepancies, the German version shall be binding.
As of: 19 June 2026