Privacy policy

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, and we measure how this website and the sign-in pages are used. We collect nothing else.

Sign-in and account

• You can create an account and sign in with Google, or with your email address and a password.
• With Google, we receive your name, your email address, your Google account identifier and whether that address is verified.
• To create an account with an email address, we send a single-use link that expires, to check that you can receive mail at that address. You then choose a password. We store your password only as a one-way hash. If you forget it, we email you a link to reset it.
• You can set up an authenticator app that gives you one-time codes, as a second sign-in step. We store the authenticator secret encrypted, and the recovery codes only as one-way hashes.
• We use these details to create and identify your account and to keep it secure. We also keep when the account was created and last changed, when you last signed in, whether the account is active, and a count of failed sign-in attempts with any temporary lockout that follows.
• Sign-in events are written to audit records that hold the event, your account identifier, a request id and the outcome. They do not hold your email address or your password.
• An account lets you sign in. Access to the studio during the beta also needs an invitation; without one, you can join the waitlist.

Session

• The studio keeps a server-side session, so that your browser stays signed in between visits.
• The session identifier travels in one cookie, which only the studio sets. The sign-in service at auth.userbus.com keeps its own server-side session the same way, in a cookie of its own.

Analytics

• This website and the sign-in pages load Google Tag Manager and Google Analytics. We use them to count visits, clicks on the buttons that open the studio, and completed sign-ups.
• Analytics cookies stay off until you allow them. Until you choose, and if you decline, Google Analytics receives only cookieless signals: the page, the event and the kind of browser, with no identifier that links one visit to the next. Like every request your browser makes, these signals reach Google with your IP address.
• If you allow them, Google Analytics sets its cookies and can tell your visits apart. We keep analytics data for 14 months.
• Google signals and advertising features are off, and we do not use analytics data for advertising.

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 your account details for as long as your account exists. They include your email address, any details received from Google, and any password hash or authenticator setup your account has.
• 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 and audit records. We keep the logs of requests to the service, and the audit records of sign-ins and other actions, that let us operate it, keep accounts secure 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.

These companies process data for UserBus.

Google

Sign-in and analytics. If you use Google sign-in, Google provides the account details listed above. Google Analytics measures visits and sign-ups as described 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.

SendGrid

Email. SendGrid, a Twilio company, processes your email address and the content of the emails we send you, to deliver account emails and service notices, such as sign-up links and password reset links.

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.

Session cookies that keep you signed in, one cookie that remembers your analytics choice, and analytics cookies only if you allow them.

• The studio sets the session cookie that keeps you signed in. Without it, you would sign in again on every visit.
• The sign-in service at auth.userbus.com sets its own session cookie, for the same purpose.
• This website and the sign-in pages set one cookie, userbus_analytics, which remembers your analytics choice for 180 days. Change the choice with “Cookie settings” at the foot of any page of this website.
• If you allow analytics, Google Analytics sets its cookies (_ga and _ga_ followed by an identifier) on userbus.com. If you decline, it sets none.
• We set no advertising cookies.
• You can block or clear cookies in your browser. If you block the session cookie, the studio 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.
• Passwords are stored only as one-way hashes, and authenticator secrets are stored encrypted.
• Card details are handled by Stripe. They never reach UserBus systems.

07 / TRANSFERS

International transfers.

Where your data can be processed.

Google, Stripe, Cloudflare and SendGrid 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.