Cookies, tokens and storage

The website sets only these first-party cookies:

• stranding_rt: keeps you signed in by storing the session renewal token. HttpOnly, Secure and SameSite=Lax. Lasts until the browser is closed (the token expires after 1 day anyway), or 30 days if you choose “Remember me”.
• stranding_temp: marks a temporary guest session. HttpOnly, Secure, 24 hours.
• stranding_locale: remembers your chosen language. Until the browser is closed.
• beta_launch: records which mode the site is in during the beta phase (restricted access or open site). Readable by the page, until the browser is closed.
• stranding_beta_invite: keeps your personal beta invitation link while you sign in or create your account. HttpOnly, Secure, sent only to /api/beta-invites addresses; lasts 30 days or until you accept or decline the invitation.

No cookie contains your password. If you block technical cookies, the site cannot keep you signed in.

The access token stays only in the page memory for about 15 minutes; the renewal token is replaced at every renewal and you can have at most 10 active sessions. From your profile you can see and revoke connected devices.

Signing out deletes the access cookies and revokes the corresponding token; changing your password revokes all sessions.

The website stores some information in your browser (localStorage and sessionStorage). It stays on your device and is not sent to us, except the guest identifier when you submit a sighting.

• stranding_web_tour_seen_v1: remembers that you have seen the guided tour.
• stranding_web_report_intro_hidden_v1: remembers that you hid the sighting introduction.
• stranding_web_guest_device_id_v1: random device identifier for guest sightings.
• stranding_photo_watermark_preferences_v1: photo watermark text and preferences; it may contain the name, social handle or email you entered.
• community-seen-activity: community activity you have already seen, for each account used in that browser.
• stranding_web_guest_draft_handoff_v1 and stranding_beta_widget_hint (sessionStorage, deleted when the tab is closed): handover of a guest draft to an account and the beta widget hint.

So you do not lose your work, the sighting form saves the draft in the browser database (IndexedDB, “stranding_web_drafts”): location and its accuracy, original photos with their metadata (such as date and GPS coordinates), notes, guest contact email and co-author names.

The draft stays on your device until you submit or delete the sighting or clear the site data from your browser, and in any case it is deleted automatically if you have not saved it for 30 days. On a shared computer, delete it after use.

The app keeps access tokens and the device identifier in the system’s secure storage (Keychain on iOS, Keystore on Android). If you enable notifications, Google’s Firebase Cloud Messaging handles the device token. Maps go through our intermediate server and typefaces are bundled with the app, so OpenStreetMap and Google Fonts do not receive the device IP address. App versions installed before this update may still contact them directly until they are updated.

Images are not stored in cookies. Browsers and the content-delivery network (Cloudflare) may cache public images for up to 1 year to speed up the site. When we accept a removal request we delete the files and request cache invalidation, but we cannot control copies made by third parties.

On the website and in the app, maps go through our own intermediate server, so OpenStreetMap does not receive your IP address.

You can delete cookies, local storage and cache from your browser settings at any time. Signing out removes the access cookies but not local preferences or drafts. To learn how we use personal data, read the Privacy notice.