Privacy policy

Utah Aura LLC, a Utah limited liability company, runs Utah Aura. For anything about your information, write to info@utahaura.com.

• Your account. Your email address and, when you sign in with Google, the name and photo Google shares. Your display name starts as that name or, when you sign in with an email link, as the part of your email address before the @. What you add yourself: a display name, a handle, a photo and a city. There are no passwords: sign-in is by a link we email you or by Google.
• What you do here. The events you save; the practices and centers you follow (only you and each one's team can see that you follow it); your RSVPs, how many guests you bring, and for each guest the name and email you give and whether they are under 18; your orders (the tickets, the date, the amount, and Stripe's reference numbers; never your card number or its last digits, which stay with Stripe); the name and email you give for each ticket, including a guest's, and whether it's for someone under 18; refunds and refund requests; check-ins at the door; the hosts you ask to join; the groups you're in, are added to, ask to join or say no thanks to, and the Private events whose guest lists you're on or ask to be added to, with any note you write, and the ones you say you can't go to; the chats you're in, with the messages you write, the photos you send, how far you've read, and the chats you pin, mute, archive or delete; the requests you accept or delete, and the people and hosts you block; the people you follow or ask to follow, who follows you or asks to, whether your account is private, and the name you use in group chats; and any report you send us, with the messages it copies. A photo you send in a chat is kept as the picture alone: the place, the camera and the time your phone recorded with it are taken out first.
• What you sign. When a host asks you to sign one of its own documents, such as a waiver or a consent form, you sign by typing your full name and ticking that you agree. If you run a practice, you sign a center's policy for practitioners the same way. With each signature we keep:
  • the name you type and, when you sign for someone under 18, the name you type for them;
  • the agreement line you ticked, and which document and version you signed, with a fingerprint of its exact words: a code made from those words alone, which any change to them would change;
  • the date and time, to the second, and how you signed: as you booked, from a pass, at checkout, at the door or for your practice;
  • the IP address the signature came from, and the browser or app you used;
  • what it was for: for an event, the event and date, the order when you sign at checkout, and, when you sign for a pass rather than for your own account, that pass with the name and email on it (on a pass for someone under 18, their name, not yours); for your practice, the partnership;
  • if you were signed in, your account, its email and whether that email is confirmed, whether the account was made with Google or an email link, and the name on your profile then;
  • at the door, who on the team running it handed you their phone or showed you the code and, when you scan a code, the IP address and browser or app of the door's phone that showed it;
  • and where we emailed your copy, and when, or why it didn't send.

  We keep no drawn signature, no photo ID and no answers to questions, because signing asks for none of them. Away from the door, a host's team can open your pass, but being on the team doesn't let anyone sign from it. Signing from a pass takes one of three things: the account it belongs to; the link in that pass's own email, or the one the person who booked sends you; or, for a pass marked under 18, the account of the person who booked, signing as parent or guardian.

  When you buy tickets, what you type in the waiver part of the checkout, with any names you type for someone under 18, is held with your order until the payment goes through, along with the IP address and browser or app you used. The host's team can see it while it is held. If the payment doesn't go through, it is dropped within about a day. If your signature doesn't save after you pay, it stays with the order, where the host's team can still see it, until we save it.

• If you host. Your practice, center or collective's details, photos and address; the events and services you publish; the documents you ask people to sign, with every version, and the signatures they collect; the id and status of your Stripe account (Stripe holds the rest: your identity, your bank details); your payouts; your page's chats, with which of your owners and teammates wrote each of its messages, and the people it blocks; and the emails the site sends for you. When you run a door, your name goes on each signature you take there, with your phone's IP address and browser or app, and the event's host sees it.
• Technical. Our hosting and database providers keep request logs, with IP addresses, for a short time to keep the site running and safe. Our sign-in provider keeps the IP address and browser or app of each signed-in session until you sign out or delete your account. We count requests by IP address for a day or two to slow down abuse. Beyond these, we keep an IP address only with a signature, as above, and, at a door, for about a day, the IP address of the team's phone with each signing code it shows. If we turn on Google Analytics, it counts visits and pages in aggregate; we do not use it to identify you.
• Cookies. The cookies that keep you signed in; one that remembers where to send you after signing in; one that remembers whether the left bar is open; one that remembers which of your pages you are acting as; two that, when you tap Follow before signing in, remember which host for up to half an hour, so the follow finishes after you sign in; and two that Stripe, our payments provider, sets on event pages and when you pay, to help stop fraud. Your light or dark choice is kept in your browser's storage. No advertising cookies, and no tracking across other sites.

• To run your account and sign you in.
• To hold your place, issue your passes, and check them at the door.
• To keep the documents a host asks you to sign, with your signature and the exact words you signed, for you and the host, so that either of you can show what was agreed, and so that we can answer a claim or a legal request it may matter to.
• To send the emails you would expect: sign-in links, your passes (with a link to sign, when a host asks for a signature), a copy of what you sign (when we have an address for it), a reminder the day before a date when a signature is still missing (for your own place, for a place you booked for someone under 18 with no email of their own, or for a ticket you bought and left without a name), a refund, a moved or cancelled date, a host's yes when you ask to join its team or one of its groups, a note when a host adds you to its team or to one of its Public groups, new events from the hosts you follow, and a host's notices about an event you joined. A Private event's guest list sends no email: being added, or let in after asking, shows only in your account.
• To let the host of an event you joined see who is coming and who has signed, and a host see who is in its groups and on its guest lists.
• To deliver your messages and photos to the people in each chat.
• To pay hosts, handle refunds, and keep records of payments.
• To keep the site safe: to act on reports, and to find and stop abuse.
• To answer you when you write to us.

• Hosts. For each event you join, its host sees your name and photo, your email, your guests, what kind of ticket you hold, whether you checked in, and any refund request you send, with its note. When the event asks you to sign one of the host's documents, its owners, and the teammates they allow to see who's coming, also see whether you and your guests have signed, which version and when, whether a parent or guardian signed, and whether a guest is marked under 18. They can also open each signature's whole record, as What you sign lists it, including the IP address and browser or app it came from and the email you signed in with. If you were on the host's team when you signed, only its owners see that email and where your copy went, and only while you are still on the team and its page is open. In its groups and on its guest lists, it sees your name and photo, any note you write when you ask to join or to be added, whether you said no thanks when it added you to a group, and whether you said you can't go. Its owners also see the email address you sign in with if you are on its team or ask to join it through its team link; you can take back your ask while it waits or after a no, and then they no longer see it. While you are on a host's team, the RSVPs you make to its events show the team your name, not your email; a ticket you buy for one of them still shows your email, as anyone's does. If you sign a center's policy for practitioners for your practice, that center's owners, and the teammates they allow to see who's coming, see that signature's whole record the same way, without your email, and those on your practice's team who answer for its centers see that you signed, the name you typed and when. When you write to a host, its owners and the teammates it allows to read its chats read your messages and photos and see how far you've read theirs; in the chats it makes for its events and groups they read everything written there and see who is in them. If you write for a host, the others on its team who read its chats see which of its messages you wrote, and so do we in a report's copy. Beyond your profile, which anyone can see (see Other people), whether you follow it and since when, and the record of what you sign, a host sees nothing else about you, and the Host terms limit what they may do with your details from its events, groups and guest lists, and with what you write to it, and let them use your signature only as their record of what was agreed.
• The venue or the practitioner. When an event is held at a center, or led by a practitioner its host works with, the host may let that center or practitioner check people in at the door. They then see the names on that date's door list, what kind of pass each person holds, whether they checked in, whether each person has signed the host's documents, and, for someone under 18 who still has to sign, that a parent or guardian signs for them. When you sign at their door, the signature goes to the event's host, with the name of whoever on their team handed you the phone or showed you the code. They never see your email or your payment, and can't look up your signature afterwards, even one you typed on their phone.
• Other people. A host's page is Public, open to everyone, or Unlisted: then it opens only for people with its link and for the people connected to it. Your profile can be seen by anyone: your display name, handle, photo and city, when you joined and when you first and last saved it, and whether you show your name on your pages. The site shows it only where you appear, for example as a member of a host's team, or to the other people in a group that lets its members see each other. Your email address is not part of it, but if you sign in with an email link, your display name starts as the part of your email address before the @, until you change it in Settings. On the site, the person who booked your place sees whether you have signed, and whether a parent or guardian signed for you, but not the name you typed. If you sign without signing in, though, your copy, with the name you typed and the words you signed, goes to the address on your pass, when it has one. The person who booked gave that address, so it may be theirs; on a ticket with no address of its own, it is always theirs. Anyone holding your pass's link, the host's team included, sees on the pass whether the host's documents have been signed, which version, on what day and whether by a parent or guardian, and can read their words. On a pass marked under 18 that still has to be signed, it says a parent or guardian signs for its holder. A host's documents can be read by anyone who can open an event that asks for them.
• Who's going. On a Public event whose host shows who's going, anyone who opens it, signed in or not, sees how many people are going and the photos of the people who left “Show my photo here” on when they RSVP'd or bought tickets, or their initials when they have no photo. The switch starts where you left it last time, on until you first turn it off, and you can turn it off for a date at any time on its event page. Your name, email and guests are never shown there; your guests are only counted. The photo is the one on your profile, which anyone can see, so someone could match it to your display name. RSVPs and tickets from before the switch existed stay hidden until you turn it on. It never applies to an Unlisted or Private event.
• Utah Aura itself. The people who run Utah Aura look at a signature only when you or the host asks us to, to keep the site running and safe, to answer a claim or a legal request it may matter to, or where the law requires. They look at the email you signed in with, which is kept with it, only to help you, for security, or where the law requires, apart from the two cases that follow. A page we run ourselves, such as one we set up for a host before handing it over, has us on its team, so we see its signatures, that email included, as its team does. When a host can't download its own signatures, because there are too many for one download or its page is closed, we send it the file its team could download. If someone makes a claim against us, we may also share a signature with our lawyers and our insurer, and with the court; the email you signed in with goes with it only where the law requires.
• Chats. In the app you can write to people and hosts. A chat is read by the people in it at the time, and at Utah Aura only as Security says: in a chat with one person, the two of you; with a host, you and its owners and the teammates it allows to read its chats, including ones it adds later, who read what was written before; in a chat a host makes for an event's date or for a group, and in a group chat of your own, everyone in it. Direct chats use your account name and profile photo. Group chats use the one name you choose for group chats, with your photo shown only where you choose to show it, and never your photo on an event whose going list you hid it from; a member's card there doesn't link to their account or offer Follow or Message. You're in an event's chat only once you tap Join the chat, and whoever joins later can read what was said before. In a group with a chat every member is in it unless they leave it, and someone who joins the group later reads it from when they joined; in a group chat of your own, you read from when you last accepted an invitation. In a chat with one person or one host, each of you sees how far the other has read, once any request is accepted. A chat's photos open only for the people in it at the time, but anyone who has seen a message or a photo may have kept a copy. Who can start a chat with you: a host you have an RSVP or a ticket with, or paid for tickets to and weren't refunded in full, for a date ahead or in the last 12 months, or whose group you're in or asking to join, or that you follow; people on a page's team with you; friends, people you follow who follow you back; and, unless your account is private, anyone else, whose first messages wait in your Requests until you accept. If your account is private, it doesn't show when people search by name, people ask before following you, and apart from the hosts and teammates above, only friends can write to you, and people you let follow you can ask. Only the two of you see that one follows the other. Nobody can find you by your email address.
• Providers who work for us. Supabase (the database and sign-in), Stripe (payments; your card details go straight to Stripe and never pass through our servers), Resend (email, including the copies of what you sign), Vercel (hosting), and Google (sign in with Google, and analytics if we turn it on). To place an event on the map we look up its public street address with the US Census Bureau's geocoder, and when a host types an address, Google suggests matches. Each holds only what it needs for its job, under its own terms.
• The law. When a law, a court or a valid request requires it, or to protect someone's safety.

We do not sell your information, and we show no advertising.

• What Google user data we access. When you choose Continue with Google, Google's sign-in service gives us your name, your email address, a link to your Google profile photo, and an id for your Google account. That is all. We ask for no Gmail, contacts, calendar, Drive or any other Google data, and we will not ask Google for more without updating this page first.
• How we use it. Your email address signs you in and is where we send our emails to you. The host of an event you join sees it, and so do a host's owners when you are on its team or ask to join it through its team link, as described under Who sees it. When you sign a host's document while signed in, we keep your email address with the signature, along with the name on your profile at the time and the fact that your account was made with Google, as the record of which account signed. The host sees them, as Who sees it says. The account id lets us recognize you the next time you sign in. Your name becomes the starting display name on your profile, which you can change at any time. The photo link is kept with your sign-in record and not shown anywhere on the site. Nothing else is done with it.
• How we store it, and for how long. In your sign-in record with Supabase, our database and sign-in provider, on servers in the United States, for as long as your account exists. Deleting your account deletes it, except what is kept with anything you signed, which stays as How long we keep it says. To delete your account, use Delete account in Settings, or ask at the address below. Stripe keeps the copy of your email address it received, and Resend the emails we sent you, under their own terms.
• Who we share it with. We never sell Google user data, use it for advertising, or use it to train artificial intelligence models. It reaches Supabase to run sign-in; your email address also reaches Resend, which delivers our emails, and Stripe when you pay or when you set up payouts for a page with no contact email; anyone else gets it only where the law requires it. A host sees the name and email you give when you join one of their events. When you sign one of their documents while signed in, they also see the email you were signed in with, the name on your profile then and that your account was made with Google, as Who sees it says. A host's owners see your email address when you are on its team or ask to join it through its team link, as described under Who sees it. A host never sees anything else from your Google account.
• How we protect it. It travels encrypted, and it is stored encrypted by Supabase under its own security program. Who can read which row of the database is decided by policy in the database itself, not only by the app. The people who run Utah Aura look at a sign-in record, or at the email kept with anything you signed, only to help you, for security, or where the law requires, and at the rest of a signature only as Who sees it says. There are two exceptions: on a page we run ourselves, we are its team and see what its team sees, as Who sees it says; and when a host can't download its own signatures, we send it the file its team could download.
• Turning it off. You can remove Utah Aura's access at any time on your Google Account's third-party connections page. You can then still sign in with a link by email. To have the information itself deleted, write to us at the address below; what is kept with anything you signed stays, as How long we keep it says.

Utah Aura's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain words: Google user data is used only to sign you in and to run the features you see on the site. It is never used for advertising, never sold or passed to data brokers, never used to decide creditworthiness or for lending, and never used to train artificial intelligence or machine learning models.

We send only the emails about your account, your places and your tickets, among them a copy of what you sign (when we have an address for it) and a reminder the day before a date when a signature is still missing; a note when a host adds you to its team or to one of its Public groups, or says yes when you ask; the ones a host sends through us about an event you joined; new events from the hosts you follow, at most one email a day from each, with a link to stop; and, if you host, the notices about your page and its events. Nothing is emailed about a Private event's guest list. There is no newsletter today. If one comes, it will be opt-in, from a separate address, with unsubscribe in every message.

• Your account and what you have done with it stay while the account exists, apart from what the lines below keep longer.
• Messages you write stay until you delete them or your account, or until the host deletes the chat, or the group, the event or the date it belongs to, or closes or deletes its page. Messages you write for a page stay with the page. Deleting one erases its words or photo and leaves "Message deleted" in its place. A host can also remove messages in the chats it makes, or delete such a chat for everyone, and we can remove one that was reported. Delete chat takes a chat off your own list; the others in it keep theirs. A chat for an event's date is deleted for everyone two days after the date ends. A group chat of your own lasts until everyone leaves it or whoever manages it deletes it for everyone.
• When someone reports a message, we keep a copy of it and the four before it that they could see, with their photos, until we close the report, even if those messages, their chat or the accounts that wrote them are deleted meanwhile. Then the copy is deleted, unless the law requires us to keep it longer.
• Orders, refunds and payouts are kept for as long as payment and tax records have to be, up to seven years, and a host's record of who came to a past event stays with that event, apart from the RSVPs of an account that is deleted: those are deleted with the account, guests included.
• We keep a host's documents and signed records while its page is open and we provide the Documents service. When the page closes or we end that service, the host has at least 90 days to download the records before we delete them, unless the law requires us to keep them longer or delete them sooner. The earlier page or service end starts the period. We show the download deadline and honor a later deadline we have already given the host. Deleting your account does not delete the host's record or start that period. The record can include the name you typed, your account's email and id, and the other details listed under What you sign. Hosts are responsible for keeping their own copies for as long as they need them. Keep your own copy too. Copies downloaded or emailed outside Utah Aura are kept by whoever received them, under their own responsibilities.
• To delete your account, use Delete account in your account's Settings, or write to info@utahaura.com. We remove your profile and your sign-in. The messages you wrote as yourself go too, with their photos, and so do your follows of other people and theirs of you; the others in your chats see "Deleted account" where your name was. Messages you wrote for a page stay with it, and a copy kept with a report stays as said above. If you manage a group chat of your own, you choose someone in it to take over, or delete it for everyone, before your account goes. Where the law requires a record of a payment to stay, we keep it without your name attached. What you've signed stays for the document storage period above, with its whole record, such as the name you typed and the email it was signed with. Your account's id stays on it, with no account behind it. If you ran a door, your name stays on each signature you took there for the time above, with your phone's IP address and browser or app. If you want your own copy of what you signed, use Download a copy in Settings before you delete: once your account is gone, so is the Signed page in your account, and you can write to us about information we still hold.
• Something we delete from our database stays in our database provider's daily backups for up to seven days more.
• You can download a copy of your profile, orders, tickets, RSVPs, what you signed while signed in, what was signed for your own place, saved events, the hosts you follow, the pages you're part of, the messages you wrote as yourself with each chat's name and when you sent them, and the people you follow and who follow you, from Settings in your account, or write to info@utahaura.com for everything we hold about you, and we will send it. The copy shows the IP address and browser or app only for what you signed while signed in, other than at a door.

Utah Aura has no accounts for anyone under 18. A minor's name may appear on a ticket or RSVP held by a parent or guardian, for an event a host has opened to them. When an event asks for a signature, the person booking marks each guest who is under 18, and a parent or guardian signs for them. The minor's name, as the parent or guardian types it, is kept with that signature beside their own for the time under How long we keep it, and is in the copy we email. When the person booking gives a guest under 18 an email address, the guest's pass and its emails go there. When a parent or guardian signs for them while signed in, the copy goes to that account's email; signed out, it goes to the address on the guest's pass, when it has one: the one the person booking gave for them or, on a ticket with no address of its own, the buyer's. To get your own copy, sign in before you sign. We don't check anyone's age: if a child under 13 signed for themselves, a parent or guardian can write to info@utahaura.com and we'll delete that signature.

Everything travels encrypted. Who can read which row of the database is decided by policy in the database itself, not only by the app. Card details never touch our servers. There are no passwords to lose. Chats are not end-to-end encrypted, so we hold their words and photos in a form our systems can read. Nobody at Utah Aura reads a chat they aren't in, with two exceptions: when someone reports a message, the people who run Utah Aura read it and the four before it, from a copy taken at that moment that only they can open; and where the law requires it. A page Utah Aura runs itself, such as one we set up for a host before handing it over, has us among its owners, so we read its chats as its team. No system is perfectly safe, and if something happens to your information we will tell you.

Our providers store your information in the United States.

We may update this policy. When a change matters, we say so on the site or by email before it takes effect. The date at the top is the date of the current version.

Utah Aura LLC, info@utahaura.com.