Cookies

Cookies are small files a site stores in your browser. We also use similar storage such as localStorage for Cookie Preferences. This page covers avaga.io and what happens when you continue to app.avaga.io.

It is not a list of cookies on Meta, Google Ads, WhatsApp, or your own website. Those stacks keep their own cookies when you run ads or paste avaga-forms.js on a customer site.

Some storage is required for avaga.io to load, keep a page from breaking, and remember that you submitted a form (the sent or error query on a thank-you URL). You cannot turn this off and still use the site.

• Next.js session and load balancing for the marketing site
• Cloudflare Turnstile on contact forms, loaded from challenges.cloudflare.com, so a stranger cannot post a lead
• Cookie preference record in this browser so we honor your last save

The marketing site uses a WhatsApp button that opens wa.me with a starting message. That click is handled by WhatsApp, not by an Avaga form script on this page.

Full-page forms on Talk to sales, Partners, and Compliance still post to /api/contact. Amazon SES delivers those leads to hello@avaga.io.

Login, Google Sign-in, 2FA, and the live floor live at app.avaga.io. Those cookies are the product, not a marketing pixel. Turning off marketing-site analytics does not sign you out of a workspace, and Cookie Preferences on avaga.io does not wipe app sessions.

Owners and admins should keep 2FA on. A stolen owner cookie is a stolen DID.

This marketing site does not currently load a third-party analytics pixel (no gtag snippet in the app shell). The Analytics toggle in Cookie Preferences is reserved. If we add a measurement tool later, it will respect that toggle and we will update this page.

Product analytics inside a workspace (floor reports, SLA, email reporting) are customer records in Avaga Workspace, not marketing cookies. They follow the Privacy Policy and your plan.

avaga.io loads the Meta Pixel from connect.facebook.net. It records a page view when you open a page, and a Lead event when a contact form is sent. The Marketing toggle in Cookie Preferences controls it: leave Marketing on to allow the pixel, or turn it off to stop the pixel in this browser. Meta, Google Ads, and LinkedIn cookies on your own campaigns are still configured in those products.

Use Cookie Preferences on this site. You can also clear cookies in your browser. Blocking all cookies may break login on app.avaga.io.

If you use Avaga in a clinic, agency, or enterprise browser with a cookie proxy, test login on app.avaga.io after the proxy rules change.

The marketing site loads the Meta Pixel. If we add another pixel, a chat tool that is not Avaga, or a new host, we will name it here. Questions: hello@avaga.io.