Privacy terms for trusted cultural exchange.

This notice explains what Saii collects, why it is used, and which account controls are available.

Current required consents

Version 2026-07-21

Version 2026-07-20

Sensitive data processing

Version 2026-07-20

Data we collect

Account identity, social-login references, verified phone status, school or work affiliation-verification metadata, profile details, interests, posts, comments, chat metadata, structured peer references, profile-view analytics, friendship-funnel milestone analytics, reports, blocks, device registrations, consent records, safety moderation/throttle metadata, identity-verification metadata, and subscription entitlement state.

School and work email verification

The full email address and one-time code are encrypted only while Brevo delivers the verification email, then redacted. We retain a masked address, keyed digest, domain, verification status, review history, and expiry so we can prevent duplicate claims and show an accurate organization email badge.

Profile-view analytics

Public profile opens are stored as one aggregate row per viewer and viewed profile, including view count and last-viewed time. These include profile views you made and profile views received.

Friendship-funnel analytics

Allowlisted milestones such as completed onboarding, useful profile discovery, reciprocal chat, event or meetup participation, and confirmed attendance are stored with coarse role, service-language, catalog-city, and affiliation-type snapshots. Names, contact details, message bodies, profile text, organization names, and raw event or conversation identifiers are not stored in analytics context. These records are removed when you request account deletion.

Verified peer references

After a trusted two-way chat or confirmed attendance together, a member may choose one to three predefined positive traits about another member. We retain the author, recipient, selected traits, and the verified chat, event, or meetup used as provenance. Public profiles show only combined trait counts and broad provenance; the recipient can privately see the author, hide or report a reference, and the author can update or withdraw it. Free-text references and public negative ratings are not collected.

Sensitive-data processing

Identity verification is vendor-SDK based. Rails stores verification metadata only, rejects direct document uploads, and keeps production KYC provider work behind the post-review webhook boundary.

Provider and billing posture

Premium access, calling, push delivery, and identity checks use provider boundaries so sensitive data and account controls stay separated.

Map tiles and location controls

City maps use CARTO-hosted tiles based on OpenStreetMap data. Tile requests may send CARTO your IP address, browser and request data, and the requested map area. If you tap Show my location, your browser or app uses the device coordinate to center the map. Saii does not receive or store that raw coordinate through this control, but the tile area requested from CARTO can reflect the area around you. If you tap Nearby in Discover Buddies, your browser or app matches the coordinate to a catalog city on your device, and Saii receives only that city code. Read CARTO's privacy notice. Read the OpenStreetMap Foundation privacy policy.

Your controls

Request account deletion

The account deletion page explains the web request path, the 30-day recovery window, and which data may be retained for security, fraud prevention, legal, or audit reasons.