Cookie policy

1. What this website uses

Cookies are small pieces of data the browser stores and sends to the relevant website. Screengaze uses technical cookies to maintain the access you request, secure sign-in and save your optional analytics choice. The controller is the operator identified in the legal notice.

PostHog and DataFast are not currently installed and no events are sent to these services. The website does not load analytics, advertising or cross-site tracking cookies. Preferences are saved in a first-party cookie; localStorage and sessionStorage are not used for preferences or tracking identifiers. Fonts are served by the website itself.

2. Authentication cookie

__Secure-better-auth.session_token · A first-party authentication cookie. It links the browser to your account session and enables access to purchases, licences and authorised Macs. By default it lasts for the browser session. If you select the keep-me-signed-in option when using Google sign-in, it becomes a persistent cookie lasting up to 90 days, renewable during use.

This cookie is HttpOnly, uses SameSite=Lax and is sent over a secure connection on HTTPS. It does not contain a cached copy of your profile or purchase data. Signing out invalidates the relevant access. If you clear it manually, you will need to sign in again to use private features.

__Secure-better-auth.dont_remember · A first-party session cookie that remembers your choice not to stay signed in after closing the browser. It is used when you leave the keep-me-signed-in option unchecked. It is HttpOnly, SameSite=Lax and Secure on HTTPS; it contains no profile data and is not used for tracking.

3. Google sign-in security cookie

__Secure-better-auth.state · A first-party security cookie. It checks that Google's response corresponds to the sign-in process started in your browser and protects that exchange against unrelated requests.

Its configured maximum lifetime is 5 minutes and it is removed when the authentication response is completed. It uses HttpOnly, SameSite=Lax and Secure on HTTPS. It is not used for analytics or advertising.

4. Preference cookie

screengaze_cookie_consent · A first-party cookie necessary to remember your choice and its date for 180 days. Its value follows the format v2.allow.timestamp or v2.deny.timestamp: the notice version, whether you allow or reject optional analytics, and when you saved the preference. It contains no email, account data or advertising identifier.

It is saved only when you accept, reject or save a selection. Without a valid choice, analytics is treated as off. You can reopen preferences from the footer or this page. If you clear the cookie, it expires or the notice version changes, you will be asked to choose again.

The previous screengaze_cookie_notice cookie with the value v1 only remembered dismissal of an informational notice. It is ignored when managing your current choice and is never treated as analytics consent.

5. Planned optional analytics

The planned addition of PostHog and DataFast would help us understand website and product usage, measure visits and analyse conversion attribution. Their SDKs and scripts have not yet been added. Accepting the category now only saves a preference; it does not install tools, send events, record sessions or identify users with these providers.

Preferences distinguish necessary cookies, which provide the features you request and remember your choice, from optional analytics, initially off. No advertising category is planned. Rejecting or leaving the banner unanswered keeps analytics off.

Before activation, we will publish the specific configuration, technologies and cookies used, purposes, providers, processing locations and retention periods. No duration is assigned to future cookies now. We will renew the notice version and request a fresh choice before collecting data with these tools.

6. Google and Stripe on their own websites

When you choose Google sign-in or payment, your browser is directed to Google or Stripe Checkout. Those providers may use their own cookies and technologies on their domains under their policies. This website does not embed a Stripe payment form or a Google widget.

The authentication cookies described here are first-party Screengaze cookies. In local HTTP environments, Better Auth names may appear without the __Secure- prefix; their purpose is the same.

7. Controlling cookies

The banner offers ‘Reject’ and ‘Accept analytics’, plus ‘Preferences’ to review the optional category and save your selection. You can change it or withdraw acceptance at any time through ‘Cookie preferences’ in the footer without signing in. Save with analytics unchecked to reject or withdraw it; necessary cookies remain available for their functions.

You can also inspect, block and clear cookies in your browser's privacy settings. Clearing sign-in cookies may sign you out or interrupt authentication. Clearing the preference cookie will prompt a fresh choice. Browsing, ignoring the banner or closing a preferences section does not grant consent.

8. Questions and updates

Send cookie and privacy questions to screengazestudio@gmail.com. Also consult the privacy policy for account and licence data, purposes and your rights.

This policy reflects the website configuration on the stated date. Changes in technology or purposes will be explained in a new version, with the relevant information and choices.