00d 00:00:00 · Black Friday — 30% off 00d 00:00:00 · Black Friday — 30% off 00d 00:00:00 · Black Friday — 30% off 00d 00:00:00 · Black Friday — 30% off

Cookie policy

Version 1.0 · effective 15/11/2026 · demo text for the prototype, not legal advice.

This policy lists the cookies the SuperAgent Social site and application set, what each one does and how to refuse them. It covers the website and the prototype application, not the sites you reach through a link.

1. What cookies are

A cookie is a small file a site stores in your browser. It can remember that you are signed in, keep a preference between visits or count a page view. Some are deleted when you close the browser (session cookies); others stay for a set time (persistent cookies). Similar technologies such as local storage and pixels are covered by the same rules.

Cookies do not run programs on your device. They hold a short identifier that the site can read on the next request, so the site can tell one browser from another without knowing who you are.

A first-party cookie is set by the site you are on. A third-party cookie is set by a service embedded in that page, such as a payment form. Session cookies disappear when you close the browser; persistent cookies stay for the period written in the policy or until you delete them. Local storage works like a persistent cookie but is not sent with every request. The policy tells you which kind each cookie is, so you can decide what to keep.

2. How we use cookies

We use cookies for three jobs: keeping you signed in, remembering your theme and language, and counting page views in aggregate. The first is required for the service. The second improves the interface but is optional. The third is optional and can be refused without losing a feature.

We do not use advertising cookies, we do not build profiles across other sites, and we do not sell cookie data. The site works without optional analytics; only the signed-in experience depends on the session cookie. If you open the application from a link in an email, a short-lived cookie remembers which workspace you meant so you do not land in the wrong one. None of these cookies follows you to another site.

3. Managing cookies

Every browser lets you see, block and delete cookies. The setting is usually under Privacy or Site data. You can also browse in a private window, which drops cookies when you close it. Blocking the session cookie signs you out and prevents publishing, scheduling and approvals.

Our cookie banner records your choice for optional categories. Changing your mind later takes one click in the banner; the change applies on the next page load. Deleting all cookies also deletes that choice, so the banner asks again.

If you block all cookies, public pages still work. Signing in, approving a post and connecting a channel do not, because the application cannot tell that the request comes from your session. A private window is a good way to check what the site looks like without the optional cookies.

We honour the Global Privacy Control signal where your browser sends one, and we do not use a cookie wall: you can refuse optional cookies and still read every public page. Do Not Track is not a standard we can rely on, which is why we ask directly instead of checking that header. The banner appears once and does not follow you around the site after you answer it.

4. The cookies we set

  • sas_session — keeps you signed in. Required. Expires when the session ends or after 30 days if you choose “remember me”.
  • sas_theme — remembers light or dark theme. Optional. Lasts 12 months.
  • sas_lang — remembers English or Vietnamese. Optional. Lasts 12 months.
  • sas_analytics — counts page views without identifying you. Optional. Lasts 13 months.
  • sas_consent — stores the cookie choices you made. Required. Lasts 12 months.

The application may set a short-lived cookie while a publish job is running so a refresh does not duplicate the job. It is deleted when the job finishes and is not used for tracking.

We keep the number of cookies small on purpose. Each cookie has one job, a defined lifetime and a name that says what it does. If a release needs a new cookie, this page and the banner are updated in the same release, and the change is listed in the changelog.

A consent record stores the categories you accepted, the version of the banner you saw and the time of your choice. We keep it so we can show that we asked, and so a later change to the banner does not silently widen what you agreed to. It contains no browsing history.

5. Third-party cookies

Our payment processor sets its own cookies on the checkout page to prevent fraud and remember the payment flow. Those cookies are controlled by the processor and its policy applies there. Our email provider may set a cookie when you open a message from us, which we use only to measure delivery, not to track you across sites. Neither provider receives your workspace content from us.

If you embed a video or follow a link to a network, that network may set cookies under its own policy. We do not control those cookies. The networks we connect for publishing do not set cookies on our site; the connection happens server to server.

Our public pages load no advertising or social plugins. A blog post may embed a video player; the player is loaded only after you click it, so no third-party cookie is set just by reading the page. If we add an embed that loads automatically, this page and the banner change before it ships. The same rule applies to a customer story or a partner logo that links out: the link opens a new page, and the destination sets its own cookies under its own policy.

6. Contact us

Questions about cookies go to privacy@superagent.social. If you believe a cookie is doing something this page does not describe, tell us and we will investigate before the next release. This page was last updated on 15 November 2026, and the version at the top of the page is the one that applies to your visit.