Privacy Policy

Last updated: 20 October 2026. This explains what bagworkRH (“we”) collects when you use bagworkRH, why we need it, how long we keep it, and how to have it removed.

1. What we collect

  • Your account — email address, username, and a password we store only as a one-way hash.
  • Your seller code — the public handle that identifies you in campaign records (for example SELLER-7K4M2P).
  • Your wallet address and the signature that proves you control it. We never receive your private key or seed phrase.
  • Your connected social identity — the platform account ID, username, display name and avatar URL returned by the platform's own API.
  • Access credentials for that account — stored encrypted, and revocable by you at any time by disconnecting.
  • Your posts that we track — post ID, URL, a text snapshot, publication date, and engagement counts, together with the periodic snapshots used to reproduce a reward calculation.
  • Verification records — whether a post is your own original work, the evidence behind that finding, and the reason if it was rejected.
  • Reward and claim records — amounts, statuses, timestamps and transaction hashes.
  • Technical data — your IP address (used to apply rate limits and to blunt abuse), request identifiers in our logs, and error reports if error tracking is enabled.

2. What we do not do

  • We do not sell, license or share your data with advertisers.
  • We do not build advertising profiles, and we do not resolve your identity across platforms.
  • We do not use your data to train models, and we do not make automated decisions about you as a person. Fraud signals queue a case for a human to review; the platform does not accuse anyone automatically.
  • We do not post, reply, like, repost, follow or message on your behalf. Our access is read-only, and there is no code path that writes to your account.
  • We never ask for your private key or seed phrase, and no legitimate member of our team ever will.

3. Why we use it

  • To run the service you asked for — verifying that a post is yours, calculating and recording the reward, and settling your claim on-chain.
  • To keep the platform and the money safe — rate limits, anti-farming signals, budget and cap enforcement, and an audit trail that a payout dispute can be settled against.
  • To meet our own obligations — keeping financial records, and honouring the platform rules the campaigns are run under.

The verification logic reads one thing from your social account: the platform's record of whether a post is an original, a repost or a quote. That single fact decides whether a payout is owed, which is why we ask for it and nothing more.

4. Who we share it with

  • The social platform you connect, through its official API — read-only, using your own authorisation.
  • The blockchain — reward and claim amounts, the receiving wallet address, and transaction data are public and permanent by design. Nothing else about you is written on-chain.
  • Our infrastructure providers — hosting, database and error monitoring, which process data only on our instructions.

We do not sell your data. We disclose it to authorities only where the law requires it.

5. How long we keep it

  • Post content and metrics: erased 365 days after the campaign it belongs to ends. The countdown starts at the campaign's end date rather than at the moment we found the post, so it measures how long the data stayed useful. Erasure is automatic and runs daily; the post's text, URL, external ID and engagement counters are removed, and the platform payloads we stored are deleted.
  • Rewards and claims are kept, with their amounts and statuses, because they are the record a payout dispute is settled against and the ledger they belong to cannot be unpicked. Every erasure records explicitly that financial records were retained, so the omission is visible rather than silent.
  • Logs and error reports are kept only as long as they are needed to run and secure the service.

6. Your choices and rights

Two different things, and the difference matters:

  • Disconnect — stops us reading your account and keeps your history. Nothing is deleted, because you may reconnect.
  • Erase — available from your account settings, or via POST /api/v1/me/data-deletion/ with {"confirm": "DELETE"}. This removes your identifiers and everything derived from the platform: post content is anonymised, stored credentials are destroyed and the access token is revoked with the platform, linked handles are replaced and the accounts disconnected, and your email, username and names are replaced with your password made unusable. It is irreversible.

Because of the financial records described above, erasure does not delete your reward and claim history, and the anonymised account row those records point at stays. You can also ask us for a copy of your data, or ask us to correct it. Write to bagworkRH@proton.me and we will respond within the time the law allows; you may also complain to the data protection authority in your country.

7. Security

  • Access credentials for your social account are encrypted at rest, and can be re-encrypted under a new key without you reconnecting.
  • Traffic is encrypted in transit, and stored credentials are never written to our logs.
  • Post content is not exposed publicly: the endpoints that reveal post URLs or engagement counts are restricted to staff, and your own posts are visible only to you.

8. Cookies and local storage

We do not use advertising or analytics cookies, and we do not embed third-party trackers. Your sign-in token is kept in your browser's local storage so you stay logged in; clearing your browser data or signing out removes it.

9. Age, changes, and contact

  • bagworkRH is not for anyone under 18.
  • If we change this policy we will update the date at the top, and material changes will be announced in the app.
  • Questions or requests: bagworkRH@proton.me. See also our Terms of Service.