UserBus

Overview / Privacy policy

PRIVACY POLICY

Privacy policy

This policy describes how UserBus handles personal data. It covers your account, the jobs you submit, the console you submit them from and this website.

Last updated 17 September 2026.

01 / WHAT WE COLLECT

What we collect and why.

We collect the data the service needs to sign you in, run your jobs and take payment for them. We collect nothing else.

Sign-in and account

  • Sign-in runs through Google. Google returns your name, your email address, your Google account identifier and whether that account is verified.
  • We use those four items to create your account, to identify it and to keep it secure.
  • An operator invitation is required before an account is created.

Session

  • The console keeps a server-side session, so that your browser stays signed in between visits.
  • The session identifier travels in one cookie. That cookie is the only cookie we set, and only the console sets it.

Prompts, job parameters and output

  • When you submit a job, we send your prompt and the job parameters to our backend and to the GPU worker that runs the job.
  • The prompt and the generated media are stored as artifacts in your account, and we serve them back to you.

Payments

  • Stripe processes payments for jobs. Card details go to Stripe and never reach UserBus.
  • We keep a billing record for every charge, credit and refund on your account.

The backend writes structured audit logs. An audit record holds a request id, your customer id, the action, the object and the outcome. It does not hold your sign-in details, and it does not hold the body of your prompt.

We do not sell personal data. We do not train models on your prompts or on your results, and that is a fact about how the service is built rather than a policy we choose to keep: the platform contains no training or fine-tuning component.

02 / RETENTION

How long we keep it.

We keep what we need to run and account for your jobs, and then we delete it.

  • Account details. We keep the account details Google sign-in gives us for as long as your account exists.
  • Your jobs. We keep the prompts, the parameters and the results of your jobs for as long as we need them to run the job, deliver the result and account for it.
  • Billing records. We keep the record of what a job cost so the books add up, including after an account ends.
  • Request logs. We keep the logs of requests to the service that let us operate it and investigate faults.
  • Deleting your account. You can ask us to delete your account and its results: write to support@userbus.com. We will action the request and confirm when it is done.

03 / PROCESSORS

Who processes data for us.

Three companies process data for UserBus, each for one purpose.

Google

Sign-in. Google confirms who you are and returns the account details listed above.

Stripe

Payments. Stripe charges the payment method you gave it and reports the result to us.

Cloudflare

Delivery. Cloudflare fronts the public UserBus hostnames and passes traffic to our servers.

Independent providers supply the compute that runs jobs. A job is executed on provider hardware, so the prompt and the job parameters reach the worker that runs it. Providers take on that work under contract with UserBus.

04 / COOKIES

Cookies.

One cookie, set by the console.

  • The console sets the session cookie that keeps you signed in. Without it, you would sign in again on every visit.
  • We set no advertising cookies and no analytics cookies.
  • This website sets no cookie at all. It is static pages and one stylesheet.
  • You can block or clear cookies in your browser. If you block the session cookie, the console treats every visit as a new sign-in.

05 / YOUR CHOICES

Your choices.

You can ask us to do any of the following, and we answer every request.

  • Access. Ask for a copy of the personal data we hold about you.
  • Deletion. Ask us to delete your account and its results: write to support@userbus.com. We will action the request and confirm when it is done.
  • Correction. Ask us to correct a name or an email address we hold for you.
  • Withdrawal of consent. Withdraw your consent to processing at any time. Withdrawal stops future processing. It does not undo processing that has already happened, and it does not remove records we have to keep, such as billing records.

Write to support@userbus.com for any of these, and we will confirm what we did.

06 / SECURITY

Security.

The controls that protect the data above.

  • Traffic to the public UserBus hostnames is encrypted in transit.
  • Access to production systems and to customer data follows least privilege. Each operator and each service holds the access its role needs and nothing more.
  • Secrets are kept out of logs. Application logs carry identifiers, not sign-in details and not prompt bodies.
  • Card details are handled by Stripe. They never reach UserBus systems.

07 / TRANSFERS

International transfers.

Where your data can be processed.

Google, Stripe and Cloudflare run infrastructure in many countries, so your data may be processed outside the country where you live. Each of those companies publishes the terms that cover those transfers, and we choose providers that publish them.

08 / CHILDREN

Children.

The service has an age limit.

The service is not for people under 18. We do not knowingly collect personal data from anyone under 18. If you believe that a person under 18 has used the service, write to support@userbus.com and we will delete the account and its artifacts.

09 / CHANGES

Changes to this policy.

How a change becomes visible.

We may change this policy. When we do, we publish the date of the change on this page, so the version you are reading always carries its own date.

10 / CONTACT

How to contact us.

Privacy questions have one address.

Write to support@userbus.com about this policy, about your personal data or about a request in the section above.