Privacy

Last updated 27 October 2026. Version 2026-10-27b. This policy covers the Premium App Drops website, the waitlist, accounts, claiming codes and our emails.

Who is responsible

Premium App Drops is run by Selanto Apps, the sole proprietorship (eenmanszaak) of Antonio Cappiello, registered with the Dutch Chamber of Commerce (KvK) under number 75803097. Selanto Apps is the controller of your personal data.

Contact: hello@premiumappdrops.com. Our postal address is on our Legal page.

In short

We use your email address to run the waitlist, to sign you in and to email you about drops.
We never sell your data and never give your email address to app developers or advertisers.
We don't keep your IP address in our database.
We use advertising cookies only if you choose "Accept" on our cookie banner. You can change your mind at any time.
Your codes are shown only to you.
You can unsubscribe in one click, end your account yourself and ask us to delete everything at any time.

What we collect

When you join:

Your email address, and whether you joined as a user or as a developer.
Users: which phone you use.
Developers: the App Store and Google Play links you give us, and your answers to our questions about Drop #001. For Founding Indies, which personal PricePush codes we gave you (stored encrypted), so your page shows the same ones each time. If you delete your sign-up, the codes stay used but no longer point to you.
Proof of your consent: when you ticked the box, which version of the text you saw, which version of the Terms applied, and when you confirmed your email.
Your country, worked out from your network. We don't record your city or exact location.
How you found us: campaign tags in the link you used, the page you landed on and the website that sent you.
If someone invited you: their referral code and which share button the link came through (WhatsApp, email and so on). They see how many people joined with their link, and we email them when a friend joins, but we never tell them who.
Your own referral code, and how many people joined with it.

When you create an account:

Your email address, and how you signed in: Apple, Google or an email link. Google tells us your email address, your name and the web address of your profile photo. Apple tells us your email address, which can be a private relay address that hides your real one, and your name if you choose to share it.
Sign-in records: the connection between your account and Apple or Google, and the sign-in links we sent you until they expire. A session cookie keeps you signed in.
The Terms version you accepted, when, and that you confirmed you are 16 or older.
A display name, if you add one. It is optional.
An avatar, if you add one: one from our set, your Google photo, or a picture you upload. We save the web address of your Google photo with your account, but we copy the photo itself only if you choose it as your avatar. An uploaded picture is re-encoded and its metadata (such as location) is removed. Avatars are stored in Vercel Blob, a private file store in Frankfurt, Germany.
Your choice to show your display name and avatar to the person who invited you. It is off by default.
Your badges are worked out from your claims and referrals when you open your account page. Only you see them, and we don't store them.

When you claim a code:

Which drop and which phone type (iPhone or Android), and when you claimed.
The code you received. We store it encrypted and show it only to you.
Your country, worked out from your network. We don't record your city or exact location.
Scrambled codes (keyed hashes) of your network and of your device, and a scrambled copy of your email address in its short form (without a plus tag and, for Gmail, without dots). We use them to enforce one code per person per drop and the monthly limit, and to check claims when more than 20 come from one network in one drop. We never store your IP address.
A log entry when you open a code: which claim, your account, the scrambled code of your network and the time. Opening it again from the same network within the same hour adds no new entry.

If you email us, we keep your message and our reply.

Developers: we keep short notes on our contact with you, such as when we wrote to you and whether you said yes to a drop.

When you use the site:

Visit statistics (Vercel Web Analytics): pages viewed, the website that sent you, country, browser and device type. It works without cookies and doesn't follow you across websites. We remove private links, such as your welcome page key, before anything is counted.
A bot check (Vercel BotID): when you send a form, a script checks technical signals from your browser to tell people from bots. We only use the result to block abuse.
Rate limits: to stop abuse, we turn your IP address and your email address into keyed hashes (scrambled codes) and count requests for a short time, for example for sign-in links and claims. We never store your IP address itself.
Fair referrals: when you confirm your spot, we keep the scrambled code of your network for 24 hours, linked to your referral code. If someone confirms with your link from that same network within the day, we keep their sign-up but don't count it as your referral. We also count, per referral link and day, how often it is opened and how often its share buttons are pressed, and through which button, without storing who opened it: the same scrambled network code, kept for 24 hours, makes sure one network counts once a day.
Your cookie choice and, only if you accept advertising cookies, what our advertising partners receive. The Cookies section below explains both.

Our hosting provider and, if you accept advertising cookies, our advertising partners receive the technical data every browser sends with a request, including your IP address.

Why we use it, and on what legal basis

What	Why	Legal basis (GDPR)
Your email address and sign-up details	To keep your spot, count your referrals, give you first pick and, for developers, the Founding Indie perks	Our agreement with you, the Terms of use (art. 6(1)(b))
Emails about the waitlist and new drops	Because you asked for them	Your consent (art. 6(1)(a)). You can withdraw it at any time.
Bot check, rate limits, checks for fake referrals	To keep the waitlist fair and safe	Our legitimate interest in preventing abuse (art. 6(1)(f))
Country, campaign tags, landing page, referring website, visit statistics	To learn which channels bring people, so we spend our time well	Our legitimate interest in running and improving Premium App Drops (art. 6(1)(f))
Proof of consent	To show that you agreed	Our legal obligation to prove consent (art. 6(1)(c))
Your emails to us	To answer you	Our legitimate interest in answering (art. 6(1)(f))
Your account: email address, name, sign-in records, avatar, the Terms version you accepted	To let you sign in, claim codes and manage your account	Our agreement with you, the Terms of use (art. 6(1)(b))
Your claims, your codes and the log of when you opened them	To give you your code, show it only to you and answer questions about a claim	Our agreement with you, the Terms of use (art. 6(1)(b))
Scrambled network and device codes, the device cookie, claim limits, bans	To keep claims fair: one code per person for each app in a drop, the monthly limit, and finding abuse	Our legitimate interest in preventing abuse (art. 6(1)(f))
Internal alerts about sign-ups, claims and actions we take on accounts	To spot abuse and problems with the service quickly	Our legitimate interest in preventing abuse and keeping the service running (art. 6(1)(f))
Your cookie choice (the pad_consent cookie)	To remember whether you accepted or rejected advertising cookies, and to show that you chose	Our legal obligation to respect and prove your choice (art. 6(1)(c))
Advertising cookies, and the events our advertising partners receive	To see which of our ads bring people who join, so we spend our ad budget well	Your consent (art. 6(1)(a), and art. 11.7a of the Dutch Telecommunications Act for the cookie). You can withdraw it at any time through "Cookie settings".

Where we rely on legitimate interest, you can object at any time.

When you sign in with Google, we only use what Google tells us (your email address, name and profile photo address) to run your account. The use and transfer by Premium App Drops of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You need to give your email address to join. Everything else is optional or collected automatically.

We don't make decisions about you based only on automated processing that have legal or similarly big effects. Our bot check and rate limits can block a sign-up automatically. The claim limits can refuse a claim automatically, for example a second claim from one device in one drop. If that happens to you by mistake, email us and a person will review it. When a claim is held for a check, a person decides whether it goes ahead. A person also decides every ban, and we ban only for abuse.

Who sees your data

Inside Selanto Apps, only the people who run Premium App Drops can see your data, and only what they need to answer you, run the drops and stop abuse. The admin tools need a separate, recent sign-in from an approved address.

We never sell your data, and we never share your email address with app developers or advertisers.

These companies process data for us, under contracts that oblige them to protect it:

Vercel Inc. (USA): hosting, visit statistics, the bot check and Vercel Blob, the private file store for avatars. Our server code runs in Frankfurt, Germany, but requests pass through Vercel's global network.
MongoDB Inc. (MongoDB Atlas): our database, stored in the EU.
Upstash Inc.: rate-limit counters, stored in the EU.
Twilio Inc. (SendGrid): sends our emails. SendGrid stores email data in the USA.
Google (Google Workspace): our mailbox, hello@premiumappdrops.com.

We use Telegram (Telegram Messenger Inc., based in the United Arab Emirates) as our internal alerting and monitoring service. It carries private alerts to us so we can spot abuse and problems with the service quickly. An alert shows your email address only in masked form, such as a***@gmail.com, with a link to your record in our admin tools. That link works only for us. An alert can also contain details about your sign-up (such as your country, how you found us and, for developers, your app links), your claims or an action we took on your account, such as a ban. Alerts never contain your full email address, a code or your IP address. Telegram works under its own terms, not a data processing contract with us (see Data outside the EEA).

These companies receive data and decide themselves what they do with it, under their own privacy policies:

Apple and Google, only if you choose to sign in with them. They check who you are and tell us the details listed above. They know that you signed in to Premium App Drops. Their own privacy policies apply to what they do with it.
Our advertising partners, only if you choose "Accept" on our cookie banner. The Cookies section names them and says what they receive. We and each partner are jointly responsible for collecting this data on our site and sending it to the partner. After that, the partner is responsible for what it does with it, as its own privacy policy says.

We may also share data when the law requires it, for example with a court or the tax authorities.

Data outside the EEA

Some of these companies, including our advertising partners, are based in the USA or can access data from there. For transfers to the USA we rely on the EU-US Data Privacy Framework for companies certified under it, and otherwise on the EU Standard Contractual Clauses.

Telegram is based in the United Arab Emirates. The EU has no adequacy decision for that country, and we have no data processing agreement or Standard Contractual Clauses with Telegram. Alerts show email addresses only in masked form, but together with the other details in an alert we can still link them to a person, so we treat them as personal data. Telegram says it stores the data of accounts registered in the EEA in data centres in the Netherlands. We send it only alerts, and they are deleted after 1 month.

Email us for a copy of the safeguards.

How long we keep it

Sign-ups you never confirm: deleted 30 days after you signed up.
Your account (email address, name, avatar, settings): until you end it. Ending your account is described below.
Sign-in sessions: 30 days after you sign in. Sign-in links work for 15 minutes, and unused ones are deleted when they expire.
Claims and the code you received (drop, phone type, country, scrambled network and device codes, time, and the scrambled copy of your email address): 24 months after the claim. If you delete your account, the claim stays for the rest of that time without your country, and with scrambled codes in place of you, as described below.
Logs of when you opened a code: 12 months.
Claim counters that enforce the monthly limit: they expire 1 day after the month ends. Counters for claims from one network in one drop expire 1 day after the drop closes.
Avatars: until you change them or delete your account. If a deletion fails, we retry it every day.
The device cookie: 1 year.
If we ban an account: a scrambled copy of the email address, for as long as the ban lasts.
Confirmed sign-ups: for as long as you're on the list. Unsubscribing stops our emails but keeps your spot, so you still get first pick. To remove your spot and your data, email us, and we delete it within 30 days. If claiming opens and you never create an account, we delete your sign-up 12 months after Drop #001.
Rate-limit counters: 10 minutes for IP addresses, except the daily limit on sign-in links from one network (24 hours), and 24 hours for email addresses.
Network codes for fair referrals and link counts: 24 hours.
The daily counts for your referral link: as long as your sign-up, and deleted with it.
Internal alerts (Telegram): deleted automatically after 1 month.
Your cookie choice (pad_consent): 12 months. Then we ask again.
The welcome page cookie (pad_wk): 7 days.
Only if you accept advertising cookies: our partners' cookies on our site last as long as the list under Cookies says, or until you choose "Reject". The conversion cookie (pad_conv) lasts at most 1 hour. What a partner received stays with it for as long as its privacy policy says.
Emails with us: up to 2 years after our last message, unless they are about a purchase.
Purchases (such as the launch kit): invoices and related records for 7 years, because Dutch tax law requires it.
After we delete your data, we keep nothing about you. You can sign up again later, and you'll confirm by email like the first time.

Ending your account

You can end your account yourself on your account page, with "End my account and withdraw". This also withdraws you from your agreement with us (the Terms of use), at no cost. We send a short confirmation to your email address, and the account is deleted at once. We delete:

your profile, with your display name and settings;
your sign-in records, your sessions and any sign-in links that are still open;
your avatar;
the logs of when you opened your codes.

Your claims stay, with a scrambled code in place of your account. They never held your email address itself, only a scrambled copy of it. The monthly claim counters also hold only that scrambled copy, and they are deleted 1 day after the month ends. We keep them so the limits still work: you can't get a second code in a drop by deleting your account and signing up again. They no longer show a name, an email address or a country. They can only be matched to an address if someone gives us that address again. They are deleted 24 months after the claim.

Ending your account does not remove your waitlist spot, and we keep sending its emails until you unsubscribe. The unsubscribe link in each email stops them. To leave the waitlist completely, email us.

If we banned your account for abuse and it is deleted, we keep only a scrambled copy of your email address, so the ban holds. We keep no name, no profile and no reason.

Your rights

Wherever you live, you can ask us to:

show you the data we have about you and give you a copy, also as a file you can take elsewhere;
correct it;
delete it;
limit how we use it;
stop using it for something you object to. For emails, the unsubscribe link does this at once.

You can withdraw your consent at any time. For our emails, use the unsubscribe link. For advertising cookies, use "Cookie settings" at the bottom of every page. Withdrawing doesn't affect what we did before.

Email hello@premiumappdrops.com. We answer within one month. We may ask you to confirm the request from the email address on the list.

You can also complain to a data protection authority. In the Netherlands that is the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl). You can also contact the authority where you live. We'd be glad to have the chance to fix things first.

Age

You must be 16 or older to join or to create an account. We ask you to confirm it the first time you sign in. If you think someone younger has signed up, email us and we'll delete the sign-up and the account.

Cookies

We use two kinds of cookies. Strictly necessary cookies make the site work and need no consent. Advertising cookies are set only if you choose "Accept" on our cookie banner. The visit statistics and the bot check described above don't use cookies.

Strictly necessary

The sign-in cookie keeps you signed in until 30 days after you sign in. While you sign in with Apple or Google, a few more short-lived cookies protect that step. Our admin sign-in uses the same kind of cookie.
The device cookie (pad_did) is a security cookie. It holds a random value, can't be read by scripts on the page and lasts 1 year. We set it the first time you press Claim. We keep only a scrambled copy of it with your claim, so we can allow one claim per device for each app in a drop. We don't use it for anything else.
The welcome page cookie (pad_wk) takes you to your welcome page after you confirm your spot. It carries your private welcome key, so the key doesn't appear in the address bar. Scripts on the page can't read it, and it lasts 7 days.
The consent cookie (pad_consent) remembers your choice on the cookie banner ("Accept" or "Reject"), the version of the banner and the date. It lasts 12 months. Then we ask again.

Advertising (only with your consent)

We advertise Premium App Drops with advertising partners. To see which ads bring people who join, we use their measuring scripts (often called pixels). They load only after you choose "Accept". They never run on your account pages, the drop pages, the sign-in, confirm and unsubscribe pages, or any page whose address holds a private link.

This list always shows exactly the advertising partners that run now:

We don't use any advertising partners at the moment, so no advertising cookie is set.

If we add a partner, the banner asks you again, because your earlier choice covers only the partners listed when you made it.

The partners receive three kinds of events: you viewed a page, you confirmed your waitlist spot, and you created an account. Each event comes with a random event id, the page address, the website that sent you, the partner's cookie id and, if you came from that partner's ad, the click id from that link.
When you confirm your spot or create an account, and only if you accepted, we set the conversion cookie (pad_conv). It holds only the kind of event and a random event id. The next public page sends the event and deletes the cookie. It lasts at most 1 hour.
They never receive your email address, your name or any code from us.
If you are signed in to a partner's own service in the same browser, that partner can link these events to your account there.

If you choose "Reject", or don't choose, no partner script loads. We still count which campaign brought you from the tags in the link, without cookies, as described above.

To change your choice, use "Cookie settings" at the bottom of every page. If you reject after accepting, the partner scripts stop from the next page and we delete the partners' cookies on our site. This doesn't affect what was sent before.

Changes

If we change this policy in a way that matters to you, we'll email you before the change applies. The date at the top shows the last update.

See also the Terms of use and the Legal page.