Cookie Policy
Overview
Autonomy Bridge uses a low-footprint site setup.
This policy explains what cookies and similar technologies may be used on the site, what is not used, and what choices users have at the browser level.
What Are Cookies
Cookies are small text files stored by a browser when you visit a website.
They can be used for technical functions, analytics, session handling, or advertising. Autonomy Bridge uses a narrow subset of these functions.
Cookies We Use
Analytics, if applicable
The site may use a privacy-first analytics tool to understand aggregate traffic patterns, such as page views, referral sources, and broad geography.
No personally identifiable information is collected for this purpose. No cross-site tracking is used. If the analytics setup remains privacy-first, no persistent advertising or profiling cookie should be set.
Cookies We Do Not Use
Autonomy Bridge does not use:
- advertising or retargeting cookies
- social media tracking pixels
- third-party behavioral profiling cookies
- session recording tools that capture personal data
- heatmap tools that capture personal data
The site does not share browsing behavior with advertisers or data brokers.
Netlify and Functional Behavior
If a contact form is submitted, Netlify may set a short-lived session token required for technical form handling.
That token is functional only. It is not used for advertising or behavioral tracking and should expire when the session ends.
How to Opt Out
Users can limit or block cookies and scripts through standard browser controls.
Common options include:
- blocking cookies in browser settings
- using script-blocking tools such as uBlock Origin
- using privacy-focused browsers such as Firefox or Brave
Jurisdiction Notes
Canadian users may have rights under PIPEDA.
California users may have rights under CCPA or related state privacy laws, depending on applicability.
Requests related to site data practices can be made through the contact page.
Updates to This Policy
If tracking practices change, this policy will be updated before the new configuration is deployed.
The current version is identified by the last updated date at the top of the page.