Summary
Quiet Social processes account, profile, availability, connection, meeting, safety, and location-related data to support nearby discovery and real-world coordination.
Privacy Policy
Meeting people should not require giving away more than you mean to.
This page reflects what the Quiet Social app and backend structure indicate about accounts, availability, location, meetings, and safety data.
Data processed
Based on the app and backend structure, Quiet Social may process email, profile basics, date of birth, username, profile and contact settings, invitation codes, location, availability windows, connection requests, meeting requests, meetings, blocks, and reports.
Authentication
The app uses a magic-link and verification-code flow, with the backend supporting passwordless access and future OAuth-compatible paths.
Location and nearby matching
Location is used to support nearby discovery and to make meeting suggestions more realistic when people are actually close enough.
Availability and meetings
Availability windows, meeting requests, and meetings are processed so users can share when they are open and coordinate plans with less ambiguity.
Safety features
The backend structure explicitly includes blocks and reports, and the app models privacy-aware visibility and contact-sharing controls.
Infrastructure
The current backend README indicates a Spring Boot stack with MySQL, Flyway, and Gmail-based email delivery for local magic-link development.
Contact
For privacy-related questions, contact [email protected].
Last updated: May 2026