Privacy Policy
BountyTN · last updated 8 October 2026 · this version takes effect on the date shown and replaces all earlier versions
Who is responsible for your data
BountyTN (“BountyTN”, “the Service”, “we”) is operated by Dhia Elabed, an individual developer based in Tunisia, acting as the data controller for the personal data described in this policy. BountyTN is not a company and has no corporate parent, subsidiary or affiliate. There is no data protection officer, because the Service does not meet the threshold at which one is required; the operator handles all data protection matters personally at the address in Contact.
The operator has no commercial relationship with TikTok, Meta or Google. BountyTN is an independent third-party client of their public APIs, used with permission that you grant and can withdraw.
Scope of this policy
This policy covers the BountyTN website and web application served from the BountyTN domain, including the account-connection flows and the metric lookups they enable. It applies to everyone who visits the site or connects an account, wherever they are located.
It does not cover TikTok, Instagram, Facebook, YouTube or any other platform. When you are sent to a platform's login screen you are on that platform's own property and its privacy policy governs what happens there. Nor does it cover anything you do with the numbers after BountyTN shows them to you.
What data is collected
BountyTN collects only what it needs to answer the question you asked. There is no sign-up, so there is no account to create and no profile to fill in.
Account connection data
When you connect a social media account, the Service receives and stores:
- the access token the platform issues, and the refresh token where the platform provides one;
- the account identifier the token belongs to — the
open_idfor TikTok, the user id for Instagram, the Page id for Facebook, the channel id for YouTube; - your display name and the URL of your profile picture, so the app can show you which account a reading was taken with;
- the scopes granted and the token's expiry time.
Metric data
For each video you look up, the Service stores:
- the video's platform id and URL, its caption and its publish time;
- its view, like, comment and share counts as the platform reported them;
- the time of the reading, which account it was taken with, whether ownership was confirmed and on what basis, and whether any figure came back rounded rather than exact;
- the raw API response, kept as a record of what the platform actually returned, so a number shown to you can always be traced back to its source.
Technical data
- Standard web server logs, written by the reverse proxy: IP address, timestamp, requested path, HTTP status, user agent and referrer. These exist to keep the server running and secure, not to analyse visitors.
- Application error logs, which may incidentally contain a request path or a platform error message.
What is never collected
- Your password. Authentication happens entirely on the platform's own login page. No password is ever shown to, typed into, transmitted through or stored by BountyTN.
- Your email address, phone number, postal address, date of birth, contact list, calendar or precise location.
- Payment or financial data — the Service is free and has no payment function of any kind.
- Special category data under Article 9 GDPR (health, race or ethnic origin, political opinions, religious beliefs, trade union membership, genetic or biometric data, sex life or sexual orientation). The Service has no field for it and does not infer it.
- Direct messages, drafts, private content, or any content belonging to anyone else.
- Anything at all if you only read the site and never connect an account.
Where the data comes from
All personal data comes from one of two places: from you directly, when you choose to connect an account and paste a link; or from the platform's API, when it answers a request made with the token you granted. BountyTN does not buy, rent, scrape together or otherwise acquire personal data from data brokers or any other third-party source.
Why it is used, and the legal basis
Under the UK and EU General Data Protection Regulation a controller must name a lawful basis for each purpose. BountyTN's are:
| Purpose | Data used | Legal basis |
|---|---|---|
| Reading the metrics of a video you asked about and displaying them to you | Connection data, metric data | Performance of a contract (Art. 6(1)(b)) — this is the service you asked for |
| Keeping you connected between page loads | Session cookie, account identifier | Strictly necessary for a service you requested |
| Checking that a video you asked about belongs to the account you connected, and refusing if it does not | Account identifier, video owner id | Performance of a contract (Art. 6(1)(b)) and legitimate interests (Art. 6(1)(f)) in preventing misuse of the Service against third parties |
| Keeping an audit record of what a platform returned, so a displayed figure can be verified later | Metric data, raw API response | Legitimate interests (Art. 6(1)(f)) in the accuracy and verifiability of the figures the Service reports |
| Keeping the server available, secure and free of abuse | Server logs | Legitimate interests (Art. 6(1)(f)) in the security of the Service |
| Answering your questions and handling your rights requests | Whatever you include in your message | Legal obligation (Art. 6(1)(c)) and legitimate interests (Art. 6(1)(f)) |
Where the basis is legitimate interests, the operator has considered whether that interest is overridden by your rights, and concluded it is not: the data is the minimum needed, it stays on one server, it is never combined with anything else, and you can object or have it erased at any time. You can ask for the balancing reasoning in writing.
Your data is never used to build an advertising or marketing profile, to score or rank you, to train a machine learning model, or for any purpose unrelated to showing you the metrics you asked for.
Platform data: TikTok, Meta and Google
Data obtained through a platform API is held to the terms of that platform's developer policy in addition to this one.
TikTok
With your authorisation, BountyTN requests the scopes user.info.basic and video.list through the TikTok Login Kit and Display API. It uses them to read your TikTok display name, avatar URL and open_id, and to list the videos published on your own TikTok account together with each video's caption, cover image URL, create time and its view, like, comment and share counts.
TikTok data is handled as follows:
- Use. Only to display your own TikTok metrics to you, in the session in which you asked for them, and to keep the audit record described above. It is not used for advertising, not sold, not licensed, not used to train models, and not combined with data from any other source.
- Storage. On the operator's own server, described under storage. Tokens are kept on disk with filesystem permissions restricting them to the application's own user.
- Sharing. TikTok data is shared with nobody. It is never transferred to any third party, including other platforms, analytics vendors, advertisers or data brokers.
- Deletion. Disconnecting TikTok inside the app deletes the stored TikTok token immediately. Revoking BountyTN in your TikTok settings has the same effect on TikTok's side. Stored TikTok metric records are deleted on request, within 30 days.
TikTok's own handling of your data is governed by the TikTok Privacy Policy.
Meta — Instagram and Facebook
With your authorisation, BountyTN reads the media published on the connected Instagram account, or the videos published by a Facebook Page you administer, together with their view, like and comment counts. Meta Platform Data is used only to provide the feature you asked for, is not transferred to any third party, and is deleted when you disconnect or on request. Meta's own handling is governed by the Meta Privacy Policy.
Google — YouTube
BountyTN uses YouTube API Services and requests read-only access (youtube.readonly), which it uses only to list the videos on the connected channel and read their statistics. BountyTN's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. By connecting a YouTube channel you also accept the YouTube Terms of Service; Google's handling of your data is governed by the Google Privacy Policy. You can revoke BountyTN's access at myaccount.google.com/permissions.
Cookies and similar technologies
BountyTN sets no advertising cookies, no analytics cookies and no cross-site tracking identifiers, and embeds no third-party tags, pixels or beacons. There is no consent banner because there is nothing to consent to: every cookie it sets is strictly necessary for a function you asked for.
| Cookie | Purpose | Contents | Lifetime |
|---|---|---|---|
tm_tiktok, tm_instagram, tm_facebook, tm_youtube | Keeps you connected to that platform between page loads | That account's identifier and a signature. Nothing else. | Until you disconnect, or the token expires |
| OAuth state cookie | Protects the connection flow against cross-site request forgery, as the OAuth specification requires | A random value, matched once and discarded | The few minutes of the connection flow |
| Operator session cookie | Signs the operator in to maintenance functions. Never set for ordinary visitors. | A signature | The session |
You can delete these cookies in your browser at any time. Doing so signs you out; it does not by itself delete the stored token, which is what disconnecting does.
Who the data is shared with
BountyTN does not sell, rent, trade or otherwise disclose personal data for money or for any other consideration, and has never done so. There are no advertising partners, no analytics providers, no data brokers and no marketing lists.
Data leaves the server in only these circumstances:
- To the platform whose API you asked to be called — TikTok, Meta or Google — as part of the request that fetches your metrics. This is the Service doing what you asked.
- To the hosting provider, which operates the virtual server the application runs on and can in principle access the disk, acting as a processor under contract. It does not use the data for its own purposes.
- To an optional third-party data provider, where the operator has configured one for a platform whose own API will not serve a figure. Where this is in use, only the public URL of the post being looked up is sent — never a token, never your identity. The app shows which source a reading came from, so you can always see when this path was used.
- Where the law requires it — in response to a valid, binding legal demand from a competent authority. The operator will tell you unless legally prohibited from doing so.
- To protect the Service, where disclosure is strictly necessary to investigate abuse, fraud or a security incident, or to defend a legal claim.
There is no onward transfer for any other purpose. If the Service were ever transferred to another operator, you would be notified beforehand and given the opportunity to have your data erased first.
Where the data is stored and processed
All BountyTN data is stored on a single virtual private server rented by the operator, hosted in the European Union (France). There is no additional database service, no cloud storage bucket and no backup held by a third party.
The operator administers the server from Tunisia, so personal data is accessed from outside the European Economic Area. Where BountyTN relies on an EU or UK legal basis, that access is covered by the appropriate safeguards for a transfer to a third country, including Standard Contractual Clauses where applicable, and is limited to the operator alone. Calling a platform API also sends data to that platform, which may process it outside the EEA under its own policy and safeguards.
How long it is kept
| Data | Kept for |
|---|---|
| Access and refresh tokens | Until you disconnect, until the platform expires them, or until you ask for deletion — whichever comes first |
| Account identifier, display name, profile picture URL | Deleted with the token |
| Metric records and raw API responses | Up to 24 months from the reading, as the audit record of what was reported — or immediately on request |
| Web server access logs | 30 days, then rotated out |
| Application error logs | 30 days, then rotated out |
| Correspondence with the operator | 12 months after the matter is closed |
Nothing is kept indefinitely, and nothing is kept for a purpose it was not collected for.
How it is protected
- All traffic is served over HTTPS; plain HTTP is redirected and never serves content.
- The application is not reachable directly from the internet. A reverse proxy is the only public entrance, and it terminates TLS.
- Tokens are stored outside the web root with filesystem permissions restricting them to the application's own user, and are never written to logs or sent to the browser.
- Session cookies are signed, HTTP-only and marked secure, so page scripts cannot read them.
- The connection flow uses the OAuth 2.0 authorization code grant with a state parameter, so a connection cannot be initiated by a third-party site on your behalf.
- Ownership of a post is verified before any figure is displayed.
- Administrative access to the server is restricted to the operator, over SSH with key authentication.
No system is perfectly secure, and the operator does not claim otherwise. In the event of a personal data breach likely to result in a risk to your rights and freedoms, the operator will notify the competent supervisory authority within 72 hours of becoming aware of it, and will notify you directly without undue delay where the risk is high.
Your rights, and how to exercise them
Wherever you live, you may exercise all of the rights below. They are listed in the language of the GDPR; equivalent rights under other laws, including the California Consumer Privacy Act as amended, are honoured on the same terms.
- Access — a copy of the personal data held about you, and confirmation of what is being done with it.
- Rectification — correction of anything inaccurate. Figures read from a platform are reproduced as that platform reported them; where the platform itself is wrong, the correction has to be made there.
- Erasure — deletion of your data. See Deleting your data.
- Restriction — processing paused while a dispute about accuracy or lawfulness is resolved.
- Portability — the data you provided, in a structured, commonly used, machine-readable format. BountyTN exports it as JSON.
- Objection — to processing based on legitimate interests. There is no direct marketing to object to, because there is none.
- Withdrawal of consent — where consent is the basis, withdraw it at any time; disconnecting an account does this directly and takes effect immediately.
- Non-discrimination — exercising any of these rights will not get you a degraded service. There is no paid tier to be moved out of.
To exercise any right, email stuffshop.tn@gmail.com from the address you can be reached at, saying which platform account the request concerns. The operator will acknowledge within 7 days and respond substantively within 30 days, extendable once by a further 60 days for a genuinely complex request, in which case you will be told why. There is no charge. Where the request concerns a connected account, the operator may ask you to re-connect it, or to confirm the request from the account itself, as proof that it is yours — no identity document is ever requested.
Deleting your data
There are three ways, and they do different things:
- Disconnect inside the app. Deletes the stored access and refresh tokens for that platform immediately, along with the identity details attached to them. The Service can no longer read that account. This is instant and needs nobody's involvement.
- Revoke BountyTN in your platform settings. In your TikTok, Instagram or Facebook settings, or at myaccount.google.com/permissions for YouTube. Invalidates the token at the platform's end, so it cannot be used even if a copy existed.
- Email the operator for full erasure. To have the stored metric records and raw API responses deleted as well, email stuffshop.tn@gmail.com. This is completed within 30 days and confirmed to you in writing. Server logs containing an IP address rotate out on their own 30-day cycle.
Children
BountyTN is not directed at children. It is intended for people who publish video on a social media platform, and its minimum age is the higher of 16 or the minimum age of the platform you connect — which is 13 for TikTok in most countries, and higher in some. The Service knowingly collects no data from anyone below that age, and has no feature that would appeal to a child. If you believe a child's data has reached the Service, email the address in Contact and it will be deleted without delay.
Automated decision-making
There is none. BountyTN makes no automated decision that produces a legal effect for you or otherwise significantly affects you, and does no profiling within the meaning of Article 22 GDPR. The ownership check is a direct comparison of two identifiers, with the reason for its outcome shown to you.
Changes to this policy
This policy may be updated as the Service changes or the law does. The date at the top always reflects the current version. A change that materially reduces your rights or broadens how your data is used will be announced on this page, and on the home page, at least 14 days before it takes effect; where consent is the basis, fresh consent will be sought rather than assumed. Continuing to use the Service after a change takes effect means you accept the updated policy.
Complaints
If something about this has gone wrong, raise it with the operator first — it is one person and it is usually quickest. If you are not satisfied, you have the right to lodge a complaint with a data protection supervisory authority: in Tunisia, the Instance Nationale de Protection des Données Personnelles (INPDP); in the EEA or the UK, the authority for the country where you live, work or where the issue arose. Complaining to an authority does not affect any other remedy available to you.
Contact
Questions about this policy, requests to exercise a right, and requests to delete stored data all go to one address:
Dhia Elabed · Tunisia · sole operator and data controller for BountyTN. Expect an acknowledgement within 7 days.
See also the Terms of Service, which set out the rules for using BountyTN.