6SIX

Relationship guides 08 · 10 min

Understand your data and your choices

Check what is stored, what is excluded and what you can control before using a relationship service.

Who this guide is for: People who want to know the data boundary before importing.

1. Separate server and device storage

A signed-in account stores import history, counts, preferences and support requests; pseudonymous relationship keys, evidence and timestamps; and introduction and consent states. Optional features also store saved searches, team sharing and integration records. Display names, importance marks, hidden people, corrections and goals stay in this browser's encrypted storage. If encryption is unavailable, names are not persisted. These records do not automatically move to another device.

2. Understand the limits of pseudonyms

Original files, raw phone numbers, raw email addresses and conversation bodies are not stored on the server. Relationship keys remain linked to an account and are pseudonymous, not fully anonymous. Sensitive traits are not used to judge relationship importance.

3. Export, correct or delete

JSON combines device records with account records retrieved successfully. It can contain device display names. CSV and VCF focus on people and omit support requests and detailed activity. If the account request fails, check the device-only export warning. Delete my data clears this device and requests deletion of signed-in account data. Device data may be cleared even if the server request fails; read the result. Downloaded copies, other devices and the sign-in provider's account need separate action.

4. Keep advertising separate

Public guides may display ads. Names, contact details, relationship graphs, introduction requests and support inquiries are not supplied for ad personalization. Ads are labeled separately from service actions. On shared devices, sign out and manage downloaded copies yourself.

Terms explained
Metadata
details such as source, time and count, rather than a message body.
Pseudonymous key
a value used instead of a name; it remains linked to an account.
Encryption
storing data in a form that needs a key to read; it does not prevent every risk on the same device.
JSON
an export format that preserves named fields and structure.
CSV / TSV
tables whose columns are separated by commas or tabs.
vCard / VCF
a contact-card file format.
PWA
a web app that supported browsers can add to the home screen.
Relative score
a comparison within current records, not a person's worth or success probability.