Privacy policy

In effect from 9 September 2026

This document describes what data the AutoSwipe AI Chrome extension and the autoswipeai.com website collect, why it is needed, who it is shared with, and how you can delete it.

In short. We store your email, subscription status and — for subscribers — a summary of your Tinder conversations: who wrote last and when. When you press a button asking for a suggested reply, the open conversation is sent to a text-model provider to write it, and is not stored afterwards; if you have linked that conversation to the same person's chat in another app, the last few messages of that chat travel with it. The conversations themselves are kept only in your browser, so that the assistant does not have to re-read them every time — and the panel menu erases them whenever you want. A voice message you ask to transcribe is sent to a speech-to-text provider and not kept. Of a match that has disappeared we also keep its last two messages, so the dashboard can say what ended it. Filter settings and swipe counters stay in your browser. Profile photos are sent to an external model only when you explicitly enable the AI photo filter and are not stored by us. Your Tinder password is never read.

1. Who processes the data

The controller is AutoSwipe AI. For any question about your data write to support@autoswipeai.com. The controller's registration details and postal address are available on request.

2. What we collect and why

All data is collected and used solely to provide and maintain the single purpose of the extension: automated browsing and swiping of Tinder profiles according to the rules set by the user.

Data	Purpose	Where stored
Email address	Account creation, sign-in, linking subscription, service emails	Supabase
Password	Sign-in	Supabase (stored only as an irreversible hash). We never see or can recover your password
Subscription status, expiry date and payment identifier	Unlocking paid features for the paying user	Supabase
Filter settings, stop-words, language and optional map location	Running the extension according to user rules	Only in the browser (`chrome.storage`). Never sent to our servers
Session token	Keeping you signed in	Only in the browser (extension and site local storage)
The conversation you are asking about — sent only at the moment you press a button that asks the assistant for something, and together with it, if you linked this conversation to the same person's chat in another app, the last messages of that chat	Writing the suggested replies, the invitation or the answer you asked for	A text-model provider, for signed-in subscribers. Passed through and not stored by us
The conversations you have opened with the assistant — up to the last few hundred messages of each of the last few dozen chats — and which of them belong to the same person	Telegram and Instagram keep only a handful of messages on screen at a time. Without this the assistant would have to scroll the whole conversation open again every time you return to it, and a chat that moved from Tinder to a messenger would lose its history	Only in the browser (`chrome.storage`). Never sent to our servers; the messages themselves reach a model only as part of a request you make, as described in the row above. The panel menu has Forget saved chats, which erases all of it at once
A voice message you asked to have transcribed: the audio itself, sent once and not stored	Turning speech into text, so the assistant can answer what was said in it	A speech-to-text provider, for subscribers. Without a subscription — and whenever the provider is unavailable — the transcription runs inside your own browser and the audio never leaves the computer
State of your Tinder conversations: match id, the person's first name and avatar, who wrote last, when, and how many messages there are. For a match that has disappeared — the last two messages of that conversation	The chats dashboard at autoswipeai.com/chats.html: which conversations are waiting for you, which went quiet, and what ended the ones that ended	Supabase, once an hour, for signed-in subscribers

What we do not collect

We keep no copy of your conversations. The two last messages of a match that has disappeared are the one exception, described in the table above. A conversation is sent onwards only at the moment you ask the assistant for something — to the model that writes the answer, which neither we nor it keeps afterwards. Nothing is sent while you simply read or write.
Your Tinder login or password — the extension operates inside the session you already opened.
Payment card details or wallet addresses — payments are handled entirely by the payment provider.
Browsing history outside Tinder, contacts, or any other personal data not listed above.

3. Profile photos (optional AI filter)

When the user explicitly enables the AI looks / body-type filter, the extension sends photos from the currently open Tinder profile card to a third-party image-processing service so that a score can be obtained and used for the swipe decision.

Only photos of other users’ profiles shown to you in the Tinder feed are sent — never your own photos.
Images are downscaled before transmission and sent over HTTPS.
We do not store the images or the scores. The model’s response is used only to decide the current swipe and remains only in the temporary panel log in your browser until the page is reloaded.
The AI provider processes the images according to its own privacy policy. The provider API key never leaves our server.

If you do not want any photos to be sent, simply leave the AI photo filters disabled. All other filters (age, height, distance, keywords, verified badge, number of photos) work entirely locally and send nothing.

4. Who the data is shared with

Recipient	What they receive	Purpose
Supabase	Email, password hash, subscription status	Account and database hosting
NOWPayments	Payment amount and an internal account identifier; for card payments — the data you enter on their form	Processing payments
Image-processing model provider	Profile photos from the Tinder feed (only when AI filter is enabled)	Generating a score used for the swipe decision
Text-model provider	The conversation you asked about, and the last messages of a chat you linked to it — only when you press a button that asks for a suggestion	Writing the suggested replies
Speech-to-text provider	A voice message you asked to have transcribed	Turning speech into text
GitHub Pages	Standard technical request data when you visit the website	Website hosting

We do not sell user data. We do not share data for advertising, profiling, or any purpose unrelated to the single purpose of the extension.

5. Limited Use commitment

The use of information received from users and from Google APIs (if any) adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide and improve the disclosed single purpose of the extension and is not transferred for unrelated purposes.

6. How long we keep data

Account data — for as long as the account exists.
Payment records — for as long as required by payment-system rules and accounting obligations.
Settings and counters in the browser — until you remove the extension or clear the data.
Conversation summary — for as long as the account exists; deleting the account removes it. Of a disappeared match only the last two messages are kept: the rest of the tail is discarded as soon as the reason for the unmatch has been worked out.

7. Your rights

Write to support@autoswipeai.com to:

receive a copy of the data we hold about you;
correct inaccurate data;
delete your account and all associated data;
withdraw consent to processing (this will stop the service from working).

We respond within 30 days.

8. Children

The service is not intended for anyone under 18, as it works with a dating application that has the same age restriction.

9. Changes

For material changes we will update the date at the top of this page and notify you at the email address associated with your account.