Privacy notice

Controllers and contact

Paul Batthyany and Leon Holluschek, Helfentalweg 2, 6020 Innsbruck, Austria, are joint controllers under Article 26 GDPR. Contact: support@zusio.app. Paul coordinates privacy and support requests; Leon coordinates technical security and moderation. They deputise for each other, and rights may be exercised against either controller. No data protection officer is currently appointed.

Sign-in and legal records

We process email address, account identifier, sign-in provider, authentication data and session information. Email sign-in uses a one-time code. If selected, Apple or Google may provide an identifier, email address and name. We do not receive the Apple or Google password.

The app stores the session locally. To record legal acceptance we store account ID, document type, version, language, checksum, server time and the acceptance or acknowledgement. Interface language and the confirmed minimum-age threshold are stored separately. Acknowledging this notice is not blanket consent to processing.

Profile and social connections

Name, username, optional city, interests, biography and profile image are used to identify people and attribute meetups. These fields are generally visible to other signed-in users and are not limited to friends. Date of birth, gender field, friend code and settings are private. Date of birth is used to enforce the minimum age of 13.

Friend requests, friendships, groups, invitations and blocks store the participants, status and timestamps. Data may also come from other users who invite, message or report you. Address-book access and contact matching are not implemented.

Meetups and calendars

Public meetups are visible to signed-in users. Other visibility options include selected people, friends and friends of friends. Title, description, location hint, time and participants follow the selected visibility. The exact address is stored separately for the host and confirmed participants.

Calendar entries contain title, time, location, notes, recurrence, exceptions and reminder settings. They are private by default. If shared with friends, authorised friends with Zusio+ can view the shared content. Zusio does not currently import the device calendar. Ending a subscription does not automatically delete saved calendar entries.

Chats and media

Event chats store messages, sender, time, replies, reactions, read status and selected photos, videos and voice messages. Content is delivered to authorised participants and is not end-to-end encrypted. Authorised operators may access it where necessary for operation, security or report handling.

Chat media is held in private storage and made available through short-lived links. A recipient copy or previously issued link may persist beyond hiding content. Uploaded files may contain technical metadata; complete metadata removal is not guaranteed.

Location and place search

You may enter an address or, after a purpose-specific explanation, share your current location once in a chat. Coordinates and a resolved address may then be stored as part of the message. Zusio does not continuously track location in the background. Revoking device permission does not delete a location already shared.

When place search is enabled, search text, language and technically necessary connection data are sent directly to photon.komoot.io. Operating-system geocoding may also involve Apple or Google. Opening a map deliberately passes the chosen place or coordinates to Google Maps.

Notifications

Push notifications are enabled only after an explicit choice and device permission. Supabase stores an Expo push token, random installation ID, platform and activity information. Expo and the operating-system push service process token and payload data for delivery. Notifications may be visible on the lock screen.

Notification categories can be changed in the app and device settings. Local calendar reminders are scheduled on the device and removed when signing out. Push permission is not marketing consent.

Zusio+ and payments

Apple processes in-app purchases and payments. RevenueCat receives the Zusio account ID as its app-user ID and product, transaction and subscription information for purchase attribution and restoration. Zusio stores entitlement status, expiry and synchronisation evidence. Deleting a Zusio account does not cancel an Apple subscription; subscription management remains available through Apple.

Reports, safety and support

Reports store reporter, target, category, details, timestamps, status and a snapshot required for review. Measures and complaints store the decision, reasons, duration and review state. A report does not automatically prove a violation. Support and privacy requests store the message, handling state and response.

External DSA notices store the information supplied, a reference, status, decision reasons and any complaint. Contact details may be omitted only for the statutory exception implemented in the reporting form. Access codes are stored as hashes. Email delivery is queued through the configured mail provider.

Providers and international transfers

Supabase provides authentication, database, storage, Realtime and Edge Functions; the project database is configured in eu-west-1 (Ireland). RevenueCat supports subscriptions. Apple and Google support selected sign-in, Apple supports purchases and APNs, Expo supports push delivery, Photon supports place search, and Sites/Cloudflare serves the website. Cloudflare Email Routing forwards support@zusio.app through an active catch-all rule to the Gmail mailbox used by the operators. Resend is intended for transactional DSA and deletion messages.

Where data is processed outside the EEA, we use an applicable adequacy decision or contractual safeguards and assess additional measures as required. The current provider list and contract evidence are maintained in the service-provider register. Providers acting for their own purposes remain independently responsible for those purposes.

Legal bases

Processing necessary to create an account, organise meetups, provide chats, calendars and paid functions is based on performance of the contract or steps requested before contracting under Article 6(1)(b) GDPR. Security, abuse prevention, service improvement, support and legal defence rely on legitimate interests under Article 6(1)(f), after balancing the interests involved. Accounting and legally required moderation rely on Article 6(1)(c). Optional device permissions and any consent-based processing rely on Article 6(1)(a) and can be withdrawn for the future.

Special-category or criminal-offence data is not requested as a profile purpose. Users must avoid entering it unnecessarily. If such information appears in safety material, access and processing require a separate necessity and legal-basis assessment.

Retention

Incomplete registrations are removed after 48 hours. Event and chat archives are removed 12 months after the meetup ends. Unreferenced uploads are removed after 24 hours. Inactive accounts are removed after 24 months following notices around 30 and 7 days beforehand, unless an active subscription, open proceeding or legal hold applies.

Operational logs are retained for 30 days and security logs for 90 days; confirmed incident records may be retained up to three years after closure. Successful push jobs are retained for 7 days, permanently failed jobs and disabled tokens for 30 days. Moderation material is retained for six months after the final decision and, where required for an incident or proceeding, up to three years. Support content is retained for six months and minimised proof of privacy-request handling for three years. Contract evidence is retained for three years after the contract; tax records are retained for the legally required period, generally seven years. Backups roll for no more than 30 days and deletions are reapplied after restoration.

Your rights

Subject to the legal requirements, you may request access, a copy, rectification, erasure, restriction, portability and object to processing based on legitimate interests. Consent can be withdrawn for the future. Requests can be submitted in the signed-in app or to support@zusio.app. We may request proportionate verification and will not ask for passwords or one-time codes.

You may lodge a complaint with the Austrian Data Protection Authority, Barichgasse 40-42, 1030 Vienna, or another competent supervisory authority. Automated individual decision-making producing legal or similarly significant effects is not intended. Moderation prioritisation and filters are subject to human review.

Security and changes

We use access controls, row-level database policies, private storage, short-lived media links, restricted operator roles and deletion workflows. No system is completely secure. Report suspected vulnerabilities to support@zusio.app without sending unnecessary third-party data.

We update this notice when processing materially changes. The displayed version, date and checksum identify the applicable text. Material changes are communicated where legally required.