Buhata
Login Start for Free

Privacy Policy

Last updated: October 21, 2026

Buhata is a life-tracking app for your money, tasks, family, and health. This policy explains what information the app handles and where it goes. The short version: Buhata needs an account, your entries are written to your device first and then copied to our server so they reach your other devices, and there are no ads.

Who you are dealing with

Buhata is operated by Buhata LLC, a Florida limited liability company, document number L26000404649, of Pensacola, Florida, United States, whose full postal address is in the Terms. Buhata LLC decides what is collected and why, which under European law makes it the data controller. Write to [email protected] about anything in this policy.

This policy covers every version of Buhata: the Android app from Google Play, the iPhone, iPad and Mac apps from the App Store, the Windows desktop app, and the browser app at buhata.com. Where a platform differs, it says so.

Our representatives in Europe and the UK

Buhata LLC is in the United States and has no office in Europe or the United Kingdom, so we’ve appointed representatives in both under Article 27 of the GDPR. You can go to them instead of us about anything in this policy, and they’ll pass it on.

In the European Union: Instant EU GDPR Representative Ltd, Office 2, 12A Lower Main Street, Lucan, Co. Dublin, K78 X5P8, Ireland. Contact Adam Brogden at [email protected], or use the request page at buhatallc.gdprlocal.com/eu.

In the United Kingdom: GDPRLocal Ltd, 1st Floor Front Suite, 27-29 North Street, Brighton, England BN1 1EB. Contact Adam Brogden at [email protected], or use the request page at buhatallc.gdprlocal.com/uk.

Going to a representative doesn’t take away your right to complain to your own data protection authority. In the United Kingdom that’s the Information Commissioner’s Office, where Buhata LLC is registered under reference ZC231158.

Information stored on your device

Everything you enter in Buhata (financial entries, tasks, grocery lists, weight, water and mood logs, a workout schedule, journal entries, household profiles) is written to your device first, which is why the app keeps working with no connection. While you are signed in, a copy is also sent to our server, as described below.

Buhata Cloud account (required)

Buhata needs an account. While you are online and signed out, the welcome screen cannot be dismissed, and the only way to open the app without one is to start it with no connection at all. We store your email address, a hashed password (we cannot see the original), your display name, and a copy of your Buhata data so it can appear on your other devices. That copy is made automatically while you are signed in, and it covers everything you keep in the app, including financial and health entries. If you join a household, the parts a household shares are also visible to the members you approve. You can delete your account in the app, or ask us and we’ll do it, and your data is removed from our live systems at once. That includes your support history and your Restore Points, so support can’t bring a deleted account back. The only place it still sits is inside the encrypted backups of our whole database, which nobody can sign in to and which are never used to restore one account. We keep almost nothing that could recognize you if you signed up again, and the account deletion page lists the few exceptions.

Signing in with Google, Apple or Microsoft

You can sign in with an email address and a code, or with a Google, Apple or Microsoft account. If you choose one of those, that company tells us your email address, a permanent identifier for you at that company, and your name if they hold one. That is all we ask for. Apple also hands back a sign-in token, which we keep encrypted for one job: when you delete your account, we send it back to Apple so Apple ends Buhata’s access to your Apple ID, as Apple asks of every app that offers its sign-in. We never get your password, and we cannot see anything else in your account there: not your contacts, not your files, not your calendar.

We store the identifier so that signing in again recognizes you. Signing in this way tells that company you use Buhata, which is true of every service you sign into with them, and their own privacy policy governs what they do with that fact.

Apple lets you hide your real address and give Buhata a relay address instead. That works normally here. Everything still reaches you, and we never see the address behind it.

Voice commands and the command bar

The words come from the speech service your phone or browser provides, and Buhata never receives the sound itself. In Chrome and on most Android phones that service is Google’s, and it can send the recording to Google to be recognized. In Safari and on Apple devices it’s Apple’s, and in Microsoft Edge it’s Microsoft’s. Their own privacy policies cover what happens to the recording. Dictating a note uses the same speech service, and what you dictate is kept as the note you wrote.

Once the speech service has turned what you say into words, Buhata reads the sentence on the device itself, using a recognizer that learns the way you in particular talk: the words you use for things, the shops you name, the people you mention, the times you tend to mean. The longer you use it the more it handles alone, and a command it finishes there never reaches our server unless you mark it with a thumb, as described below.

A sentence the device cannot resolve is sent to our server. We check it against a list of common commands first, and on Premium one the list can’t answer is passed to Anthropic, a language model provider, to be turned into an instruction such as “add milk to groceries”. On the other plans it goes no further than our server. Apart from a command you mark with a thumb, described below, that’s the only time a spoken sentence reaches our server. Anthropic does not use it to train anything.

A command you type into the command bar goes the same way. Your device reads it first, and one it can’t resolve goes to our server, and on Premium to Anthropic, exactly as a spoken sentence would. It’s kept in the same short record of what was heard, described below.

Two different things are kept, and they are worth telling apart.

What Buhata remembers from a command is a shape, not a sentence. When a command is understood, Buhata stores the pattern it followed with the name and the amount replaced by blanks, filed under a one-way code built from your account and the words rather than the words themselves. Saying or typing something similar later is matched against that pattern and the real values are read from the new sentence. That store is permanent and it is also unreadable: nothing in it can be turned back into what you bought, from whom, or for how much.

A short record of what was heard is kept separately, against your account, and this one does contain the sentence, whether you said it or typed it. It exists so that mistakes can be found and the recognizer corrected, which is the only way voice gets better at the words you actually use. It is deleted automatically after 30 days, it is erased immediately if you delete your account, and it is never used to build an advertising profile or shown to anybody outside the small number of people who keep Buhata running. It is not displayed anywhere in the app; if you want yours cleared sooner, write to [email protected] and we will do it.

A command you mark with a thumb up or down is kept with the rest of your Buhata data, the sentence included, along with the reasons you pick and anything you type about it, so while you’re signed in it’s part of the copy on our server described above.

If the command was read by the AI model or came from your own saved phrases, pressing a thumb also sends your mark to our server straight away, with the sentence that was answered and the commands read from it, whether or not you tick anything. A thumbs up can save that reading as one of your phrases, and it counts toward that pattern being shared with everyone. A thumbs down removes the saved reading and keeps the command’s pattern, with the name and the amount blanked out, against your account until you’ve confirmed that kind of command twice or you delete your account.

If you also tick Allow Buhata to use this request to improve commands, the sentence, the reasons, which part of Buhata read it and the pattern it was read as are sent to us as a separate record, so the commands people mark wrong can be found and fixed, and your mark counts for or against that pattern being shared. What you typed about it isn’t part of that record. That record is deleted automatically after 90 days, it’s erased immediately if you delete your account, and only the small number of people who keep Buhata running can see it, without your name beside it.

Voice is always something you start by tapping the microphone. Buhata does not listen in the background and has no wake word.

Reading a photo (Premium)

On Premium you can photograph a receipt, a list, a wall calendar, a planner page or a note and have Buhata read it into items you then check. The picture goes to our server and on to Anthropic, whose AI model reads it and sends back what it found. Before it goes anywhere, it passes the same child-safety checks as a picture shared in a Space, described under who else touches your data. We don’t keep the picture. What stays is a line in the short record of what was heard, saying a photo was read and how many items came back, which is deleted after 30 days like the rest of that record, and whichever items you chose to keep. Anthropic doesn’t use the picture to train anything.

The Daily Brief

The Daily Brief’s opening line is written on your device from the day’s own counts, and nothing is sent for it. On Plus and Premium the Brief also has an overview, which Anthropic’s AI model writes when there’s enough in your day to say something. For that, our server sends it your first name and your day as numbers: how many entries you’ve made, your tasks that are open, late, due today or coming up in the next week, how long the oldest late one has waited, your open goals, your longest habit streak, your workout hours and this month’s spending against your budget. If you’ve connected a bank on Premium, it adds the month’s spending and income from the bank and the five shops and five categories you spent the most at, with their amounts. Opened inside a Space, it also sends what kind of Space it is and how many members it has, how many of its board’s tasks are open, late and unassigned, how many were finished this week and the week before, and how many threads it has. Inside a Team, each member’s first name and last initial goes with their count of open and finished tasks. Task titles, notes and the words in your entries aren’t sent. When there isn’t enough in your day to write about, a template writes the overview instead and nothing goes to Anthropic. The overview and the numbers it came from are kept with your account and deleted with it, and Anthropic doesn’t use them to train anything.

Weather and exchange rates

When the Weather tool fetches a forecast, a coarse position (from your browser prompt on the web, or estimated from your network connection) is used once per fetch to request a local forecast, and is not kept by Buhata. The only location Buhata keeps is the city and country each sign-in came from, which is a security record and is described under where your data is held. Currency features fetch public exchange rates from ExchangeRate-API, and the Android app asks Frankfurter when that one doesn’t answer. These requests retrieve data for you; they do not send your personal content anywhere.

Your profile in a Space

In a Household or a Team you can fill in a profile card for that Space: a picture, a banner, a short about-me, your pronouns, a status line, your local time and badges you’ve earned. Only your name is required and everything else starts empty. Each Space keeps its own card, and only the people in that Space can open it. Nobody can search for it anywhere in Buhata and it has no link of its own. Your email address and phone number aren’t on it unless you type them in yourself.

The badges you can show are the Winner’s Circle, the Ambassador badge and how many days in a row you’ve written in your journal or kept a habit. If you show a streak, the app sends us the number of days and nothing else, never the habit’s name or what you wrote. The Winner’s Circle and Ambassador badges only show while you’re on Plus or Premium, so showing one tells that Space you’re on a paid plan. Your plan itself only shows if you turn that on.

Anyone in the Space can report your card the way they’d report a message, and its moderators can hide your about-me, picture, banner, pronouns or status line. A hide goes in that Space’s moderation record and you’ll see what was hidden. Your picture and banner pass the same child-safety checks as a picture shared in a Space and are never at a public address. Leaving a Space deletes your card there, deleting your account deletes all of them with their pictures, and your cards are in your data export.

In a Household or a Team, Buhata keeps when you last opened each channel and thread, for you alone, so it can show you what’s new. Nobody else in the Space sees it, and it’s deleted with your account.

The daily drawing

If you enter the daily drawing and win, we keep your account id, the code that proves the win, and the date. That’s all, and it’s deleted with your account.

Your win only appears on the public Hall of Fame if you’ve turned that on. It’s off unless you switch it on, you can switch it back off whenever you like, and nothing about a win is published without it.

Age

Buhata is an adult service. You must be 18 or older to hold an account, and everyone in a household has their own adult sign-in. We don’t ask for a date of birth, we don’t record an age, and we don’t knowingly collect information from anyone under 18. A chore page shared by link opens in an ordinary web browser, asks for nothing, and stores nothing about whoever opens it beyond the task being ticked.

What we do keep is the confirmation itself. When you create an account you confirm you are 18 or older, and we store which version of the Terms you accepted and the date. That is two fields on your account, and it is included in your data export. We keep no age and no date of birth because storing one would mean collecting that information about people under 18 in order to prove none are here.

If you believe someone under 18 holds an account, write to [email protected] and we’ll remove it. If they are a member of a Space you run, reporting the member brings it to us the same way. Once we know, we close the account and delete its contents.

Who else touches your data

Buhata is a small company and runs on other companies’ infrastructure. These are all of them, and what each one gets:

Two things we want to be plain about, because a file you share at work is not a thing you expect to leave the company you shared it in. Every picture and document uploaded into a Space is sent for checking before it is shown to anyone, including files that turn out to be entirely ordinary, and there is no way to opt a Space out of it. Malware scanning happens too, on our own servers, and those files go nowhere.

Google, through Google Analytics, on the website only: it receives the page you viewed and a shortened form of your IP address, and it sets one cookie that tells pages of this site apart. In the European Union, the wider European Economic Area and the United Kingdom it waits for you to accept the cookie notice, and if you decline, nothing from Google is loaded; the cookies page says what happens elsewhere. It does not run inside the Buhata app. There is no advertising network on this list and no data broker, because Buhata uses none. If that ever changes, this list changes with it before the change ships.

Tasks in a Team

A task in a Team can be handed to more than one person, and the Team keeps a history of each of its tasks: who changed it, what they changed (its status, its priority, its due date, its board, the people on it or its name) and when. A line in that history keeps the change and never the words anybody typed. A task can also be made from a message in the Team’s room or a post on one of its boards, and it keeps a link to that message, so the message shows how the task stands. Comments on a task are posts in the Team and are kept, reported and removed the way every other post is. Everybody who can see a task’s board can see the people on it, its comments and its history, and nobody else in the Team can.

If you leave a Team, or are taken out of it, you come off every task in it, and the changes you made stay in its history under your name. If you delete your account, you come off every task in every Team, and your name comes off every line of history you made or were named in, which stays as a change by a former member. A Team’s admin can ask us for a copy of its tasks, the people on them and their history, the way Teams and your data describes. None of this goes to any company outside Buhata.

Invoices from a Team

A Team on Team X can invoice its clients through a Stripe account of its own. When it does, Buhata passes the client’s name and email address and the lines of the invoice to that Team’s Stripe account, so Stripe can send the invoice and take the payment. Stripe is the processor for these payments, and the client pays on Stripe’s own page, so Buhata never sees the card and never holds the money.

If you run the Team, we process your client’s details for your business and on its instructions. A business customer in the European Union, the wider European Economic Area or the United Kingdom has that covered by the Data Processing Addendum. If you’re the client, the Team that invoiced you decides what goes on the invoice, and questions about a charge go to them.

Buhata keeps its own copy of each invoice, which is who it’s to, its lines, its total and whether it’s been paid. That copy goes when the Team is deleted, and a client’s copies go when the client deletes their account. Stripe keeps its own record of every invoice for the period the law requires of it, and that carries on after a Team is deleted.

A Team’s clients and projects

A Team on Team X can keep a short record about each client it has approved: the company they work for, its website, where they stand in the Team’s pipeline, and which member looks after them. Only the people in that Team who can manage it see these records. Nothing is added to a record from an inbox, a calendar or anywhere outside the Team. The last activity shown beside a client is worked out each time it’s shown, from the Team’s own requests, the notes on them, its invoices and its tasks, and it isn’t stored.

A Team can also gather tasks from any of its boards into a project, and a project can be for one of its clients. The people who can manage the Team see every project. Anyone else in it sees a project that has no tasks yet, one they made, and any project holding a task their own boards let them open. Inside a project, each person sees only the tasks their own boards let them open, and only the people who can see the Team’s clients see which client it’s for. Making, renaming, archiving and deleting a project, and each change to a client’s record, are written to the Team’s audit trail.

If you run the Team, we keep these records for your business and on its instructions, as with invoices. A client’s record goes when they leave the Team or the Team removes them, when the Team is deleted, and when the client deletes their account. A member who leaves the Team stops being named as the one looking after a client. Your data export includes what each Team keeps about you as its client.

Connecting a bank

Bank connections are part of Buhata Premium. Nothing here applies unless you’re on Premium and choose to connect an account.

Buhata reads. It never moves money. There is no way to send a payment, make a transfer or touch a balance from inside Buhata, and there is no plan to add one. The connection is one-way and read-only.

What we ask your bank for, through Plaid:

What we do not ask for: your identity documents, your account and routing numbers, your investments, or anything that would let money leave your account.

Your bank login never reaches Buhata. You type it on Plaid’s own screen. What Buhata stores is a token that lets us read the accounts you chose, and that token stays on our server and never goes to your phone or your browser.

You can disconnect a bank at any time from the app, which removes the connection and the transactions we read from it. If Premium ends, whether you cancel it, move to Plus, a trial runs out or it isn’t renewed, the bank connections, balances and transactions it read are deleted when its paid period ends, and what you typed in yourself stays. Deleting your Buhata account removes all of it as well, along with everything else, as described below.

Bank connections have no fixed limit, and each institution you connect adds one Space to your plan. The connection is billed to us per bank login, so connections are meant for personal and household use and is covered by the fair use and permitted use terms; use far outside what a household plausibly needs is what those terms exist for, and we will contact you before anything is ever restricted.

Bank connections work with banks in the United States and Canada only. If your bank is somewhere else, it can’t be connected, and the rest of Premium works the same.

Where your data is held, and for how long

Buhata runs on servers in the United States. If you are in the United Kingdom, the European Economic Area or anywhere else with its own rules about data leaving the country, using Buhata means your information is handled in the United States, by us and by the companies listed above. For people in the European Economic Area and the United Kingdom, that transfer rests on the Standard Contractual Clauses in each company's agreement with us, with the UK addendum, and several of them also hold the EU-US Data Privacy Framework certification with its UK extension. Our representatives, named above, can give you a copy of the clauses on request.

How long things are kept:

Your rights over your information

Wherever you live, you can do all of the following, and you do not have to give a reason:

If you are in Europe or the United Kingdom, the lawful bases we rely on are simple ones: performing the contract you entered into when you signed up, which covers running the app, and our legitimate interest in keeping it secure and working. Voice commands are optional and you turn them on yourself. You may complain to your national data protection authority, and in the United Kingdom that is the Information Commissioner’s Office.

If you are in California, you have the right to know what is collected, to have it deleted, to correct it, and not to be discriminated against for asking. In the 12 months before October 20, 2026, Buhata didn’t sell personal information or share it for cross-context behavioral advertising, and on that date it did neither, so there’s no opt-out to offer. If that changes, this policy will say so before it happens, along with how to opt out. Global Privacy Control already switches Google Analytics off on this website, as the cookies page says.

Deleting your account

You can delete your account and everything in it from inside the app. Deletion happens straight away, with no waiting period and nothing to cancel afterwards. Everything personal goes: your data, its Restore Points and anything you wrote to support, so support can’t bring a deleted account back. What stays is what we’re required to keep for tax, whatever other people made for themselves, a record of what our own staff did without anything they wrote about you, and a copy inside the encrypted backups of our whole database, which nobody can sign in to and which are never used to restore one account. Account Deletion explains exactly what goes and what we must keep.

One narrow exception exists, and only for accounts that took a one-time offer: the free trial, the free month, or a place in the referral program. Deleting an account and making a new one would otherwise be a way to take the same offer twice, so a small record is kept: a one-way hash of your email address and, where there was one, the reference your card issuer gives us, along with the date and a short reason. No name, no address, nothing you wrote, and nothing that can be turned back into your email or your card. It is kept for two years and then deleted automatically.

A second narrow exception exists for the Buhata Student program, and it works the same way. One student discount is allowed per school email address, ever, so when a .edu address is verified we keep a one-way cryptographic token of it. If the account is later deleted, everything readable goes, including the address itself, and only that token remains. It cannot be turned back into the address and it answers a single question: has this school email already been used for a Buhata Student offer. It is kept for as long as the student program exists, because deleting it would make every deleted account a fresh claim on the same discount. Your verified student email, the school domain, and the verification dates are visible to you in your account and to our support staff while your account exists, and they are deleted with it.

The record kept for a one-time offer stops a new account at the same email address from taking the free trial, the free month or the Buhata Student discount, or from earning or triggering a referral reward. Nobody can verify that address as a school address for the Buhata Student discount either. That holds for each of those offers, even one the deleted account never took. Where the record keeps a card reference, that card can’t trigger a referral reward. It does not stop you registering, signing in, paying or using any part of Buhata, and it is never used for marketing, for recognizing you, or for anything else. If you think it should not apply to you, write to us and a person will look at it.

Buhata is an adult service, as the Age section above sets out. We don’t knowingly collect personal information from anyone under 18, and the app asks for no date of birth and records no age.

Invite links and keeping the referral program honest

Referral rewards are worth real money, so people try to farm them: one person making several accounts, or a household passing one subscription between its members. To catch that without asking anything extra of you, two values are worked out from the ordinary web request your browser or the app already sends, and only when you either arrive through somebody’s invite link or open your own invite screen.

The two values are a rough signature of the browser, being the user agent and the languages it accepts, and the network address the request came from. Both are put through a one-way hash with a secret key before anything is written down, so the address itself and the browser details are never stored. What is stored cannot be turned back into either one. It can only be compared with another stored value to answer one question: do these two signups look like they came from the same place. Those records are deleted after 180 days, and they are deleted immediately if you delete your account.

No advertising identifier is read. Nothing is asked of your phone, no identifier is kept on your device for this, and none of it follows you to any other app or website. It is used for one thing, deciding whether a referral reward is genuine, and it is shared with nobody. A match is never on its own a reason to refuse anybody: households share a network, families share a laptop, and a referral that looks unusual is held for a person to look at rather than rejected by a machine.

What we never do

How the site and the apps are protected

Buhata sits behind Cloudflare, which filters traffic before it reaches us. That means attacks are turned away at the edge, unusual bursts of requests are slowed down, and a browser is occasionally asked to prove it is a browser. Those checks look at the request rather than at you: an address, a rate, a pattern.

Every page is sent over HTTPS and nothing else is accepted. The browser is told, in the response itself, not to guess at file types, not to let another site frame Buhata, not to hand a full address to anybody you click through to, and to refuse any attempt by a page to reach your location, microphone, camera or payment methods. None of those are things Buhata’s website needs.

We use Cloudflare’s own counts of page visits, and, from September 2026, Google Analytics on this website. In the European Union, the wider European Economic Area and the United Kingdom it runs only after you accept the cookie notice, and if you decline, nothing from Google is loaded; elsewhere it runs by default unless your browser sends Global Privacy Control or Do Not Track, and the cookies page says how to turn it off. There is no advertising network, no session recorder, and nothing that follows you between sites. What we get is which pages were opened and roughly how people move between them, not who they were.

Security

Cloud traffic is encrypted in transit (HTTPS). Passwords are stored only as salted hashes. Our servers sit behind network-level protection and access to them is limited to the operator of Buhata.

If you have found a security problem in Buhata, the security page says where to send it and what happens next.

Employee access

Buhata employees and contractors can view account details to answer support requests: your email address, your plan, the devices signed in to your account with the city and country each one signed in from, when your data last synced and how large it is, and your payment status. They cannot open the contents of your apps, which includes your notes, money entries, health records and medication lists. That sign-in city is the only location Buhata keeps. Support may be handled by a contractor working outside your country, under a written confidentiality agreement.

If you apply for a job

Applying through our careers page sends us your name, your email address, the country you’re in, any links you give us, your answers to the role’s questions, and your CV if you attach one. We use it to consider the application and for nothing else.

We keep an application for a year and then it deletes itself, the file along with the record. If you’d rather it went sooner, write to [email protected] and we’ll remove it.

Marketing email

There is none. Buhata doesn’t run a mailing list and doesn’t send product news or offers to anyone, and there’s no setting that opts you into them: the one that used to exist went when promotions left the product. Email about your own account still sends, such as a sign-in code, a receipt, a renewal notice, a security alert or a change to these policies, because it’s part of the service.

The Sunday digest is the one email you choose to get, a weekly list of what’s due, what renews and whose birthday it is. It’s off until you switch it on, and it only sends while your plan includes it. Each one has a link at the foot that stops it, your mail app’s own Unsubscribe button stops it in one click, and you can switch it off in the app under Settings, then Notifications, on any plan.

Your choices

Health and fitness information

Weight, water, mood and workout entries are treated as consumer health data under the laws of several US states, and they have their own policy: the Consumer Health Data Privacy Policy. It covers what we hold, why, who sees it and how to remove it. The app asks for your explicit consent before the first of these entries is kept, records the date and the wording version, and lets you withdraw in Settings, which deletes them. Buhata has no menstrual, fertility, pregnancy, symptom, medication or diagnosis tracking of any kind.

If you are in a US state with its own privacy law

Several states give residents rights over sensitive personal information, which in our case means health and fitness entries and nothing else. Whichever state you are in, our position is the same one and we apply it to everybody rather than by residence:

Residents of California, Virginia, Colorado, Connecticut, Oregon, Texas, Montana and other states with comparable laws can exercise the rights described above by writing to [email protected]. We will answer within 45 days, we will not charge you, and we will not treat you differently for asking. If we refuse a request you may appeal to the same address, and if we refuse the appeal we will tell you how to complain to your state attorney general.

If something goes wrong

If personal information is exposed in a way that puts you at risk, we will tell you. We will notify affected people without undue delay once we understand what happened, and we will say what was involved, what we have done, and what you should do. Where the law requires it, we notify regulators too, which in the European Union and the United Kingdom means within 72 hours of becoming aware.

We would rather tell you early and be wrong about the scale than wait until the picture is perfect. Security reports from researchers go to [email protected], and how we handle them is on the Security page.

Complaints, and who to go to

If you are unhappy with how we have handled your information or answered a request, write to [email protected] and say so plainly. We will look at it ourselves and answer in writing within 45 days. If we got it wrong we will say so and fix it.

You never have to come to us first, and coming to us does not use up any other route. You can complain directly to your own data protection authority, to the Information Commissioner’s Office in the United Kingdom, or to your state attorney general in the United States.

For matters under the European Union’s Digital Services Act, including notices about content, our point of contact is [email protected], and it accepts correspondence in English. Legal process and preservation requests are covered on the Law Enforcement Guidelines page.

Contact

Questions or requests: [email protected].

Buhata LLC, United States. Our full postal address is in the Terms.

If Buhata changes hands

If Buhata LLC merges with another company, is bought, or sells all or part of its business, the information it holds about you can pass to whoever takes the business on. They’re bound by this policy for everything collected under it, and if they want a different policy to apply, you’ll be told before it does.

Changes

If this policy changes in a way that matters, we’ll say so in the app’s release notes and update the date above.