Wicket

Privacy

What Wicket keeps, for how long, why, and how to ask about it. Effective 17 November 2026.

Who runs it

Wicket is run by Stackwell Labs LLC, a company registered in Wyoming, USA. Write to support@stackwell.tech with any question about this page or your data, and a person will answer.

Two kinds of people

People who sign in to an app that uses Wicket give it their email address, and Wicket mails them a link. Developers register apps in Wicket's dashboard, and may buy a paid plan (Starter or Pro) for them.

The app you signed in to is run by its developer, not by us. Wicket tells that app your email address when you sign in, and what the app does with it afterwards is up to its developer and their own privacy policy. Each developer is responsible for their own use of Wicket's sign-in.

In the terms of the GDPR and the UK GDPR: Stackwell Labs is the controller of what Wicket keeps about developers, and of the records it keeps to protect and charge for the service (the sending limits, the audit record, the bot check, the monthly counts and the logs). When Wicket signs you in to an app, the app's developer is the controller of that sign-in, and Stackwell Labs handles it for them as their processor, under the data processing agreement in Wicket's terms.

What Wicket keeps, and for how long

Wicket's stored records are also kept in backups for up to 35 days, so that a deleted app can be restored after a mistake.

There is no table of apps' users: apart from those records, Wicket keeps no list of who has signed in to an app. There is no sign-up form, no profile and no password: a developer's account is the record above, made by their first sign-in. The dashboard's cookies sign a developer in and keep them signed in. Besides those, Wicket sets only the ad cookie, and only for visitors outside the European Economic Area, the UK and Switzerland. Wicket sets no cookie when you sign in to an app. No page carries a tracking pixel, and the sign-in page is the only one that carries anyone else's script: Cloudflare's bot check, below.

The ad cookie. If you come to wicketauth.com from one of our Google ads, the __Host-ad cookie keeps that ad's campaign name and Google's id for your click, for 30 days, on wicketauth.com and login.wicketauth.com, so that we can tell which ads bring developers and spend on those. If you then sign in to Wicket's dashboard for the first time, your developer account keeps the campaign and the click id, the cookie is removed, and Stackwell Labs' marketing records keep them with the time of your sign-up for 90 days. We send Google Ads the click id and that time, so that it counts the sign-up against the ad; nothing else about you goes with them. We tell your country from your network address, at the edge of our servers: visitors in the European Economic Area, the UK and Switzerland, and anyone whose country we can't tell, get no ad cookie, and one they still hold is removed.

Why, and on what legal basis

What, and whyLegal basis
Your email address, the hashes and the expiry times: to send you the link you asked for, so that it works once, for a few minutes, and for nobody else, and to tell the app who signed in. That is the service. For a sign-in to an app, we do this for its developer, as their processor, and their privacy policy gives the basis. For a developer signing in to Wicket itself, the contract (GDPR Art. 6(1)(b)).
The sending limits, Cloudflare's check, the audit record and the logs: to stop the service being used to flood someone's inbox, and to investigate abuse or a fault. Our legitimate interest, and that of everyone Wicket mails, in a sign-in service that can't be turned against them (Art. 6(1)(f)).
The monthly counts: to apply each app's plan and charge for it, holding each address only as a one-way hash. Our legitimate interest in charging for what an app uses (Art. 6(1)(f)).
A developer's account, apps and command-line credentials: to give them the service. The contract (Art. 6(1)(b)).
The billing ids: to charge for a paid plan. The contract (Art. 6(1)(b)).
The ad cookie, and the campaign and click id it brings to a developer's account: to see which ads bring developers. Only for people outside the European Economic Area, the UK and Switzerland. Our legitimate interest in measuring our own advertising.

Wicket makes no decision about anyone by automated means alone that has legal or similarly significant effects. A link refused over the sending limits, or a failed bot check, only means trying again later.

Who else handles it

Five companies process data for Wicket, each only for its part:

Amazon Web Servicesruns Wicket's servers and stores everything above, in the US (us-east-1, Virginia).
Resendsends the sign-in mail, so it handles each address and mail it sends, and keeps its own delivery records.
Cloudflareruns the check on the sign-in page that tells people from bots (Turnstile), so that nobody can make Wicket mail strangers. The page loads Cloudflare's script, which sends Cloudflare your network address and signals about your browser and device. Wicket then sends Cloudflare the check's answer and your network address, to confirm it. Cloudflare is not told your email address.
Stripetakes payment for a paid plan, so it holds the paying developer's billing details and card.
Googleruns our ads. For a developer one of them brought, from outside the European Economic Area, the UK and Switzerland, Google Ads is sent the click's id and the time of the sign-up, to count the sign-up against the ad (the ad cookie, above).

We don't sell or share data with anyone else, except where the law requires it.

Where it is handled

Stackwell Labs is in the US, and Wicket's servers and everything they store are in the US (AWS us-east-1, Virginia). The companies above may handle their part elsewhere too, as each one's own privacy policy says. If you are in the European Economic Area, the UK or Switzerland, you give your address to Wicket in the US when you sign in or register. Where a developer outside the US has Wicket handle their users' sign-ins, the data processing agreement covers that transfer with the European Commission's standard contractual clauses and the UK's addendum to them.

Your rights

You can ask us:

Write to support@stackwell.tech from the address concerned. We answer within one month, or tell you within that month if a complicated request needs up to two more. It costs nothing. The audit record is kept for its 30 days whatever happens, so that abuse can still be investigated, and backups and logs go when their time is up, as above. Developers can also delete their apps themselves, from the dashboard.

For what an app holds about you, ask that app's developer: Wicket can't see or delete it. If you ask us about a sign-in we handled for an app, we help its developer answer you.

If you think we have handled your data unlawfully, you can complain to the data protection authority where you live or work, or where you think it happened: in the UK, the Information Commissioner's Office (ico.org.uk); in the European Economic Area, your country's authority (the list). We'd like the chance to put it right first, but you don't need to ask us before you complain.

Changes

When this page changes, the date at the top changes with it. A change that keeps more, keeps it longer or adds a company that handles it is mailed to every developer with an app at least 30 days before it takes effect.