YET LEGAL

Privacy Policy

Last updated: September 29, 2026

This Privacy Policy explains how YET collects and uses personal data through the YET mobile application, website and related services. The data controller is Tommaso Savorana, based in Italy and operating YET. Privacy requests: info@yet.social.

This notice covers visitors, account holders, event creators and people whose information is supplied by another user. It explains our processing; reading or acknowledging it is not blanket consent to optional processing. The Terms of Service explain your agreement with YET.

1. Data we collect

Account and authentication

Email address, unique username, display name, authentication provider, email-verification status, password credentials managed by Firebase Authentication, passkey credentials, account creation date, acceptance records for legal terms, confirmation of minimum age and security information. With Google or Apple sign-in, we receive the identifiers and profile information the provider makes available, such as your name and email (including an Apple relay address). YET does not receive your Google or Apple account password. Passkey records contain a public key and credential metadata, not your device's Face ID or Touch ID biometric data.

YET does not ask for a phone number or use SMS authentication. The Google Sign-In SDK's published privacy declaration also includes phone-number processing for sign-in functionality. This is a provider declaration; YET's sign-in flow does not request or store a phone-number field.

Profile information

Profile image, biography and links you choose to provide, in addition to your username and display name. New profiles are public by default. These details are displayed as profile information, subject to the available visibility controls. Information you put in free-text fields or images is also processed, so avoid unnecessary sensitive details. Email address, authentication data, notification tokens and account-security settings are private and are not displayed on public profiles.

Events and social activity

Events you create, edit, attend, save, share, comment on or collaborate on; event title, category, images and attached documents such as PDFs, location, dates, links, visibility and invitation lists; followers, following, blocks, collaboration responses, reports and notification interactions. This includes drafts, saved preferences and event-related stories. Social connections are YET's social graph, not an upload of your phone address book. Public events and public profile previews can be viewed without an account on the YET website and indexed by search engines, not just by people who receive a share link. Attendance at public events and social connections may be visible to other users. Private events are restricted according to their invitation and access settings. Public information can be copied, screenshotted or cached by others. Blocking an account does not make public web content inaccessible to someone viewing it without signing in.

Manual public-content review

New or edited public submissions covered by YET's prepublication review flow are held privately for human review before publication. This includes eligible public event and profile content, usernames, comments and images. The exact proposed text or prepared image, actor and target identifiers, revision, content digests, review status and decision reason support that review. A submission intended to become public is not treated as already public merely because it was submitted.

Authorized people handling moderation can access the held submission and necessary case information to assess rules, explain decisions and handle appeals. These records are linked to the submitting account; hashes and review identifiers are not a promise of anonymity. Review is limited to the necessary content and context, not sensitive-person profiling, advertising or model training.

A person reviews each candidate in this flow before approval, including event covers, profile avatars and gallery images submitted through the public event-media review path. Existing comments on an event changed from private to public receive human review. A pending state is not a rule violation, and a rejected edit normally preserves the last accepted version unless it is separately restricted. Errors or expiry do not publish pending material. Approval permits publication only through a successful retry of the exact approved submission, not automatic publication.

Google Cloud Natural Language and Vision safety checks are not active in this release. Content is not sent to those services for screening, including when an account has a saved AI preference. Google/Firebase infrastructure and optional Google sign-in remain separate uses described in section 4. No AI permission is required for the manual route, sign-in, reports, appeals or account deletion. This notice and any saved preference do not authorise future AI processing.

If an AI preference was previously recorded, its enabled or disabled value, notice version, update time and change history are held privately. A saved enabled value does not mean screening is active. You can ask us to withdraw a saved preference at info@yet.social. The separate retention periods are explained in section 6.

Private events, private chats, PDFs, unsubmitted drafts and bulk account histories are not sent for AI screening. These boundaries do not prevent limited human access needed for a particular report, security incident or applicable legal obligation. Review does not promise that every item across YET is checked in advance. A mistaken restriction can be challenged through human review.

Location

With permission, the app may use precise or approximate device location to calculate distance, find nearby events and set a home-area view. You may instead select a city manually. Event creators may publish an event location, which becomes visible according to the event's visibility. You can change iOS location permissions at any time.

Location or a manually selected area is sent to YET's servers when needed for location-based discovery. On the website, selecting nearby discovery requests browser permission and sends latitude and longitude in the request URL. Request URLs may appear in infrastructure logs. Location accuracy depends on your device and browser settings, and the coordinates received may be precise. Device location used for search is different from a location you deliberately publish in an event. You can decline permission and use other discovery views; the website's nearby view will then be unavailable.

Chats, comments and support

Messages, shared-event references, comments, conversation participants, read state and timestamps are processed to deliver inbox features. Current YET chats are protected by authenticated access controls and encryption in transit and at rest, but they are not end-to-end encrypted. Support emails, moderation reports and their attachments may be retained to answer requests and investigate safety issues.

Other users may supply information about you in messages, invitations, collaboration requests, photos or reports, even if you do not have an account. Contact us to raise a concern. People handling support and moderation may access relevant content when necessary to investigate a report, secure the service or meet a legal obligation. Do not send passwords, authentication codes or unnecessary identity documents to support.

Rights complaints and permissions

To assess copyright, privacy or likeness complaints and related reviews, we may process the reporter's contact details and authority to act, content links or identifiers, relevant licence or release evidence, the affected account's response, correspondence and decision history. When YET seeks permission for its own material or a campaign, records may include the rights holder, authorised uses, territories, duration and applicable conditions. These records document the particular claim or permission, not ownership of every item uploaded by that person. Submit only necessary evidence and redact unrelated personal or confidential information. We may request further proportionate information when needed.

These records are used to assess rights, address disputes and document authorised uses, and are not used to build advertising audiences. Access is limited to people and service providers who need it for those purposes, subject to the disclosures below. To obtain a response or explain a decision, we may share the minimum relevant allegations or evidence with the affected party or their authorised representative when lawful and necessary. We do not automatically publish a complaint or send the entire file to the other party. We consider safety, confidentiality and redaction; identity or contact details are disclosed only where necessary and lawful, including where a statutory notice or counter-notice procedure requires it. We cannot promise absolute confidentiality when law or due process requires disclosure.

The dispute-handling legal bases in section 2 and case-specific retention criteria in section 6 apply. Records needed to establish a licence or resolve a claim may be retained after an upload or account is deleted, only for a justified period and purpose. People depicted or mentioned in content can contact us without an account. A content licence, permission to use a person's image and consent to optional tracking are separate matters; none automatically supplies the others. See the reporting and review procedure and section 8 for data-protection rights.

Device, notification and technical data

Push tokens, notification preferences, app and operating-system version, device identifiers used for security, App Check attestations, server logs, IP-derived security information, request timestamps, request latency, errors and other operational diagnostics needed to detect abuse, maintain availability and troubleshoot errors. Authentication and infrastructure services also process identifiers, usage and diagnostic information needed to deliver and maintain their services, including IP-based approximate location for sign-in security. YET also records a limited set of interactions with its own service, such as sessions, event views, searches, shares, attendance changes and feature use. These records contain your account identifier, time, app version, platform and limited interaction properties; they are account-linked, not anonymous. These interaction records exclude message contents, search text, email addresses, precise location and advertising identifiers. Per-account usage counters and daily aggregate counters are also maintained. This first-party measurement is distinct from Google Analytics and from advertising tracking.

2. Why we process data

Legitimate interests do not override your rights, particularly those of children. You can object to processing on this basis, including product measurement, by contacting us. Account identifiers, authentication details and minimum-age confirmation are required to operate an account; without them we cannot provide authenticated features. Optional photos, biography, links and device location are not required to create an account. Choosing not to provide data needed for a particular feature may prevent that feature from working.

Account-linked product measurement currently runs without a separate in-app switch or consent prompt. Browser cookie settings do not stop it, and accepting the Terms or acknowledging this notice is not a separate analytics consent. To object, email info@yet.social and explain your particular situation. Where Article 21 GDPR applies, we must stop the processing unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms, or the processing is needed for legal claims. Section 8 explains the request process and available remedies.

Feed ordering uses factors such as followed accounts and their event activity, event recency, timing and distance from the selected location. You can change available feed modes and location filters. This is not a decision about legal rights or eligibility for credit, employment or similar services. Automated authentication, access and anti-abuse checks may prevent a request; contact us if you believe a restriction is mistaken.

The purpose of safety review does not by itself authorise every use of sensitive personal data or offence-related information. Additional legal conditions and safeguards apply where required. Accepting the Terms or submitting content is not blanket consent from everyone mentioned or depicted. You may object to legitimate-interest processing through the rights route below; consent, when relied on for a particular use, can be withdrawn without affecting earlier lawful processing.

3. Notifications

If enabled, YET may notify you about messages, follows, event invitations, collaboration requests, comments, attendance, event changes and reminders before, during or near the end of events. Default preferences are created with an account and can be changed in the app. iOS settings can disable all push notifications.

Push delivery uses Apple and Firebase services. Notification previews may reveal message or event information on a lock screen, depending on your device settings. Disabling push does not stop essential account emails or erase notification records already held by YET.

4. Who receives data

We disclose only what is reasonably necessary to:

• other users, based on profile, event and collaboration visibility;
• Google Firebase and Google Cloud, for authentication, database, media storage, hosting, server functions, app-integrity checks and messaging, receiving data necessary for those operations;
• Apple, for App Store distribution, Sign in with Apple, device security and push delivery, and Google when you choose Google sign-in;
• Resend and the email providers used to handle support, for account and support emails, including addresses, message contents, attachments and delivery status. Support messages may be forwarded to the operator's support mailbox;
• domain and DNS providers, for routing and domain operation, not for access to private chats;
• professional advisers or authorities, where necessary to establish rights, respond to lawful requests, prevent harm or comply with law;
• a successor organisation, in a merger, financing, reorganisation or transfer, subject to applicable confidentiality and notice requirements.

We do not sell personal data or share it for cross-context behavioural advertising, and do not disclose private chats to advertisers. The current site does not run Google Analytics 4 (GA4), Google Ads tags, Meta Pixel or TikTok Pixel. The possible future providers in section 12 do not currently receive advertising events from YET. Sign-in, store, map and linked ticketing providers also process information for their own purposes under their own notices. Organisers who collect information for their own event operations are responsible for that use; following or attending an event is not consent to receive their unrelated marketing.

Held review submissions, decision records and necessary case correspondence use the infrastructure and support providers described above, with access limited to people and providers who need it for the stated purposes. Natural Language and Vision are not active screening recipients in this release. We do not authorise moderation content for model training or advertising.

5. International transfers

YET is operated from Italy and uses server infrastructure in the United States. Google, Apple and email providers may also process data in other countries outside the European Economic Area (EEA), where data-protection laws may differ from those in your country.

Transfers subject to EEA data-protection law require an applicable adequacy decision or another lawful transfer mechanism, such as the European Commission's Standard Contractual Clauses with any necessary supplementary measures. You may contact info@yet.social for information about processing locations and the safeguards applicable to your data, including a copy, with confidential information redacted where necessary. See also Firebase's processing information and Resend's data processing terms.

6. Retention

• Account, content and social records: held while needed for your account and the features you use, until deletion or another applicable removal process. An event ending does not itself erase its content or attendance history. Signing out or uninstalling the app is not account deletion.
• Individual product interactions and records used to count daily active users: scheduled for deletion after a 90-day retention period, with removal processed daily.
• Daily product aggregates: scheduled for deletion after a 25-month retention period. Per-account usage summaries are separate, remain linked to your account and are included in account deletion.
• Deletion coordination: a temporary record of your account identifier helps prevent new analytics records during account deletion. It is scheduled for deletion after a 24-hour retention period, with removal processed daily.
• Legal acceptance, support, security and moderation records: retention depends on the time needed to resolve the request or incident, document decisions, prevent repeat abuse, satisfy a specific legal duty or establish or defend claims. Relevant factors include whether a case remains open and applicable legal limitation periods. A legal hold may require longer retention, limited to the records needed.
• Provider logs, backups and email delivery records: have separate retention schedules from YET's active database. Firebase states that authentication data is removed from live and backup systems within 180 days after its customer initiates deletion. That period concerns Firebase Authentication; other providers and record types have their own schedules.

Retention depends on the record's purpose, sensitivity, whether a request or dispute remains open, and applicable legal time limits. You can ask for the retention period or criterion applicable to a particular record at info@yet.social. Scheduled processing, backup retention and justified legal holds mean that deleting an account or event does not immediately erase every copy.

Manual-review retention

• Exact candidate text and image copies: a 30-day usable queue lifetime from reservation of the submission attempt, with earlier removal where applicable. Expired copies cannot approve publication. Scheduled, bounded cleanup and retry handling remove records and image objects; physical deletion can lag logical expiry during scheduling delays or failures. Published content has its separate ordinary lifecycle.
• Minimal decision receipts: decision/content identifiers, necessary actor linkage, rule version, status, revision, concise reason and dates, without full candidate text or images. Routine expiry is the later of 180 days and six calendar months from the decision, with month-end adjustment. This is not six months of raw-image retention.
• Later notification and timely appeals: the owner records the actual notice date and, where necessary, preserves only minimal decision/context information through the six-calendar-month complaint period from notification and a timely open case. This is a manual support procedure, not an automatic notification-based extension. Necessary case metadata is then removed within 30 days after closure unless a specific justified duty or claim requires more.
• Voluntary lawful appeal copies: accepted only where needed, with a separate limit of 30 days from receipt unless a specific lawful preservation duty applies. No raw copy is required to lodge an appeal; do not resend unlawful intimate or child material.
• Previously saved AI preferences: where such records exist, the current private preference remains while needed to retain and honour the choice or its withdrawal; historical choice logs have a separate 180-day lifetime and scheduled cleanup. These records do not activate AI screening and are not appeal evidence.
• Technical safeguards: a persistent opaque review identifier and revision high-water mark prevent stale approval reuse after raw deletion. Image-deletion work records contain necessary identifiers and retry information, not image bytes, and can remain while cleanup failures are resolved. Security audit records are separate from raw queue copies and follow their justified security/dispute purpose.

The six-month appeal offer does not depend on keeping every submission. We can use the receipt, reviewer reason, your explanation and a lawful copy you choose to provide. A specific preservation duty or necessary legal claim may justify limited evidence for longer, with restricted access and a recorded reason; it is not a general extension for all candidates. These limits are not promised review times or provider-metadata retention periods.

7. Account deletion

You can request account deletion in the app or by contacting us. The deletion process covers your authentication account, active profile, private account record, device tokens, passkeys, user-linked product analytics, relationship records, profile media, created events and their media, and authored comments. It also deletes YET conversations in which you participate, including their messages and other participants' access to those conversations. You can request a copy of your data before deletion. Copies retained independently by recipients, screenshots, external search caches and the records described in section 6 are not all removed by account deletion. Deletion can require recent authentication; if it fails, you lose access to the app, or you need access to or a copy of your data, contact info@yet.social.

For manual public-content review, deletion also covers linked raw candidate copies and decision receipts through the account-deletion process, subject to justified case-specific retention described above. Outstanding approvals cannot authorise recreation of a deleted account or target. Independent technical revision fences, limited security records and lawful support-case evidence are not the same as active candidate content. Ask us about a particular retained record or a failed deletion.

8. Your rights

Email info@yet.social with your request and enough information to identify the relevant account or content. You do not need an active account. Under the GDPR, subject to its conditions, you may request access and a copy, correction, erasure, restriction and portability, and object to processing based on legitimate interests. Portability applies to data you provided that is processed by automated means on the basis of consent or contract. You may withdraw consent at any time without affecting earlier lawful processing. Objection to direct marketing does not require a particular reason.

For GDPR requests, the response deadline is normally one month from receipt. If an extension of up to two additional months is necessary because of complexity or number of requests, we must explain this within the first month. Requests are normally free; the law permits limited exceptions for manifestly unfounded or excessive requests. We may ask for proportionate information to verify identity or an authorised agent's authority. If we cannot act, we must explain the reason and available remedies, unless disclosure is prohibited by law. Contacting us is not a prerequisite to complaining to a regulator or seeking a judicial remedy.

You may complain to the Italian Data Protection Authority (Garante) or a competent supervisory authority, including in the EEA country where you live or work. Depending on your location and applicable law, additional rights may include access, correction, deletion, a portable copy, information about disclosures, opting out of sale, targeted advertising or certain profiling, and appealing a refusal. Send a privacy appeal to the same email with the original request and why you disagree. Applicable local deadlines and complaint rights remain in force. You will not be penalised merely for exercising a privacy right. The scope of these rights and the response deadlines depend on the law applicable to your request.

Advertising disclosures can constitute a sale, sharing for cross-context behavioural advertising or targeted advertising under applicable US state laws, even without a payment. YET does not currently carry out these activities. Where applicable US state law requires, any future implementation must honour opt-out preference signals such as Global Privacy Control (GPC), provide the required sale/sharing and targeted-advertising choices, and explain their browser, device and recognised-account scope before activation. This is not a claim that an automated GPC handler is already installed. GPC is not consent to other processing, and an absent signal is not an opt-in. You can also contact us to exercise an applicable right without creating an account.

9. Security

YET uses authenticated access controls, separate private account records, Firestore and Storage security rules, TLS network encryption, encryption at rest provided by infrastructure services, App Attest/App Check for supported requests, limited server credentials and monitoring. No system is completely secure. Use a unique password, enable available account-security features and report suspected compromise promptly.

10. Children

YET is not intended for children under 14. We ask account holders to confirm that they meet the minimum-age requirement. The current signup flow uses this self-declaration; it does not collect a date of birth or country of residence or verify parental authorisation. Higher local minimum ages and any legally required parental authorisation also apply, as explained in the Terms. An age declaration does not replace any age-assurance, child-protection or consent obligations that the law places on YET. If you believe an ineligible child has an account, contact us with the account details so we can investigate and, where appropriate, remove the account and data, subject to safeguarding and legal retention duties. Do not send us unlawful images as evidence. Young users should avoid publishing their home address, school, routine or sensitive information.

11. Website cookies and analytics

The current public website does not use advertising or marketing cookies. Strictly necessary storage or request data may be used for security and delivery. See the Cookie Policy. If non-essential analytics or advertising technologies are introduced, YET will update its notices and obtain consent where required before activating them. Existing campaign parameters in some incoming links can already be passed to the App Store without cookies; the Cookie Policy explains this separately from in-app analytics.

12. Future advertising and AI-enabled features

Optional analytics and advertising: currently inactive

No advertising pixels, server-side advertising events, customer-list uploads or native advertising SDKs are active. YET has not launched an advertising campaign or a customer-matching programme. GA4 is also not active. The following are possible future tools, not a list of current recipients or permission to activate them. Existing first-party app measurement and campaign-link forwarding are described separately above.

Measurement assesses which advertising led to an action. Targeting selects an audience; retargeting or remarketing reaches previous visitors on another service. Providers may be able to associate permitted events with information from their own services or other sites and devices. Cross-device linking, Google Signals, Google Ads Customer Match, enhanced conversions, Meta or TikTok advanced matching and customer-list or lookalike audiences would each require a separate assessment and clear disclosure before use. None is authorised by signing up, attending an event or providing an email for account security. Hashing an email address does not make it anonymous. No account emails, attendee lists or follower lists are currently uploaded for these purposes. Server-side forwarding does not bypass consent, an opt-out or platform tracking rules.

Data excluded from analytics and advertising

YET will not send personally identifiable information to Google Analytics, including names, usernames, email addresses, phone numbers, authentication codes or identifying values in URLs, page titles, event properties or campaign parameters. User-provided data collection and automatic form capture must remain disabled. Only approved, sanitised measurement fields may be used; search text, account identifiers and user-written content are excluded from this optional third-party measurement.

Private messages, private events, invitation lists, support or moderation records, and precise device location will not be used for advertising targeting or sent to advertising providers. Public visibility is not permission for advertising profiling. We will not infer sensitive traits, such as health, religion, political views, sexual orientation or financial vulnerability, from event attendance, searches, social connections or content for advertising. Content or page references that reveal such information must also be excluded from advertising measurement and audiences. Giving consent cannot authorise a use prohibited by law or provider rules.

Consent, withdrawal and young people

Before any optional tools above are enabled, we will provide separate opt-ins for optional analytics, advertising measurement and personalised advertising, with meaningful provider choices. Accepting the Terms is not advertising consent. These purposes will use consent under Article 6(1)(a) GDPR where it applies, alongside prior permission for non-essential device storage or access under applicable cookie laws. No preselected choice or continued browsing will supply consent. Refusal will not block core public content. Controls will let you withdraw consent as easily as giving it, stop future affected browser and server transmissions, and request deletion where applicable. Withdrawal does not undo earlier lawful processing; deletion and legally necessary retention are separate matters.

We will keep a proportionate consent record of the purposes and providers selected or refused, the notice version, timestamp, method and later withdrawal, separate from legal-terms acceptance records. Its retention period, and the actual cookies, lifetimes, event retention, audience membership periods, receiving legal entities, roles and international-transfer safeguards, must be specified before activation. Providers are not automatically processors for every purpose; the relevant service and contract determine their role. The Cookie Policy explains the required browser controls. Those optional controls are not currently installed because the tools are inactive.

We will not use data of people known to be under 18 for personalised advertising, retargeting, customer-list matching or similar-audience creation, and will exclude them from these advertising measurement tools. Where age is uncertain, these advertising uses will remain off until a lawful and proportionate eligibility process can support activation. A store rating is not age verification. Parental permission or a general consent checkbox cannot override a legal or provider prohibition. Any future native-app tracking would also require Apple's App Tracking Transparency permission where applicable; a website choice does not replace that permission, and that permission does not replace legally valid privacy consent.

AI and external assistants

If YET introduces AI-enabled features, including connections to external assistants through the Model Context Protocol (MCP), we will explain their purposes, data involved, recipients, retention and available controls before processing begins. Any such processing must have a valid legal basis and meet applicable consent and transfer requirements. Any later Google content screening requires separate activation safeguards, current information and explicit permission before sharing; no existing preference is authorisation under this notice to start that processing. Optional connections to external tools likewise require relevant user authorisation and do not remove YET's own data-protection responsibilities.

This policy does not grant blanket consent to future advertising, disclosure of private chats, unrestricted access to account data by external tools, or training general-purpose AI models on your content. Any proposed use for model training would require separate, specific information and a valid legal basis, including consent where required. Any such feature would be offered separately with its own information and controls.

13. Changes and contact

We may update this policy as YET, providers or law change. Material changes will be communicated where required, before new processing starts, and the revision date will be updated. A policy update does not by itself supply consent or authorise an incompatible new use of your data. Questions and rights requests may be sent to info@yet.social.

Controller: Tommaso Savorana, operating YET, Italy.