Skip to content
AppIn

Cookie Policy

This marketing site measures how it is found and how our ads perform, and that needs cookies. None of them store anything until you agree, and saying no is the same one click as saying yes. The links themselves, on appin.to, are a different system and set nothing at all.

Last updated

The short version

  • This site loads Google Tag Manager. Google Analytics 4 runs through it today. The Meta Pixel, the Reddit Pixel and Google Ads are configured to run the same way and will load once we advertise on those platforms; until then they are not on the page and set nothing.
  • Nothing is stored on your device until you answer the banner. Until then every one of those tags runs with storage denied.
  • Reject all is one click and sits next to Accept all, the same size and the same weight. Refusing is not the longer path.
  • You can change your answer later, on this page.
  • A tap on an appin.to link sets no cookie and runs none of those tags. That is a separate system and it is described in our Privacy Policy.

What loads, and when

Google Tag Manager is the container the tags below sit in. It is a loader rather than a measurement tool: it decides which tags run, and the cookies further down this page are set by those tags, not by the container.

Before the container is fetched, this site sets Google’s Consent Mode defaults to denied for analytics storage, advertising storage, advertising user data and ad personalisation. That command is in the page ahead of the container on purpose. Consent state is read at the moment a tag is about to fire, so a default that arrives late is a default some tags have already ignored — one identifier, one cookie, before anybody was asked. Two signals stay granted: the ones covering security and basic functionality, which are about the site working rather than about measuring you, and which the banner therefore does not ask about.

The banner then asks. Until you answer, the tags are loaded but held: they may measure nothing to your device and they may write nothing to it.

If you accept, all four categories are granted and whichever tags are running begin storing the cookies listed below. If you reject, they stay denied and no cookie from any of those tags is written.

Your answer is remembered in your browser’s local storage under appin.consent, as the single word granted or denied. It is not a cookie, it is never sent to us, and it holds nothing else.

What each tag is for

TagCategoryWhat it is for
Google Analytics 4AnalyticsHow many people reach this site, which pages they read, which country they are in, and what brought them here — a search, a link, an ad. Read in aggregate; we do not look at individuals.
Google Ads (not yet running)AdvertisingWhether someone who clicked one of our ads on Google or YouTube went on to sign up, and building the audiences used to show our ads again to people who have visited (remarketing).
Meta Pixel (not yet running)AdvertisingThe same two jobs for our ads on Facebook, Instagram and Threads.
Reddit Pixel (not yet running)AdvertisingThe same two jobs for our ads on Reddit.

The three advertising tags mean this site takes part in remarketing: having visited here can be a reason you are shown an AppIn ad elsewhere. That is what the advertising half of the banner is asking for, and rejecting it stops it.

The cookies themselves

Set only after you accept.

CookieSet byWhat it doesHow long
_gaGoogle Analytics 4Tells one browser from another, so a second visit is not counted as a second person2 years
_ga_<container-id>Google Analytics 4Holds the state of the current session2 years
_gcl_auGoogle AdsCarries an ad click through to a sign-up so the conversion can be attributed to it90 days
_gcl_awGoogle AdsThe same, written when a visit arrives from a Google ad click90 days
IDEGoogle Ads, on doubleclick.net — a third-party cookieRemarketing and ad measurement across sites13 months in the EEA and the UK, 24 months elsewhere
test_cookieGoogle Ads, on doubleclick.net — a third-party cookieChecks whether your browser accepts cookies at all15 minutes
_fbcMeta PixelStores the click identifier from a Meta ad so a later sign-up can be attributed to it90 days
_fbpMeta PixelA first-party identifier for your browser, used to attribute conversions and to build remarketing audiencesSee the note below
A first-party identifier cookieReddit PixelThe same two jobs for Reddit adsSee the note below

The advertising rows describe what each tag writes when it runs; the three advertising tags are not running yet, so those cookies do not exist on your browser today. Every duration above is the vendor's own published default, quoted rather than measured, and a vendor can change its own default without telling us. Two rows have no figure, and we would rather leave them blank than invent one: Meta publishes a 90-day lifetime for _fbc but not, in any source we can cite, for _fbp, and Reddit publishes neither a name nor a lifetime for its pixel's cookie. Your browser will show you both, under this site's name, once they exist. This page also makes no claim about how long Google, Meta or Reddit keep what they receive on their own systems — that is set in their products, not ours, and their policies govern it.

Signing in to your AppIn account sets a session cookie so the next page knows it is still you. It is scoped to getappin.com and its subdomains, because the dashboard and the API are on separate hosts and both have to recognise the same session. It is strictly necessary — sign-in cannot work without it — so it is not something consent applies to and the banner does not cover it. It ends when the session does, and signing out ends it. Blocking it means you cannot sign in.

The same Google Tag Manager container can load on app.getappin.com after you have answered the banner here. Your answer is stored as appin_consent on .getappin.com so the dashboard can honour it. A created link is sent as an event from your browser and carries no address of any kind.

A completed sign-up and a completed subscription are measured by our own servers instead, so no cookie and no answer to this banner is involved either way. See the Privacy Policy.

A tap on an appin.to link sets no cookie and stores no identifier, and none of the tags above run there. One page is an exception worth naming: the page that gets a tap out of an in-app browser writes a single key into sessionStorage so that it does not fire twice in the same browsing session. It holds no identifier, it is not a cookie, it is not sent to us, and it is gone when the tab closes.

What we do record about a tap — a country, a platform, an outcome, and no identifier at all — is set out in our Privacy Policy. Our advertising is about this marketing site. It is not wired into the link service, and nothing anyone does on an AppIn link is used to target an ad.

Once a link hands you over, you are on someone else’s site or in an app store, and their cookies are their own. We neither control nor monitor them.

Changing your mind

That reopens the banner with your previous answer cleared, so you can answer it again. The new answer applies from that moment.

Two things worth being straight about. Rejecting after having accepted stops anything further from being stored, but it does not reach back and delete cookies that were already written — clear them in your browser’s settings for this site if you want them gone. And your answer lives in this browser on this device, so a different browser, a different device or a cleared storage means you will be asked again.

Every browser can also block or delete cookies for a site outright, which works regardless of what this banner says.

If this changes

The tags are configured inside the Tag Manager container, and the table above says which of them are running today. If we add one, remove one, start one that was waiting, or change what a tag is used for, this page changes in the same release — not afterwards. The date at the top is when its contents were last checked against what the site actually loads.

Contact

Zeisoft Yazılım Limited Şirketi
hello@getappin.com