Archi FX is a boutique web studio in Tampa, Florida. We intentionally limit how many clients we take on. We read every inquiry and respond personally. Not every request becomes a client engagement.

Archi FX

Transparency

Cookie policy

We keep tracking light on this site. Essentials support security forms and HTTPS. Optional scripts may evolve; this page summarizes what we anticipate today.

Start a conversation Back to home

Cookies and similar identifiers help security, personalization, instrumentation, attribution, concurrency management. This Cookie Policy nests under our Privacy Policy and parallels what we realistically deploy on Laravel-hosted Blade delivery today.

What counts as cookies

Besides HTTP cookies, local storage blobs, IndexedDB quotas, Pixel tags (where added later transparently through tag managers clients deploy), ephemeral session identifiers, cryptographic challenge tokens verifying forms, hashed device fingerprints aiding abuse detection collectively fall under regulators’ broad “similar technologies”.

Families we categorize

  • Strictly necessary. Secure session scaffolding, Laravel CSRF token cookies, HTTPS enforcement flags, CDN bot scoring cookies ensuring route integrity; cannot opt out without breakage.
  • Preferences. Remember color theme toggles persisted client-side (archifx-theme localStorage alias) aligning with readability choices.
  • Functional. Form draft hints, partial upload tokens, conferencing embeds honoring regional consent.
  • Analytics. We may wire privacy-forward analytics after explicit consent overlays (GA4, plausible, self-hosted equivalents). Instrumentation absent today still demands notice because stack upgrades happen.
  • Advertising. We do not run retargeting pixels broadly on informational pages; coordinated campaigns initiated through Google Ads interfaces remain subject to advertiser platforms once you voluntarily enter those portals.

Specific cookies presently anticipated

  • Laravel encrypted session identifiers when authenticated routes appear (visitor sessions generally remain stateless).
  • XSRF-TOKEN or framework equivalents guarding POST surfaces.
  • Edge security cookies from CDN or WAF suites when enabled at hosting tier.

Changing controls

Browser settings let you purge, block third-party subsets, segregate ephemeral profiles, automate Do Not Track requests (signals vary wildly). GDPR-style banners may appear layered when analytic scripts launch; adjust toggles granularly unless categories remain strictly mandatory.

Do Not Sell or Share (CPRA-style labeling)

We refrain from remunerating granular personal records for programmatic advertising through this codebase. Outreach still occurs via sales humans once you proactively email/call forms. Californians asserting rights revisit Privacy Policy contact blocks.

Children

We do not market data broker-style cookies at minors knowingly. Suspicious minors’ submissions flagged by age language receive deletion consistent with guardianship confirmations.

Where to reach us

Submit questions referencing Cookie clarification in the subject line to info@archifx.com. Expect reasonable verification before revealing technical secrets possibly aiding adversarial actors.

Policy reviews follow the effective date shown site-wide (April 2026). Refresh when tagging posture materially changes or regulators require new disclosures.