Cookies & similar technologies

1What this page covers

Companies often say “cookies” to mean cookies and similar tools: device IDs, local storage, tokens, and pixels. We describe all of those here so you can see what The Deaf Socials actually uses.

Questions: privacy@thedeafsocials.com.

2The mobile app — no HTTP cookies

The The Deaf Socials app does not use HTTP cookies. It does not set a cookie jar, and it does not use cookies to advertise or to follow you across other companies’ apps.

What we do use on the device:

• Access token. A short-lived sign-in token in the device’s secure storage (Keychain on iOS, Keystore on Android). Needed so the app can call our API. Deleted from the device when you log out or delete the account.
• Refresh token. A longer-lived token in the same secure storage, used only to get a new access token. We store only a hash of it on our servers, with expiry and revocation. Deleted from the device on logout. Logout-everywhere revokes every hashed refresh session for the account.
• Installation ID. A random UUID in secure storage. Sent with API calls so we can recognize the same install for security. Not cleared on logout. Stays until the app is removed. Not an advertising ID. Not sold.

These are strictly necessary to sign in, stay signed in, and protect accounts. We do not use them for ads. We do not use advertising, analytics, or crash-reporting software in the app today. We do not use Apple’s App Tracking Transparency tracking because we do not track you across other companies’ apps for ads.

3Our public web pages

Our legal pages and the password-reset page do not set tracking cookies and do not use advertising or analytics cookies. Sign-in for the app uses bearer tokens, not a website login cookie.

We may add strictly necessary cookies on web pages later (for example, to keep a reset form from being abused). If we do, we will update this page. We will not add advertising cookies without saying so here.

4Map tiles and other network requests from the device

When you view a map in the app, your device requests map images from OpenStreetMap. That request is made by your device, not by a cookie we set. OpenStreetMap may see your IP address and usual browser-like request details. Their rules apply: OpenStreetMap tile policy.

If you paste a Google Maps or Apple Maps share link, our servers may fetch that public link over HTTPS to read coordinates. We do not forward your cookies or sign-in headers. Google’s and Apple’s own rules apply to their sites.

If you open a Facebook, Instagram, or Eventbrite link from an event, your browser or those apps may set their own cookies. That is outside The Deaf Socials.

5What we do not use today

Today we do not use:

• Advertising cookies, pixels, or SDKs.
• Analytics SDKs (no Google Analytics, Firebase Analytics, Mixpanel, Amplitude, or similar in the app).
• Crash SDKs (no Crashlytics or Sentry in the app).
• Cross-app tracking for ads.
• HTTP cookies in the Flutter app.

6Your choices

You can log out (clears tokens on the device, not the installation ID). You can delete the app (clears secure storage on most devices). You can delete your account. You can turn off location in system settings (that is GPS, not a cookie). You cannot opt out of the installation ID or tokens if you want to stay signed in — they are required for the Service.

See the Privacy Policy for what we collect, AI & Data for automated processing, and the Terms of Use for the rules of use.

We may update this page. The “Last updated” date at the top will change. If you keep using The Deaf Socials after an update, you accept the new version. We may also tell you in the app or by email when a change is important. Your continued use is acceptance even if you do not read the new version.