Cookie Policy

This policy covers cookies, local storage and similar technologies used by automationflowlab.com.

Cookies are small files placed on your device. Browser storage may also retain preferences or identifiers.

The Privacy Policy applies where these technologies process personal information.

Necessary technologies may support authentication, session security, abuse prevention and remembering privacy choices.

They are used only for essential purposes and should not be repurposed for advertising.

Blocking necessary technologies in your browser may prevent account or tool functions from working.

Preference, analytics, embedded-media and marketing technologies must be classified by their actual purpose.

Where consent is required, optional technologies stay off until you choose them.

Refusing optional tracking must not prevent access to essential app features.

We do not infer optional consent from scrolling, continued browsing or acceptance of the Terms.

At publication, the website does not use analytics, advertising or marketing cookies. No optional tracking is loaded.

If optional technologies are present, the consent interface offers “Accept optional”, “Reject optional” and “Manage preferences” with comparably accessible controls.

You can change your choice using the persistent Cookie Settings link.

Withdrawal stops future optional tracking but does not automatically erase information already lawfully collected.

You can also clear or block storage through browser settings. This may sign you out or reset preferences.

Connected providers may have their own cookie notices. Our interface must obtain any required choice before loading optional third-party content.

Because no optional technologies are in use, there is nothing optional to accept or reject. The Cookies link in the footer is the Cookie Settings page. If optional technologies are added later, they will stay off until you choose.

The live cookie register must list each actual cookie or storage key, its provider, purpose, category, expiry or retention period, first-party or third-party status and relevant data recipients.

The register must include similar browser storage and tracking pixels.

Unlisted optional tracking must remain disabled until the register and consent controls are updated.

Current register — necessary technologies only. AutomationFlowLab is the first party. No advertising or analytics provider is listed because none is in use.

__Host-grok-auth.session_token. Necessary. First-party. Keeps a signed-in staff session. HttpOnly. It lasts for the session lifetime and is removed when the session ends or you sign out.

__Host-grok-auth.session_data. Necessary. First-party. A short-lived signed cache of the session so repeat reads do not query the database each time. Maximum age 5 minutes.

__Host-grok-auth.account_data. Necessary. First-party. Used by the sign-in system when account data must be carried with the session. It is not used for advertising.

__Host-grok-auth.dont_remember. Necessary. First-party. Records a sign-in persistence choice when that option is used. It is not used for advertising.

__Host-grok_gate_session. Necessary. First-party. Marks that a sign-in session was established, so the site can tell a new sign-in from an existing one. It is not used for advertising.

No tracking pixels are in use.

afl-terms-acceptance. Browser local storage. Necessary. First-party. After a person accepts the Terms on staff sign-in, this browser stores the acceptance record identifier, version and time, so that acceptance can be linked to the account. It stays until site data is cleared. It is not used for advertising or analytics.

grok-auth.bearer-token. Browser session storage. Necessary. First-party. Set only inside an embedded preview after sign-in, when the browser isolates cookies. Removed when that tab session ends. An ordinary visit to automationflowlab.com does not set it. It is not used for advertising or analytics.

The public tools do not write a marketing or analytics key to local storage.

We update this policy and register when technologies change.

Material changes requiring new consent will prompt a new choice.

Contact Automationflowlab.info@proton.me with cookie or privacy questions.