In short
- Si Novi Ltd makes Nubo and is responsible for your data.
- We hold what it takes to run your account and subscription: your email address, the devices you use Nubo on, and your subscription and payment history. We never see your card details.
- No advertising. We count visits to the website with Altino, the cookieless analytics we build ourselves. The only cookie keeps you signed in to your account page.
- Delete your account and most of it goes straight away. Billing records stay for 6 years, for tax.
Who we are
Nubo is made by Si Novi Ltd, company number 11370658, registered office 16 Blackfriars Street, Salford, M3 5BQ, England. Si Novi is the controller of the personal data described here, and is registered with the Information Commissioner's Office as ZA437640. In this notice, "we" and "us" mean Si Novi.
This notice covers the Nubo licence service (your account, sign-in and subscription) and this website. The Nubo app keeps your AWS credentials, connections and data on your own device, and they never reach us. The Si Novi privacy notice covers Si Novi's other work.
What we hold and why
A few things below are kept as a keyed hash: a one-way code made from the value and a secret key only the service holds. We can check whether a value we're given matches one, but nobody can turn it back into the value.
- Your account. Your email address, a random account id and licence id, and when you signed up. We need the address to sign you in and to send you sign-in codes and emails about your subscription. We keep the address itself (in lower case) on your account, and wherever we look you up by it, only as a keyed hash.
- Your devices. For each device you sign in on, its name, its platform (for example macOS or Windows), the app version, and when it was first and last used. For each computer, which counts towards the limit of 2, we also keep a one-way identifier the app makes on the device, so the same computer isn't counted twice. The app makes it from the id your operating system gives the computer (the hardware UUID on a Mac, the machine GUID on Windows, the machine id on Linux), hashed on the device, so that id itself never leaves it.
- Signing in. When you ask for a sign-in code, we keep your email address, the device asking, and keyed hashes of the code, for the 10 minutes the code works and about an hour after.
- Staying signed in. The app holds a credential and your account page a session cookie. We keep only a hash of each, with the account and device it belongs to, so a copy of our records can't be used to sign in.
- Your subscription. Its status and dates, the price and any discount, the amount, currency and date of each payment, any refund and where it stands, and the ids Paddle, Apple or Google give your subscription (and, for a web subscription, Paddle's customer id). Paddle, Apple or Google takes the payment, so we never see your card details.
- Checkouts. Each web checkout's status, price, whether a free trial applied, and a masked form of your email address (like m•••@e•••.com), so the page can show whose checkout it is.
- Free trials. Each person gets one free trial. To keep to that, we keep a keyed hash of the computer a trial was started on, and, when an account is deleted, a keyed hash of its email address. Neither names you or points to an account.
- Emails we send you. For each subscription email (a trial or renewal reminder, a cancellation confirmation, a beta notice) we keep what kind it was, when it went, the message id Amazon SES gave it, whether it was delivered or bounced, and a fingerprint of its content, as a record that we sent it. That record never holds your address.
- Keeping sign-in safe. To limit how often someone can ask for codes, we count requests against keyed hashes of the email address and of the IP address they came from, for between 10 minutes and a day. We don't store IP addresses.
- Service logs. What the service did and when, for finding faults and abuse. Logs name accounts by their random id, and never contain an email address or IP address except as a keyed hash. Sign-in codes, tokens and cookies are never logged.
- Support. When we help you, a record of what was done to your account, by whom and when.
- The beta. If you're in the beta, a record of your beta access. A beta tester who uses Nubo on an Apple device may be given a one-time App Store offer code, and we record which account it went to.
Why we're allowed to
- To provide what you've signed up for (performing our contract with you): your account, devices, sign-in, subscription and the emails about it.
- Because the law requires it: billing and refund records, which we keep for tax.
- For our legitimate interests: keeping sign-in safe, one free trial per person, service logs, a record of the emails we sent and the support we gave, and counting visits to the website.
How long we keep it
- Sign-in requests and codes: about an hour. A code itself works for 10 minutes.
- Account page sessions: 30 days, or until you sign out.
- App credentials: until you sign out, remove the device or delete your account. We then keep a record of the ended credential (the device's name and platform, and why it ended) for 30 days.
- Devices: until you remove the device or delete your account.
- Checkouts: 90 days after they last change.
- Sign-in limits: between 10 minutes and a day.
- Service logs: 3 months.
- Your account: until you delete it.
- Billing records (your subscription's history, payments and refunds, and the emails we sent about it): 6 years after your account is deleted, without your name or email address. A refund's record is kept for 6 years after it last changed.
- Free-trial markers (the keyed hashes of a trial's computer, and of a deleted account's email address): 6 years.
- Support records: while your account exists, then 6 years after it's deleted, cut down to who did what and when.
Our database keeps backups for up to 35 days, so something deleted can stay in a backup for that long.
Who else handles it
- Amazon Web Services runs the licence service for us in its London region: the database, the code, the signing keys and the email we send (Amazon SES). SES keeps its own list of addresses that bounced or marked our email as spam, so it stops sending to them. An address stays on that list until we take it off.
- Paddle sells web subscriptions as merchant of record. When you check out, we give Paddle your email address and your Nubo account id, and Paddle takes your payment details itself. To show prices in your currency, we send Paddle the country you're browsing from. Paddle keeps its own records as the seller, under Paddle's privacy notice, including after you delete your Nubo account.
- Apple sells App Store subscriptions. When you link one to your Nubo account, we tell Apple your Nubo account id (a random identifier, not your email address) and read the subscription's status from Apple. Apple's own privacy policy covers what it holds.
- Google sells Google Play subscriptions. When you subscribe in Nubo for Android, the app gives Google your Nubo account id (a random identifier, not your email address) with the purchase, and we read the subscription's status from Google. Google's own privacy policy covers what it holds.
We don't sell your data, and we don't use it for advertising.
The website and cookies
nubodb.com has no advertising. It sets one cookie, __Host-nubo_session, when you sign
in on your account page, and only to keep you signed in there. It lasts 30 days or until you sign out, and it's
strictly necessary, so it doesn't need your consent.
- The site is served through Amazon CloudFront, which answers from a location near you.
- Its fonts are served by nubodb.com itself, so no font service such as Google Fonts sees your visit.
- The pricing and checkout pages load Paddle's checkout, which runs under Paddle's privacy notice and may set its own cookies.
- The beta sign-up form on the home page sends your email address, and the platforms you pick, to Buttondown, which runs the beta mailing list for us as our processor, under Buttondown's privacy policy.
Analytics
To understand how the website is used, we run Altino (altino.dev), the cookieless analytics product we build and run ourselves. We use it to count visits and see which pages are read. It does not track you across other websites, and it is the only analytics on this site, so nothing here reports to a third party.
- Altino sets no cookies, writes nothing to local storage, and does not fingerprint your device. Nothing about your visit is saved on your device, so there is no banner to accept.
- What it measures: the page you visited (the path only, with any query string stripped), the referring site (its domain only, and only when it was not this site), your browser and device type, and an approximate location.
- That location comes from CloudFront, the content delivery network in front of the analytics endpoint. It works out a rough country and city at its nearest edge and passes them along as request headers. Your IP address is never looked up against a geolocation database.
- Your IP address is not stored. It is combined with your browser's user-agent string, the date and a secret key, then put through a one-way hash, and that result is what counts you as one visitor for the day. The secret key means nobody holding a known address and user agent can compute the same hash and check whether you visited. The date goes in too, so the value changes daily and can't be used to follow you from one day to the next. The record holding it deletes itself after 24 hours.
- What is kept is aggregate counts by page, day, country, city, browser and referrer. None of it identifies you.
- Altino honours the Do Not Track browser signal. Send the signal and this site records nothing through Altino.
- Our legal basis is our legitimate interest in understanding how our own website is used. Nothing is sold or shared with third parties.
Where it's kept
The licence service and its data are in the UK, in AWS's London region. CloudFront, Paddle, Apple, Google and Buttondown may handle data outside the UK. When they do, they rely on the UK's adequacy regulations (including the UK-US data bridge) or on the ICO's International Data Transfer Agreement or Addendum.
Deleting your account
You can delete your account in the app or on your account page, after we email you a confirmation code. The refund policy explains what happens to a subscription.
- Deleted straight away: your account and email address, your devices, your sessions, your checkouts, and anything waiting to be sent to you.
- Kept without your name or email address: your billing records and the record of emails we sent, for 6 years, and the support record.
- Kept for a while: the ended credentials for 30 days, the free-trial markers for 6 years, and service logs for 3 months. A change of email address that's waiting for you to confirm it lasts 72 hours, and goes with the account if you delete it first.
Paddle, Apple and Google keep their own records of a subscription you bought from them. An App Store offer code we gave you stays recorded as used, so it's never given out twice, but no longer says which account it went to; that record goes after 6 years.
Your rights
Under UK data protection law, you can ask us to:
- give you a copy of the personal data we hold about you
- correct it, for example a changed email address
- delete it, which you can also do yourself by deleting your account
- stop or limit using it, where we rely on our legitimate interests
- give you the data you gave us in a form you can take elsewhere
Email support@nubodb.com to ask. We may need to check it's you, and we'll answer within a month. If you're unhappy with how we've handled your data, you can complain to the Information Commissioner's Office at ico.org.uk.
Changes and contact
We'll update this notice when what we hold or who handles it changes, and change the date at the top. If a change matters to you, we'll email you before it applies.
Questions about your data: support@nubodb.com. Our subscription terms and refund policy cover the rest.