Privacy notice

Who is responsible

Bump-Up.net is the service’s trading name. The legal person responsible for personal data and their postal/contact details have not yet been confirmed. This information must be completed before public launch. Contact arrangements currently shown on the contact page also require ownership verification.

Information used by the service

The implementation uses sign-in identifiers and, where supplied by the provider, email details; usernames; preferences and timezones; posts; likes and reactions; tips and balances; purchases and payment references; friendship requests; unlocks; and activity statistics such as visits and wall-leading time. Hosting, authentication and payment providers may process network, device and security information for their services.

No dedicated advertising or analytics integration was identified in this code audit. This notice does not claim that provider logs, infrastructure data or an administrator’s systems have been exhaustively inspected.

Arcade and post visibility records

The arcade records a server-issued seed, current run identifier, start and expiry times, verified results, reward events and reward-window progress. Move lists are sent for verification but are not saved as run history. Runs expire after 30 minutes; starting another replaces the current run. Public game leaderboards show usernames, best verified scores and run durations for daily, weekly, monthly and yearly GMT periods. Period rollover starts a fresh board; it does not delete historical records. Account deletion removes that account’s leaderboard entries. A retention schedule for summary records, historical scores and reward events must be finalised before launch.

New wall posts have view tracking for the unseen-post achievement. The site records when a message has appeared at least half on screen for one visible second and stores the first recorded view from someone other than its signed-in author. The marker is public with the post; the feature does not store a separate visitor identity with it. This is a recorded display event, not proof that a person read the message. Unauthenticated visits can count, including an author viewing while signed out.

What other people can see

Wall posts, author usernames, selected name colours and badges, post scores and reaction/like totals are public. The leaderboard exposes public identity and ranking fields. A private profile document is restricted to its account owner by database rules. Public content can be copied, indexed or cached by others.

Why information is used

Account and activity data support sign-in, posts, tips, purchases, friendships, preferences and unlocks. Security and technical records support abuse prevention and troubleshooting. Contract may be appropriate for requested service features, legitimate interests for necessary security, and legal obligation for applicable records. The operator must confirm and document the lawful basis for each purpose before launch, including any processing involving children. Optional processing requiring consent must use a separate valid choice; using the site is not blanket consent.

Providers and international processing

The service uses Google Firebase for authentication, its London-region database and website hosting. Cloudflare Workers executes the server API for profiles, wallets, posts and verified game scores. Those requests include authentication tokens and normal connection metadata needed to verify and process them. Stripe processes payments when configured; sandbox checkouts do not take real payments. Their infrastructure can involve processing outside the UK. The actual locations, provider contracts and applicable international-transfer safeguards must be verified before launch; they are not established by the source code alone.

Some pages load fonts, SDKs or brand resources from Google or Wikimedia endpoints. The dedicated reward fonts are hosted locally. Their servers receive normal network requests when those resources are loaded. Contact opens your email software, so your chosen email provider also processes the message.

Cookies and local storage

See Cookies and local storage for sign-in persistence, the saved theme preference and static-file caching. We have not identified an advertising tracker in the application code. The operator must complete a deployed storage/cookie assessment and any required consent controls before adding optional tracking or enabling services that require consent.

How long information remains

Posts leaving the newest-ten feed remain in the database: the current code has no automatic post expiry. Account data generally remains until the account is deleted. The deletion flow removes the profile, sign-in account, authored posts, username reservations and reciprocal friendships. It does not currently remove every like, reaction or tip left on another person’s post. Purchase records and provider-held records may also remain.

A justified retention schedule, handling of residual identifiers, backups and legal/accounting records must be settled before launch. This draft does not invent a retention period or promise complete erasure. Contact the operator to request a review of remaining personal data.

Your data rights and complaints

Depending on the circumstances, you may request access, correction, erasure, restriction, portability or object to processing. Where processing relies on consent, you can withdraw it without changing the lawfulness of earlier processing. Use Contact; do not send passwords, full payment details or unnecessary identity documents.

You can complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint. The operator must establish an effective request and complaint handling process before launch.

Children and public access

The existing proposed account minimum is 13. That statement does not prove that children cannot view the public walls. A children’s access assessment, an appropriate age policy and any required safety/privacy measures are outstanding. The service must not claim that a 13-plus label alone satisfies those duties.

Security and changes

Database rules restrict private profile reads and direct changes to balances and server-owned statistics. These controls reduce risk but are not a guarantee against security incidents. Monitoring, incident response, backups and recovery still need operational verification. This notice should be updated when actual practices or required details change.