Privacy policy
Our commitment to privacy: cookieless analytics, zero tracking cookies, and minimal data storage.
No tracking cookies
RebateFX does not use advertising cookies, marketing tracking pixels, or cross-site tracking scripts.
We believe privacy is a fundamental standard. You can browse our website, use our calculation tools, and review broker rates without having your personal identity tracked.
Privacy-preserving analytics
We use Plausible Analytics to measure aggregate website traffic and component engagement. Plausible does not use cookies, collect personal identifiers, or store persistent tracking hashes.
All analytical data is collected in aggregate form only, such as top-level page views and general referral sources.
Local browser storage
We may store non-sensitive preferences in your local browser storage (such as whether you have dismissed a notification banner).
This data remains strictly stored on your own device and is never transmitted to our servers or third parties.
Theme and language preference
When you pick light or dark mode, or a language, we remember that choice in your browser. We use the local storage keys and cookies named rfx-theme and rfx-lang.
They hold only your choice, such as dark or vi. Our server reads them to show pages in your theme and language. They are not used for tracking and are never shared with anyone.
External links to brokers
When clicking outbound referral links to brokers, you are transferred to the broker's platform. Their respective privacy policies and data practices will then apply.
Videos from YouTube
Our video guides are hosted on YouTube, a Google service. We embed them in YouTube's privacy-enhanced mode (youtube-nocookie.com).
The player loads only when you press play. Before that, the page shows a still picture of the video, loaded from YouTube's image server (i.ytimg.com). YouTube receives your IP address and browser details when that picture loads.
After you press play, YouTube's own privacy policy applies to the player. We do not control what YouTube collects inside the player.
The consultation form
When you send the form to get help choosing a rebate, we store what you type: your name and email. If you give them, we also store your phone number, Telegram username and the broker you chose.
We also store your language, the time you sent it, your browser's name and a one-way code (a hash) of your IP address. We use these only to stop spam.
We use your details only to contact you about rebates, as you asked. Your email, phone number and Telegram username are stored encrypted. Only the RebateFX admin can read them.
We delete a request 180 days after we close it. Every request is deleted 365 days after you sent it at the latest. A database backup made before then may still hold it until that backup is deleted.
We never sell your details. We do not share them with brokers or anyone else. You can ask us to delete your request sooner through our official channels.
The form uses Cloudflare Turnstile, the same short security check as the account check below.
The account check and abuse limits
The account check uses Cloudflare Turnstile, a short security check that tells people from bots. Cloudflare processes signals such as your IP address and browser details for it.
To stop people guessing account numbers, we count how often checks are made. We keep each count under a one-way code (a hash) made from your IP address, or from the broker and account number, never the values themselves.
Each count expires when its time limit ends, after one day at most, and is then deleted automatically. A database backup made before then may still hold them until that backup is deleted.
We do not save the account number or UID you type to check it.
Your member account and sign-in
To sign in, you give us your email address. We store it encrypted, with a one-way code (a hash) to find your account.
We can email you a 6-digit code, so you can sign in without a password. A transactional email provider sends it for us.
We keep the code only as a one-way code. Each sign-in code record is deleted once it is over 24 hours old, in a daily clean-up.
When you sign in, we set one cookie, rfx_session. It keeps you signed in. It is not used for tracking. The cookie holds a random key. We store only a one-way code of that key.
Your sign-in lasts 30 days at most. It ends sooner after 14 days without use, or when you sign out. Ended sessions are deleted in the daily clean-up. Sessions you signed out of are kept for 30 days, then deleted.
A second cookie, csrftoken, protects your account against forged requests. It lasts up to one year.
To stop abuse, we count sign-in requests per email and per IP address, under one-way codes. Each count is deleted after one day at most.
Our security log records each sign-in with a one-way code of your IP address.
Account numbers and UIDs you add are stored encrypted. We only show their last 4 characters.
Your profile
In Settings you can add a display name, your country and a profile photo. All three are optional.
The display name is the name we greet you by in the app. Nobody else sees it, and we don't put it in emails.
We store your display name as you type it. Unlike your email, it is not encrypted.
Your country is a two-letter code you pick from a list. We don't check it and we don't share it.
If you add a photo, your browser first crops it square and makes it smaller.
Our server then makes a new 256 × 256 picture from it. We keep only that new picture.
We don't keep your original file or its details, such as location or camera data.
We store the photo encrypted. Only you see it, in your account.
You can change or remove your name, country and photo at any time in Settings.
If we join two sign-ins into one account, your name, country and photo move to the account we keep. Anything it already has stays.
When you delete your account, we delete them too. A database backup made before then may still hold them until that backup is deleted.
Offers and news emails
Settings has a Promotions switch for news, such as a new broker or a changed rebate rate. It stays off unless you turn it on.
We don't send these emails yet. We only save your choice. We will update this page before we send any.
If we join two sign-ins into one account, this choice does not move. You choose again on the account we keep.
Payout ledger
We publish the rebates our partner broker paid to accounts opened with our partner code: the day, the amount and the last 2 characters of the account number.
We never publish names, emails or full account numbers. A day with fewer than 3 paid accounts shows only its total.
Anyone can see this page. Published days are not edited later; a correction appears as a new entry.
Telegram Mini App
If you open RebateFX inside Telegram, Telegram tells us your Telegram user ID. We store it encrypted, with a one-way code to find your account.
We don't keep your Telegram name, username or photo.
Inside Telegram you stay signed in for up to 1 hour. The app keeps that sign-in in memory only, not in a cookie.
You can add an email to sign in on the website too. If you connect Telegram on the website, we join the two sign-ins into one.
A link to connect Telegram works once, for 10 minutes. We store only a one-way code of it.
Sign in with Google
You can choose to sign in with Google. Google then tells us your email address, whether Google has checked it, and a Google account ID.
We store the email like any other member email. We store the Google account ID encrypted, with a one-way code to find your account. We don't ask Google for your name or photo.
During the sign-in we set one short cookie, rfx_google_flow. It only links Google's answer to your sign-in. It is deleted after 10 minutes, or as soon as you are back.
We don't keep any Google token. We can't read your Gmail, contacts or files.
Your password
You can choose to sign in with an email and a password.
We store a hash of your password, never the password. A hash is a one-way code: we can check a password against it, but we can't turn it back into your password.
We save the password only after you type the code we email you, so nobody can set a password on an email that isn't theirs.
When you reset your password, we sign you out on your other devices.
To stop people guessing passwords, we count failed tries per email and per connection, stored as one-way codes only.
We never ask for your RebateFX password by email, chat or phone.
Support tickets
When you open a support ticket, we store its subject, your messages and our replies with your member account.
We store the subject and every message encrypted. Only you and the RebateFX team can read them.
Our team gets a short alert about a new ticket. The alert holds only the ticket number and its topic, never your message.
Please don't send passwords or codes in a ticket. We never ask for them.
We keep support messages for up to 1 year after a ticket is closed, then delete them. A database backup made before then may still hold them until that backup is deleted.
Weekly report emails
If your member account has an email, we send you a weekly rebate report. It is a service email about your own account.
It is on by default. We send it on Mondays, only after a week with rebates on your linked accounts.
The email shows last week's rebates by broker. It is a report only: it moves no money and promises no future rebates.
To stop it, use the "Stop these emails" link in any report, or the switch in Settings. Many mail apps also show an Unsubscribe button.
The stop link holds a signed code. It can only turn this email off. It does not sign you in.
A transactional email provider delivers it for us. We share your email address only with that provider, only to deliver the email.
For each week we keep a short record of whether the email was sent. It holds no email address and no amounts. We delete it after 400 days.
AI assistant
Our help chat uses an AI model from Anthropic to answer questions.
Please don't share passwords or personal details in the chat.
We hide email addresses and long numbers before we store or send a message.
We keep chat messages for 30 days, then delete them.
Anthropic deletes API inputs and outputs within 30 days, with some exceptions in its privacy policy.
You can delete a chat at any time with "Delete this chat", or with /stop in Telegram.
In Telegram, we keep your chat ID for up to 72 hours after your last message, only to send replies.