Part of Wicket's terms, between you, the developer, and Stackwell Labs LLC. Effective 17 December 2026.
It applies wherever the GDPR, the UK GDPR or Swiss data protection law applies to the personal data Wicket handles to sign people in to your app. For that data, you are the controller (or a processor for your own customer), and we are your processor. Words such as “controller”, “processor” and “personal data breach” mean what the GDPR says they mean. Where this agreement and the rest of the terms disagree about personal data, this agreement wins; where the standard contractual clauses below apply, they win over both.
| Whose data | People who sign in, or try to, to your app. |
|---|---|
| What data | Their email address; the network address and browser signals of the sign-in request; hashes of the links and codes mailed to them; records of each sign-in step; a one-way hash of their address in your app's monthly count. No special categories of data. |
| What we do with it, and why | Mail them a sign-in link, check the request isn't a bot's, enforce the sending limits, give your app an ID token naming their address, count your app's monthly active users, and keep the audit record and logs: the service described in the terms, and nothing else. |
| For how long | As the privacy page says for each: links and codes for minutes, counts for a month after their month, the audit record 30 days, logs 14 days, backups 35 days. |
| Amazon Web Services | runs Wicket's servers and stores its data, in the US (us-east-1). |
|---|---|
| Resend | sends the sign-in mail. |
| Cloudflare | runs the bot check on the sign-in page (Turnstile). |
We are in the US, and so are Wicket's servers. Where you are in the European Economic Area and our handling is a transfer the GDPR restricts, the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914), Module Two (controller to processor), or Module Three (processor to processor) where you are a processor, are part of this agreement, with you as data exporter and us as data importer. In them: clause 7 is not used; under clause 9, option 2 applies, with the 30 days' notice above; the option in clause 11 is not used; under clause 17, Irish law governs, and under clause 18, the courts of Ireland decide disputes. Annex I is this page's parties and “The processing”, with the competent supervisory authority the one clause 13 names; Annex II is “Security measures”; Annex III is “Subprocessors”.
Where the UK GDPR restricts the transfer, the UK Information Commissioner's International Data Transfer Addendum to those clauses (version B1.0) is part of this agreement too, filled in from the paragraph above, and either party may end it as its Section 19 allows. Where Swiss law restricts the transfer, the same clauses apply, with the Swiss Federal Data Protection and Information Commissioner as the supervisory authority and Swiss law's terms read in place of the GDPR's.
The terms' limits of liability apply to this agreement, except where the standard contractual clauses or the law don't allow them. We change this agreement as the terms say they change, and never so that it protects your users' data less.