Privacy Policy
Last updated September 13, 2026
Ubitri collects only what it needs to run this website: the details you give us when you create an account or send us a message, a few cookies that keep you signed in, protect forms, and remember choices you make, and ordinary server logs. We count visits with our own analytics, which runs on our servers rather than anyone else's and sets a cookie only if you agree to one. If you buy a paid plan, our payment processor handles your card and we keep only the billing details needed to invoice you. We do not run advertising, we do not sell personal information, and we do not track you across other sites.
1. Who we are and what this policy covers
Ubitri, LLC ("Ubitri", "we", "us") is a Texas limited liability company. We provide software development, software services, IT consulting, and software products.
This policy explains how we handle personal information on www.ubitri.com (the "Site"), including accounts, the contact form, Secret Drop, File Drop, and any product beta we run. It applies to anyone who visits the Site. It also covers our analytics, described in section 2, on the other websites that use it.
Work we do for clients under a separate written agreement, such as a development project or a support contract, is covered by that agreement. Where the agreement and this policy differ, the agreement controls for that work.
2. Information we collect
Account information
When you create an account we ask for your full name, your email address, and a password. Your email address is also your username. We store your password only as a salted hash. We never see or store the password itself.
We also save your theme preference (system, light, or dark) to your account, and the time zone you choose to see dates and times in. To suggest a time zone, the Appearance page reads the one your browser reports; it reaches us only if you save it. We do not ask for a phone number, and we do not send a confirmation email to verify your address.
Passkeys
You can add a passkey to sign in with Windows Hello, Face ID, Touch ID, or your phone instead of a password. For each passkey we store its credential ID, its public key, a signature counter, the transports it supports, backup flags, the date it was created, and an optional name.
We never receive your fingerprint, your face scan, or the private key. Those stay on your device or with your passkey provider, such as Apple, Google, Microsoft, or a password manager, under that provider's terms.
Contact form
When you send us a message from the contact page we collect your name, your email address, your company (optional), the topic you chose, and your message. We also record the time we received it. If you were signed in, we record which account sent it.
Messages are stored in our database. They are not sent by email.
Billing information
If you buy a paid plan or we invoice you, we store the billing name, email address, and billing address you give at checkout, together with the type of payment method on file, its brand or bank name, and its last four digits. We also store the amounts, dates, line items, and status of every invoice. See section 5 for what happens to your card details, which is that they never reach us.
File Drop download records
When someone opens a File Drop link, enters a wrong password, or downloads a file, we record the time, the IP address and browser information of the request, and which link was used. We later work out an approximate city and country from the IP address using a location database kept on our own servers. The address is not sent to anyone to do this.
If the person who sent the files did so from a Ubitri account, they can see when each link was opened or used to download a file, which recipient's link it was, and the approximate city and country. They cannot see the IP address or the browser information.
Ubitri administrators can see the whole record, including the IP address and browser information, to investigate abuse and to answer questions about a transfer.
Technical information and logs
Like most websites, our servers keep standard logs. A log entry may include your IP address, the date and time, the page you requested, the page that referred you, your browser and operating system, the response status, and error details.
Our application also logs when an account is created (including the email address) and when a passkey sign-in or setup fails (including the account ID). To limit abuse, we count sign-in attempts per IP address in server memory for one minute at a time. Those counts are not written to the database.
Site analytics
We count visits to the Site with our own analytics, and so do some other websites that use it (see section 4). When a page loads, your browser sends our servers the address of the page, without anything after the "?" except campaign tags such as utm_source; the address of the website that linked you there, reduced to its domain; your screen width; and, when you leave or hide the page, how long it was in front of you and how quickly it loaded and responded to you. A page may also count something you did, such as pressing a sign-up button, or time something it did, such as a search, with a few details the page chooses. Nothing you type into a page is sent.
We keep your IP address with the record of each visit, and use it to work out your approximate country, state or region, and city. We do that either with a location database kept on our own servers, or by sending the address, and nothing else about you, to IPGeolocation.io, a location service. When we ask IPGeolocation.io, we remember its answer for that address for up to seven days, so the address is not sent again each time you visit. From the request we also work out your browser, operating system, and type of device. We do not keep your browser's full identification string, only what we work out from it.
Without a cookie, which is how everyone is counted, page views are grouped into visits by an anonymous code made from your IP address, your browser, and a random value that is replaced every day and then deleted, so the code itself cannot be followed from one day to the next. Because the IP address is kept with each visit, visits made from the same address on different days could still be matched to each other. Our reports do not do that: a return visit is recognised only for people who allow the cookie.
With a cookie, only if you choose "Allow" in the banner, we also store a random identifier in the ub_vid cookie. It lets us tell a return visit from a new one. Each website that uses our analytics sets its own, so the identifier is different on every website and cannot be used to follow you from one to another. It is not linked to your account, your name, or your email address.
If your browser sends a Global Privacy Control or Do Not Track signal, we do not show the banner and do not set the cookie unless you choose "Allow" yourself from Cookie settings.
Cookies
We set only the cookies listed in section 6. One of them, ub_vid, is used for analytics, and only if you agree. None of them is used for advertising.
Information we do not collect
We do not knowingly collect sensitive personal information such as Social Security numbers, government IDs, health information, precise location, biometric identifiers, or information about children. We never receive or store your full card number, its security code, your PIN, or your bank account credentials; those go directly to our payment processor, as section 5 explains. Please do not include sensitive information in a contact message.
3. How we use information
- To run your account: to sign you in, keep you signed in, apply your theme and time zone, and let you manage your passkeys and password.
- To answer you: we read contact messages and reply by email. Your company name and topic help us route the message to the right person.
- To run a product beta: if we offer early access to a product before its release, to decide who receives access and to tell you when your access is ready.
- To keep the Site secure: to lock accounts after repeated failed sign-ins, to limit sign-in attempts from one network, to protect forms against forgery, and to investigate errors and abuse.
- To improve the Site: to see which pages are read, how people find them, where they are visiting from, how fast pages load, and where people give up. We look at these as totals, not as a record of any one person.
- To bill you: to take payment for a paid plan, to issue and send invoices and receipts, to calculate any sales tax we must collect, and to contact you if a payment fails.
- To meet legal obligations and to establish or defend legal claims. Invoices and payment records are also kept because tax law requires it.
We do not use your information for advertising, profiling, or automated decisions that have legal or similarly significant effects on you.
4. How we share information
We do not sell personal information. We do not share it for targeted advertising. We share it only in these cases:
- Hosting provider. The Site and its database run on servers operated by a third-party hosting provider in the United States. The provider processes information on our behalf and under our instructions.
- IPGeolocation.io. To work out the approximate location of a visit our analytics counts, we may send the visit's IP address to IPGeolocation.io, as described in section 2. It receives the address and nothing else about you. See IPGeolocation.io's privacy policy.
- Stripe. If you buy a paid plan or we invoice you, Stripe processes the payment. Stripe receives your card or bank details directly from you, along with your billing name, email address, and billing address. See section 5 and Stripe's privacy policy.
- Passkey providers. If you use a passkey, your device or passkey provider handles the credential on your side. We only receive the public information described above.
- File Drop senders. If you open or download files sent to you through File Drop from a Ubitri account, the sender can see when you did so and your approximate city and country, as described in section 2. They do not see your IP address.
- Other websites that use our analytics. Our analytics also runs on other websites, including Ubitri's own products and other sites we provide it for. On those websites the information described in section 2 goes to our servers and is kept separately for each website. Whoever runs a website can see its totals, including countries, states, and cities, but not IP addresses. No one receives information about you as a person, and visits are never combined across websites.
- Legal requirements. We may disclose information when the law requires it, to respond to a valid legal request, or to protect the rights, safety, or property of Ubitri, our users, or others.
- Business transfers. If Ubitri is sold, merged, or reorganized, information may transfer to the new owner. We will still handle it under this policy unless you are told otherwise.
- At your direction. When you ask us to share something, for example to introduce you to a partner.
We do not use third-party analytics services, advertising networks, social media pixels, or chat widgets on the Site. Our analytics is our own and runs on our own servers. The only thing it may send anyone else is a visit's IP address, to IPGeolocation.io, to find its approximate location. Every script, stylesheet, image, and typeface on the Site's pages is served by the Site itself, so opening a page sends no request to anyone else. We do use a payment processor, Stripe, for paid plans and invoices; section 5 explains exactly what that involves.
5. Payments and billing
Paid plans and invoices are handled by Stripe, which is certified as a PCI DSS Level 1 service provider, the highest level of payment security certification.
Your card details never reach us
When you subscribe or change your payment details, we send your browser to a checkout page hosted by Stripe, on Stripe's own domain. You enter your card or bank details there, to Stripe. They are never typed into a page on this Site, never travel through our servers, and are never written to our database. We do not load any Stripe script on any page of this Site, so there is no payment form here for anything to be intercepted from.
What we do store
Stripe returns, and we keep:
- Identifiers for you as a Stripe customer, for your subscription, and for each invoice.
- The type of payment method on file (card or bank account), its brand or bank name, its last four digits, and for a card its expiry month and year. This is enough for us to show you which payment method will be charged. It is not enough for anyone to make a payment with.
- The billing name, email address, and billing address you gave Stripe at checkout. We need the address to issue a correct invoice and to work out any sales tax we must collect.
- The amounts, dates, line items, and status of each invoice.
We never receive or store your full card number, its security code, your PIN, or your bank account credentials.
Stripe's own role
Stripe handles the payment information you give it under its own terms and privacy policy, including for fraud prevention and to meet its legal obligations as a payment provider. See Stripe's privacy policy.
Invoices and receipts
We send your invoices and receipts ourselves, from Ubitri, with a PDF attached. Stripe's own customer emails are switched off, so you should receive one message from us per invoice rather than two from different senders.
6. Cookies
Cookies are small text files your browser stores. The Site sets these cookies and no others:
| Cookie | Purpose | Lifetime | Type |
|---|---|---|---|
| theme | Remembers your theme choice (system, light, or dark) so the page can apply it before it loads. | 1 year | Preference |
| org | If you belong to an organization, remembers whether you are working in your own account or the organization's, for plans and billing. | 1 year | Preference |
| ub_consent | Remembers whether you chose "Allow" or "No thanks" in the analytics banner, so it is not shown again. | 13 months | Preference |
| ub_vid | Set only if you choose "Allow". A random identifier that lets our analytics tell a return visit from a new one. Not linked to your account. | 13 months | Analytics, with your consent |
| .AspNetCore.Identity.Application | Keeps you signed in. | Until you close your browser. 14 days, extended on each visit, if you chose "Keep me signed in on this device" or signed in with a passkey. | Strictly necessary |
| Identity.TwoFactorUserId | Holds a sign-in that is part way done: between your password and your two-factor code, or while your browser completes a passkey step. | Up to 5 minutes | Strictly necessary |
| .AspNetCore.Antiforgery (with a random suffix) | Protects forms against cross-site request forgery. | Until you close your browser | Strictly necessary |
| .AspNetCore.Mvc.CookieTempDataProvider | Carries a one-time message, such as a confirmation that a change was saved, to the next page. | Until the message is shown | Strictly necessary |
| fd_ followed by a transfer ID | Remembers, for one File Drop transfer, that you entered its password and that your download has been counted, so you are not asked again or counted twice. Sent only to File Drop download pages. | 12 hours | Strictly necessary |
| ub_ticket | Remembers which support tickets you opened from a link in an email, so the link does not have to stay in your address bar. Sent only to support pages. | 30 days | Strictly necessary |
Apart from ub_vid, each of these cookies is either needed for something you asked the Site to do or remembers a choice you made. ub_vid is the only one used for analytics, and the Site sets it only after you choose "Allow" in the banner shown on your first visit. You can change your mind at any time from Cookie settings at the bottom of every page; choosing "No thanks" deletes it. No cookie is used for advertising, and no third party sets cookies on the Site.
You can block or delete cookies in your browser settings. If you block the strictly necessary ones, signing in, submitting forms, and opening File Drop or support links will not work. Deleting a preference cookie resets that choice: the theme goes back to "system", you return to your own account rather than an organization's, and the analytics banner asks again.
Stripe sets its own cookies on its checkout page during a payment. Because that page is on Stripe's domain rather than ours, those cookies belong to Stripe and are not set by this Site. They are covered by Stripe's privacy policy.
7. How long we keep information
- Account information is kept for as long as your account exists. When you ask us to delete your account, we delete it and its passkeys within a reasonable time, except for anything we must keep for legal, security, or dispute reasons.
- Passkeys are kept until you remove them or your account is deleted.
- Contact messages are kept for as long as we need them to handle your inquiry and for our business records. Ask us if you would like a message deleted sooner.
- Server and application logs are kept for a limited time for security and troubleshooting, then deleted or overwritten.
- Analytics records, including the IP address kept with each visit, are kept for 13 months and then deleted. The daily random value used to group visits without a cookie is deleted after one day.
- Billing records - invoices, amounts, and the billing details on them - are kept for at least seven years after the year they relate to, because tax and accounting law requires it. They survive the deletion of your account, and we cannot delete them on request. Stripe keeps its own copy under its own retention rules.
- Cookies expire as shown in the table above.
8. How we protect information
The Site uses HTTPS for every page, so information travels encrypted between your browser and our servers. Passwords are stored only as salted hashes, and we encourage passkeys, which cannot be phished or reused. Accounts lock for 10 minutes after 5 failed sign-in attempts, and sign-in requests are limited per network address. Forms carry antiforgery tokens.
Payment security is handled by keeping card details away from us entirely: they are entered on Stripe's own page and never reach our servers, so there is no card number in our database to expose. The credentials we use to talk to Stripe are encrypted before they are stored. Pages are served with a content security policy that restricts what code a browser will run on them.
No website can promise perfect security. If a breach affects your personal information, we will notify you as the law requires.
9. Your choices and rights
What you can do yourself
- Change your theme from the menu in the header or in Appearance.
- Add or remove passkeys, and change your password, in Security and passkeys.
- Allow or refuse the analytics cookie from Cookie settings at the bottom of any page.
- Sign out from the account menu, which ends the sign-in cookie.
- Block or delete cookies in your browser.
Rights you can ask us to honor
Wherever you live, you can ask us to:
- confirm whether we hold personal information about you and give you access to it;
- correct information that is wrong or out of date, such as your name or email address;
- delete your account, your contact messages, or other personal information;
- give you a copy of the information you provided in a portable format;
- opt out of the sale of personal information, targeted advertising, or profiling. We do none of these, so there is nothing to opt out of, but you may still ask.
Analytics records are not linked to your account, name, or email address, so we can only find yours by the IP address they were recorded from. To have them shown to you or deleted, tell us that address and roughly when you visited, and we will find and delete the visits recorded from it.
To make a request, send us a message from the contact page and choose the topic "Something else". To protect your account, we will verify that the request comes from the email address on the account, and we may ask a follow-up question before acting.
We will respond within 45 days. If we need more time we will tell you why and take up to 45 more days. If we decline a request, we will explain the reason. You can appeal by replying to our decision, and we will answer the appeal within 60 days. We will never treat you differently for exercising these rights.
Password reset by email is not available yet. If you cannot sign in, contact us from the email address on your account and we will help.
10. Children
The Site is for adults acting for themselves or for a business. You must be 18 or older to create an account. The Site is not directed to children under 13, and we do not knowingly collect information from them. If you believe a child has given us personal information, contact us and we will delete it.
11. Where information is processed
Ubitri is based in Texas, and the Site is hosted in the United States. If you visit from outside the United States, your information is transferred to and processed in the United States, where privacy laws may differ from those where you live.
12. Changes to this policy
We may update this policy as the Site changes. When we do, we will change the "Last updated" date at the top of this page. If a change materially affects how we handle your information, we will post a notice on the Site or email account holders before it takes effect.
13. How to contact us
Questions, requests, and complaints about privacy go through the contact page. Choose the topic "Something else" and we will reply by email. Our Terms of Service describe the rules for using the Site.