← Back to Arrodus

LAST UPDATED · JUNE 2026

Cookie Policy

A short one. We try not to set cookies unless we have to.

What are cookies?

Cookies are small files a website stores on your device. We use the term broadly here to include localStorage — a similar mechanism built into modern browsers that stores data locally rather than sending it back with every request.

What Arrodus uses

Currently, arrodus.com uses one piece of localStorage: it saves your Tweaks panel preferences (colour scheme, typeface) so they persist between visits. This data lives only on your device — it is never sent to us or anyone else.

We do not use:

• Analytics or visitor-tracking cookies (e.g. Google Analytics)
• Advertising or retargeting pixels (e.g. Meta Pixel, Google Ads)
• Session-recording tools (e.g. Hotjar, FullStory)
• Social media tracking cookies

Because the only storage we set is strictly necessary to remember a preference you chose, we don't need to show you a cookie consent banner. We'd rather tell you this plainly here.

Third-party services

When you submit the beta sign-up form, your email is sent to Formspree. Formspree may set its own cookies to protect the form from spam. Those are governed by Formspree's privacy policy.

No other third-party scripts are loaded on arrodus.com at this time.

Managing your preferences

To clear the Tweaks preferences Arrodus has stored, open your browser's developer tools, go to Application → Local Storage → arrodus.com, and delete the relevant entries. This will reset the Tweaks panel to its defaults on your next visit.

All major browsers also let you clear all site data via their Privacy or Settings menus. If you do this, Arrodus will still work fine — your Tweaks preferences just won't persist between visits.

When we add analytics

If we introduce analytics or any other non-essential tracking in the future, we will update this policy and clearly note the change at the top. If your consent is required by law before setting those cookies, we'll ask for it before they load — not bury it in a default-on toggle.