Cookie policy
The short version: the app sets strictly necessary cookies only. This marketing site can also set analytics and advertising cookies, separately controlled in Cookie preferences. Both are off until you approve them. Choose Configure and save with both options off to use required cookies only. The app itself has no analytics tag.
1. Cookies we set
- Session cookie (app only): keeps you signed in to your account. Set when you log in, removed when you log out or the session expires. Strictly necessary.
- Security cookies (app only): protect sign-in and forms against cross-site request forgery. Strictly necessary.
2. Local storage
We use your browser's local storage (not a cookie, never sent to our servers) for two things, both of them your own choices: your theme, under the key postauto-theme, and your answer to the cookie banner, under postauto-consent.
If you approve Advertising and you arrived from an advertisement, we also keep that ad's click identifier in session storage under postauto-click until you close the tab, so that it can travel with you to the sign-up form. With Advertising off, ad identifiers are neither written nor sent. Campaign names, such as an email campaign's source, may be stored here when either Analytics or Advertising is approved. See section 4.
3. Analytics, on this site only, and only if you agree
This marketing site uses Google Analytics through Google Tag Manager to count which pages people read. The Google container is not requested until you approve Analytics. Advertising alone does not load it. Ignoring the banner or saving both options off leaves both tracking integrations unloaded.
After you approve Analytics, Google Analytics sets its own cookies on this site, typically _ga and a _ga_ cookie per measurement stream, to tell one visit from the next. They expire after up to two years and you can delete them at any time by clearing this site's data.
app.postauto.io carries no analytics tag. Your drafts, scheduling and publishing activity are not sent to analytics providers by an app-side tracking script. Separately, the server can report account and subscription conversions using attribution identifiers previously supplied with your approval.
Your answer is remembered in local storage under postauto-consent, so you are asked once per browser. It records Required as always on and your separate Analytics and Advertising choices. Clearing your site data asks again. If your browser blocks local storage, your choice applies to the current page and you may be asked again on the next page.
4. Advertising, on this site only, and only if you agree
We advertise Postauto on Meta (Facebook and Instagram) and on Google Ads, and we need to know which advertisements bring people who go on to open an account. If you approve Advertising, this marketing site can load the Meta pixel from connect.facebook.net, which sets two cookies: _fbp, a random browser identifier, and _fbc, the identifier of the advertisement you clicked. Both last up to 90 days. Meta receives the page you were on and, on this site, two events: that you looked at the plans, and that you clicked through to create an account.
Until you approve Advertising, none of that happens. The pixel is not loaded, no request is made to Meta, and no cookie is set. There is no Meta tracking image behind a no-script tag either, because an image cannot wait for your answer.
When you click through to the app after approving Advertising, we add the advertisement's identifiers (Google's gclid and Meta's fbc and fbp, among others) to the link, so that if you later create an account we can tell Google and Meta that their advertisement worked. We also add the page you were on, which is not an identifier and is sent whatever your answer to the banner. With Advertising off, ad identifiers are left behind at this site. Separately, approving Analytics allows the Google Analytics client identifier to be passed to sign-up so the server can associate a registration with that visit. The link also carries your Advertising answer itself, as a plain yes-or-nothing marker, so that a sign-up is reported to Google with the consent you actually gave and never with more.
5. Other third-party cookies
During checkout, Stripe (our payment processor) may set its own cookies on Stripe-hosted pages for fraud prevention; those are governed by Stripe's own cookie policy. Nothing else on this site or in the app sets a third-party cookie.
6. Changing your mind
Open in the footer, turn either optional category off, and save. This stops future measurement for that category on this marketing site, removes its accessible cookies here, and stops including its identifiers in new links to the app. Clearing this site's data also removes your stored answer and asks again next time.
These controls do not revoke attribution already carried into another app tab or stored against your account on our server. Later account and subscription conversions can still be reported using those identifiers within the existing retention period. Withdraw that in the app, under Settings, Profile, Advertising measurement: the stored identifiers are cleared and no later conversion is reported. To request removal of other previously collected data, contact [email protected]. See the privacy policy for retention and data-request details.
7. If this changes
If we ever add another non-essential cookie or another advertising partner, we will update this page first and, where consent is required, ask for it before setting anything.
8. Contact
Questions about cookies: [email protected]