skip to content
DROIDHUBLIVE

Privacy policy

Last updated August 5, 2026

DroidHub Ltd (“DroidHub”, “we”) runs droidhub.live and the DroidHub Live mobile app. This policy explains what we collect when you watch robots, chat, message operators and take turns driving — and what we do with it.

What we collect

Account: your email address, display name, and a hashed password (we never store the password itself). Optionally a @handle, a bio, and either a preset pixel avatar or a photo you upload.

Preferences: interface language, colour theme and light/dark mode, so the app looks the same on every device you sign in on.

Activity: the channels and operators you follow, the streams you like, chat messages you post, direct messages you send, your place in a drive queue, and the turns you take at a robot's controls.

Credits and payments: your credit balance and a ledger of every change to it (top-ups, charges for turns, refunds, grants), plus a record of each purchase — the store, the pack, the amount charged and the provider's transaction id. Card and bank details go to the payment provider, never to us.

Technical: a session record with the IP address and browser or app user-agent that created it, so you can stay signed in and we can spot abuse.

Why we process it

To run the service you asked for — an account, a queue place, a working stream, a credit balance that adds up. This is processing necessary to perform our contract with you.

To keep the platform and the robots safe: rate limits, abuse detection, and enforcement of the community guidelines. This is our legitimate interest, and the robots' owners'.

To meet legal obligations, including keeping records of purchases for tax and accounting.

Streams, chat and driving are public

A live channel is public. Anything a robot's camera sees is broadcast to everyone watching, and messages you post in a channel's chat are visible to every viewer alongside your display name and avatar.

When you take a turn, your control inputs are relayed to the robot in real time and the fact that you took the turn is visible to the channel's operator and recorded in your credit ledger.

Direct messages are visible to you and the person you sent them to. They are not end-to-end encrypted — we can access them where we must, for example to investigate a report of abuse.

Who we share it with

We do not sell your data and we do not run advertising. We use a small set of processors to operate the service: Neon (the database), Vercel (hosting), Cloudflare R2 (avatar images), LiveKit (live video and the real-time control channel), Resend (transactional email), and RevenueCat with Google Play, the App Store or Stripe (payments).

Depending on the provider, data is processed in the EU or the United States under the transfer safeguards those providers offer.

We disclose data to authorities only where we are legally required to, and to a robot's operator where it is needed to investigate damage or misuse.

How long we keep it

Account data lives until you delete your account. Deleting an account removes your profile, follows, likes, direct messages and credit balance.

Chat messages and purchase records are kept after deletion where we need them — chat because it is part of another user's channel history, purchases because tax law requires it. Purchase records are stripped of the link to your account.

Session records expire on their own; stale ones are removed.

Your rights

You can access and correct most of your data directly in SETTINGS → EDIT PROFILE, and delete your account from the same screen — there is no undo.

For anything else — a copy of your data, an objection to processing, or a restriction — write to privacy@droidhub.live and we will answer within one month.

If you are in the UK or the EEA and you think we have handled your data badly, you can complain to your national data protection authority.

Children

DroidHub is not for children. You must be at least 13 to hold an account, or 16 where your country sets a higher age for consent to online services. If we learn an account belongs to someone younger, we close it.

Security

Passwords are hashed. Traffic runs over TLS. Broadcaster stream keys are encrypted at rest, so a database leak alone would not let someone take a channel over.

No system is perfect. If we ever suffer a breach that puts you at risk, we will tell you and the relevant regulator.

Changes and contact

If we change this policy in a way that matters, we will say so in the app before the change takes effect.

Questions: privacy@droidhub.live. General support: support@droidhub.live.