Cookie Policy

1. What is a cookie?

A cookie is a small text file saved to your browser when you visit a website. It lets the site remember you — for example, keeping you signed in. Similar technologies include browser storage areas such as localStorage and sessionStorage; we explain those in this policy too.

2. Why do we use cookies?

Necessary storage keeps you signed in, remembers your theme and language and protects your session. When Google ads are enabled, additional storage may support ad serving, frequency control and measurement; required permissions are managed separately.

Session and preference storage is necessary for the service. Advertising storage is not part of this necessary category and is not used without consent where consent is required.

3. The full list of cookies we use

aurcam_auth

Purpose: marks whether your session is open; allows a redirect to happen before protected pages are rendered (prevents the page from flickering). Type: strictly necessary. Duration: for the session / until you sign out. Party: first party.

__Host-next / Next.js infrastructure cookies

Purpose: operation of the server-side rendering and routing infrastructure. Type: strictly necessary. Duration: session. Party: first party.

When Google ads are enabled, Google consent-management and advertising cookies may also be present. Review current providers and purposes in the consent message, and stored data in your browser’s site-data settings.

4. Local storage (localStorage) keys

We keep some preferences in your browser's local storage rather than in a cookie. This data is not sent to the server and stays on your device only:

aurcam_token

Your session token (JWT). It is deleted when you sign out.

aurcam_refresh

The session refresh token — it saves you from having to sign in again frequently.

aurcam_theme

Your light/dark theme preference. It is synchronised with your setting on the server.

aurcam.sound.muted

So that muting the sound on feed videos is remembered.

When you clear your browser data these keys are deleted as well; in that case you will need to sign in again.

5. Third-party cookies

When Google AdSense in-feed ads are enabled, third-party advertising and consent storage may be used. Embedded content may also make its own requests:

• Map (OpenFreeMap): loads the map tiles. It works without an account or a key; it does not leave a cookie that identifies you.
• Deezer previews: a media request is made while a music track preview is playing.
• GIPHY: image requests are made while you search for a GIF.

These services are subject to their own privacy policies. We do not pass your identity to them.

6. The position in the mobile app

Cookies in the web sense are not used in the iOS and Android apps. The session token and your preferences are held in the device's secure local storage (AsyncStorage). When you delete the app this data is deleted too.

Google feed and rewarded ads in the app are served by Google AdMob, and AdMob uses the device's advertising identifier (IDFA on iOS, AAID on Android) when requesting an ad. On iOS this happens only if you tap "Allow" in the system permission prompt; if you decline, IDFA access is not granted. Ad availability also depends on required advertising permissions and inventory. On Android ads are requested as non-personalised. Beyond serving these ads we do not track you across third-party apps and websites. For details see Privacy Policy 2.3.

7. How do you manage cookies?

You can delete or block cookies from your browser's settings. If you block the strictly necessary cookies, however, your session will not stay open and you will not be able to sign in.

Chrome

Settings → Privacy and security → Third-party cookies / Site data

Safari

Settings → Privacy → Manage cookies and website data

Firefox

Settings → Privacy & Security → Cookies and Site Data

Edge

Settings → Cookies and site permissions

You can manage your in-app preferences (theme, autoplay, data saver) from the Settings section; they are tied to your account and apply across all of your devices.