Collect less. Say why.

Effective August 2, 2026 · Public alpha

What we collect

We collect your email, age confirmation, chosen municipality, lifetime-access status, random invitation code and—if you join through a friend—the inviting account’s internal identifier. If you voluntarily enable approximate location, we also store a coarse area centre from a roughly four-kilometre-wide grid. We also collect profile answers, private discovery preferences, photos, conversations, messages, reports, outcome check-ins, support requests, and security records. Optional profile fields include height, drinking, smoking, cannabis, and self-described ethnicity. Ethnicity can include any of the broad categories that apply; Solid never guesses it from photos or text. We do not store raw GPS coordinates, a precise address, address book, sexual history or “body count,” attractiveness scores, body-type ratings, contacts, or biometric face templates.

Why we use it

We use this information to run accounts, apply both people’s discovery filters, rank compatible profiles, deliver messages, understand whether people talk or meet, investigate reports, prevent abuse, secure the service, and respond to support or legal requests. Ethnicity is used only when a member sets an ethnicity filter; it is not a ranking, popularity, engagement, or operator-analytics signal. Payment, popularity, predicted attractiveness, and time spent in the app are not matching signals.

Connection outcome check-ins

Connection check-ins are optional. Your saved answer is visible to you and is never shown to the other person. The ordinary operator dashboard receives only combined match-level counts and rates, not a list of individual answers. Check-ins help Solid measure conversations, planned dates, meetings, and relationships; they are not used to rank profiles or sell attention.

Messages and moderation

Plain version: we are not reading your conversations for fun, but they are visible to us. Messages are stored on Solid’s servers, not end-to-end encrypted. Authorized operators can open message content to prevent, investigate, or confirm abuse, and this is not limited to accounts someone has already reported. Every view requires the operator to record a written reason and is logged to the moderation audit trail, so message access is always accountable and reviewable. Our honest suggestion: use Solid to work out whether someone is a real match, then move the flirting and anything private to text or wherever you prefer. We would rather tell you that outright than let you assume a privacy you do not have.

Solid also records aggregate high-volume outreach signals so unusual messaging patterns can be spotted without selling or arbitrarily rationing normal messaging. When a member reports someone, Solid additionally saves the relevant profile and up to 100 recent messages as private report evidence. Operators do not read conversations for curiosity, advertising, profiling, or ranking. Message content is never used as a matching signal, never sold, and never used to build an advertising profile.

Notifications

Message emails say only that an unread message exists. They never include the sender or message text. Solid sends at most one within your chosen one-hour, four-hour, or daily interval. You can separately turn off message emails, completed photo-review emails, and support-reply emails from Account. Photo-review emails include only the result, never the photo or review note. Support-reply emails include no request or reply text. Photo-review and support-reply emails are each capped at one per hour when several events happen together. Sign-in codes are sent only when you request one. Solid does not send profile-view, popularity, streak, new-member, or re-engagement emails. Read timestamps and unread counts are stored so the private inbox works across your devices.

Traffic and sign-in records

If you choose traffic analytics, we record the page path, referrer domain, allowed campaign tags, whether an account signup was started, and a daily rotating pseudonymous visitor hash derived from IP address and browser information. Invitation campaign nicknames must not contain an email or full name. We do not store the referring page’s full URL. These traffic events are deleted after 90 days. You can decline analytics or change the choice from Account without losing service. Separately, short-lived pseudonymized IP and device hashes protect login and sessions.

Location and launch waitlist

Municipality-only location is the default. If you press “Use approximate location” and grant device permission, the standard Solid site rounds the device reading into a roughly four-kilometre-wide grid cell before sending it. The raw reading is not saved in browser storage, sent to Solid by the standard site, or stored on Solid’s servers. The server validates and re-rounds the coarse value, uses it only for distance filtering and nearby ranking, and excludes its coordinates from member-visible profiles and report snapshots. You can return to municipality-only distance at any time. Solid never requests background location, tracks movement, or shows a pin, direction, neighbourhood, exact distance, or location cell to another member. Other members see your municipality and, in discovery, at most a rounded distance band. Outside the launch area, you may separately consent to a launch email waitlist using your email, province or territory, and nearest city. Waitlist records are deleted after one year unless you join or ask us to remove them sooner.

Alpha lifetime access and invitations

Accounts created while alpha lifetime access is open receive a permanent access entitlement. Each active account receives a random invitation code. When a friend uses it during alpha, we store that the new account came through an invitation so their lifetime access remains auditable. The link does not contain the inviter’s name, email, profile, or user ID. Referral relationships are used for access administration and aggregate signup counts, not matching, ranking, advertising, or public profiles.

Who handles data

Solid uses service providers for hosting, encrypted transport, database and photo storage, backups, login email, and optional message-alert email. They receive only what is needed for those jobs. We do not sell personal information and do not run third-party advertising trackers on member screens.

Visibility

Anonymous visitors cannot browse real members. Email, birth date, and discovery preferences are private. A profile appears only when both people’s filters allow it; Solid does not reveal which private filter excluded someone. Ethnicity is hidden from a profile unless the member turns on “Show my ethnicity.” A hidden ethnicity answer can still affect mutual visibility when either person uses an ethnicity filter. Approved profile information appears only in compatible discovery and conversations. Uploaded photos remain private until review. Photo approval checks content; it does not prove identity.

Retention and real deletion

Normal message records are scheduled for deletion no later than 365 days after sending. Deleting your account immediately removes your public profile, preferences, managed photos, discovery records, support requests, and sessions; ends conversations; and replaces the account email with a non-identifying tombstone. Solid never keeps or displays a deleted profile as a ghost account.

After account deletion, the inaccessible conversation record may remain for up to 90 days so another member can make a late safety report. Evidence already attached to a report may be retained for up to two years from the report, unless a shorter or longer period is legally required. Encrypted backups age out within 30 days and are used only for disaster recovery, not to restore a deleted profile to the live service.

Your choices

You can edit or pause a profile, return to municipality-only distance, refresh an approximate area only by pressing its button, leave optional fields blank, change filters, hide or clear an ethnicity answer, control each optional notification category, block or report a member, revoke sessions, decline traffic analytics, send private alpha feedback, ask for access or correction through authenticated support, or delete the account in-app. Alpha feedback enters the same private operator support queue and is shown on the ordinary dashboard only as combined counts. Remove an active ethnicity filter before clearing your own ethnicity answer. Privacy and support questions can also be sent to support@meetsolid.app. Do not place precise addresses, financial information, passwords, or login codes in profiles or messages.

Changes

This version adds optional, device-coarsened location for more accurate distance filtering. Existing members must accept the current policy again at sign-in. Future material changes also require fresh acceptance. Retention and biometric verification rules will be updated before those practices change.