manage.tickets Privacy Policy
Version: Beta 1 - Effective date: October 18, 2026
1. About this policy
1.1. This Privacy Policy explains what information Manage Tickets LLC ("manage.tickets", "we", "us", or "our") collects through the manage.tickets website and dashboard (the "Service"), why, who it is shared with, how long it is kept, how it is protected, and the choices and rights you have.
1.2. It covers everyone who visits the website, joins the beta list, or uses the Service as an Owner or a Team member of a Business. Words with capitals, such as "Business", "Owner", and "Team member", mean what they mean in our Beta Terms of Use.
1.3. Questions go to support@manage.tickets.
2. The short version
- We collect what the Service needs to work: who you are, how you sign in, and your Business's ticket records.
- We use one cookie, only to keep you signed in. No analytics, no advertising, no tracking across other websites, and no third-party scripts on our pages.
- We do not sell personal information, and we do not use it for targeted advertising.
- Your Business's ticket data is shared with us by default, so we can promote your tickets. The Owner can switch to Private mode at any time.
- Your fingerprint or face never reaches us. Passkeys keep that on your own device.
- You can export your data at any time, and an Owner can close a Business and have its data deleted.
3. Information we collect
3.1. Information you give us
| What | Examples | From whom |
|---|---|---|
| Account details | your name and email address | you, or the Owner who invites you |
| Business details | the Business's name, its Owner, its Team members and their roles | the Owner and Managers |
| Beta list sign-up | name, email, phone (optional), business size, marketplaces used, a message | you, on the homepage form |
| Ticket records | games, sections, rows, seats, quantities, costs, prices, splits, delivery, in-hand dates, tags, notes | you and your Team |
| Purchase records | where tickets were bought, order numbers, dates, totals, fees, a card label such as "Amex Gold 1005" | you and your Team |
| Sale records | marketplace, order number, date, price, fees, payout, delivery and payout status | you and your Team |
| Uploaded rows | the rows of a CSV or Excel file you import | you and your Team |
| Messages | what you write to us in a Request, and a reason you give when you ask for more time before a restart | you |
We ask you not to enter full payment card numbers, bank account numbers, government ID numbers, passwords, or the personal details of ticket buyers into the Service, except in fields built for them.
3.2. Information created when you sign in
| What | Details |
|---|---|
| Sign-in codes | a one-time code we email you. We keep only a scrambled fingerprint of it (a keyed hash), never the code itself, for at most 10 minutes |
| Sessions | a session we keep only as a keyed hash, with when it started, when it was last used, when it expires, and the internet (IP) address it started from |
| Passkeys | a public key, an ID for the passkey, a counter, the ways your device connects (such as USB or internal), a name for the passkey, and when it was added and last used |
| Sign-in record | each sign-in, failed code, sign-out, and passkey sign-in, with the time, the account, and the IP address |
About passkeys and biometrics: when you use a passkey, your fingerprint, face, or device PIN is checked by your own device. The device then signs a challenge with a private key that never leaves it. We receive only the signature and the public key. We never receive, see, or store any fingerprint, face, or other biometric information.
3.3. Information collected automatically
| What | Details |
|---|---|
| Web server logs | for each request to our website: the IP address, date and time, the page or address asked for, the result, the size, the page you came from, and your browser's description of itself (the "user agent") |
| History | every action inside a Business - tickets added, changed, priced, sold, or deleted, imports, exports, and changes of people, permissions, and settings - with who did it, when, and the old and new values |
| Request details | when you send a Request: the page you were on, your browser's description of itself, your screen size, and the ID of the last error your browser met |
| Error reports | when something fails in your browser: where it failed, a short technical description, the time, and your account |
3.4. Information from other sources
| Source | What |
|---|---|
| Ticketmaster | games, teams, venues, dates, times, and game status. This is not information about you |
| Marketplaces (once connected) | your own listings and sales on the marketplaces you connect, which may include buyers' order details. Section 6 explains how we handle buyer information |
4. Cookies and tracking
4.1. We set one cookie, named __Host-ManageTicketsSession, when you sign in. It holds a random session token, and it keeps you signed in for up to 30 days. It is marked Secure, HttpOnly, and SameSite=Strict, which means it travels only over encrypted connections, cannot be read by scripts on the page, and is never sent from other websites.
4.2. Because it is strictly necessary to provide the Service you asked for, it does not need a separate consent.
4.3. We use no analytics, no advertising cookies, no tracking pixels, no social media plugins, and no third-party scripts. Our fonts and scripts are served from our own server.
4.4. Do Not Track and Global Privacy Control: we do not track you across other websites, and we let no one else do so on ours. We treat every browser the same, whatever privacy signal it sends, because there is no tracking to turn off.
5. How we use information
| Purpose | Information used |
|---|---|
| Create and run accounts and Businesses | account and Business details |
| Sign you in and keep your account secure | email, sign-in codes, sessions, passkeys, sign-in record, IP addresses |
| Store, show, and calculate your tickets, purchases, and sales | ticket, purchase, and sale records |
| Enforce each Team member's permissions | roles and permissions |
| Keep the history the Owner and Managers rely on | history |
| Find games and flag changes to them | Ticketmaster information, your ticket records |
| Send email you need - sign-in codes, invitations, security notices, changes to our terms | name and email |
| Answer support requests and feedback | messages and the information they concern |
| Run the beta and choose testers | beta list sign-ups |
| Promote your tickets to more buyers, while Private mode is off | ticket data |
| Keep the Service working, find faults, and stop abuse | web server logs, sign-in record, history, Request details, error reports |
| Improve the Service and create statistics no one can be identified from | all of the above, combined and stripped of identity |
| Comply with the law and protect our rights | whatever the matter requires |
We do not send marketing email without your separate agreement.
6. Ticket buyers' information
When a marketplace is connected, some sales may include details about the buyer, such as a name or an email for delivery. We hold that information only on behalf of the Business that made the sale, only to record and complete the sale, and we do not use it for anything else. The Business is responsible for having the right to give it to us.
7. Data sharing and Private mode
7.1. While Private mode is off, which is the default, we may see and use a Business's ticket data (listings, seats, costs, prices, and sales) to promote its tickets to more buyers, to understand the market, and to improve the Service.
7.2. The Owner sees this choice, with its switch, during the welcome setup before the Business starts, and may turn it off there or at any time in the Business settings. Each change is recorded in the Business's history.
7.3. While Private mode is on, our own screens and tools show none of the Business's ticket data, and we do not use it to promote the Business's tickets. We will not look at that data, except where the Owner asks us to, or where we must, to keep the Service secure, stop fraud or abuse, or comply with the law.
7.4. Private mode is a promise about what we will do. It is not a technical lock: the people who run our servers can technically read the database. Section 10 describes how we protect it.
7.5. Whatever the switch shows, we always see, as the operator of the Service, each Business's name, its people (names, emails, roles, and sign-in times), and its counts, such as how many listings it holds.
8. Inside a Business
8.1. A Business's Owner, and the Team members the Owner allows, can see the Business's records, and can see the history of what each person in the Business did. The team page also shows when each person last used the Service.
8.2. If you are a Team member, the Owner controls your access and decides what you can see and do. Information you enter belongs to the Business, and stays in it if you leave.
8.3. The Owner may ask us about the Business's data. We do not give one Business's data to another.
9. Who we share information with
9.1. We do not sell personal information, and we do not share it for targeted advertising, as those words are used in US state privacy laws.
9.2. We share information only:
| With | What and why |
|---|---|
| Zoho Corporation (Zoho Mail) | your name and email address, and the content of the emails we send you, so Zoho can deliver them |
| GoDaddy.com, LLC | everything stored in the Service, because their servers in the United States run it. They host; they do not use the data. If we move to another host, we update this policy and tell you first |
| Marketplaces you connect | the listing and sale information needed to carry out what you ask, once connected |
| People inside your Business | as Section 8 describes |
| Authorities and courts | where the law requires it, or where needed to protect anyone's safety, or our rights |
| A buyer of our business | if we merge with, are bought by, or sell all or part of our business, under this policy's promises |
| Anyone else | only with your consent |
9.3. Ticketmaster receives no information about you from us. We only read game information from it.
10. How we protect information
- Every connection to the Service is encrypted (HTTPS), and browsers are told to use encryption only.
- Sign-in uses one-time email codes and passkeys. There are no passwords to steal.
- Sign-in codes and sessions are stored only as keyed hashes, so a copy of the database does not reveal them.
- Codes expire after 10 minutes, work once, and stop after 5 wrong tries. Sign-in requests are rate-limited.
- Each Business is walled off. The server reads only the rows of the Business you are signed in to, and sends no value your permissions hide.
- Data files on the server are readable only by the Service itself, and server access needs a private key.
- Backups are made every hour and kept for 7 days.
No system is perfectly secure, and we cannot promise that information will never be accessed without permission.
11. If something goes wrong
If we learn that personal information was accessed without permission, we will investigate at once, notify the people affected without unreasonable delay and within the time the law requires (for example, within 30 days under Florida law), and notify authorities where the law requires.
12. How long we keep information
| Information | Kept |
|---|---|
| Account and Business details | while the account or Business exists |
| Ticket, purchase, and sale records | while the Business exists. Deleted records stay in the trash 30 days, then are removed |
| History | while the Business exists |
| Sign-in codes | at most 10 minutes, then unusable |
| Sessions | until you sign out, or 30 days after last use |
| Passkeys | until you remove them or the account closes |
| Sign-in record | 12 months |
| Web server logs | about 14 days |
| Beta list sign-ups | until the beta ends, or until you ask us to delete yours |
| Backups | 7 days, as they roll over |
| Requests and their messages | 24 months after the Request last changed, then removed |
| Error reports | 90 days, then removed |
When a Business closes, its data leaves the live database at once, and leaves the backups within 7 days. We may keep information longer only where the law requires it, or to resolve a dispute or stop abuse, and only for as long as that need lasts.
13. Your choices and rights
13.1. Everyone may:
- see and correct their own account details in the Service;
- remove their own passkeys and sign out of every device;
- ask us for a copy of the personal information we hold about them;
- ask us to correct or delete it;
- ask us to delete their beta list sign-up.
13.2. An Owner may also export all of the Business's data, switch Private mode on or off, and close the Business.
13.3. A Team member's personal information inside a Business, such as the history of what they did, belongs to the Business's records. We will pass a Team member's request about it to the Owner, and help the Owner answer it.
13.4. Some US state laws give residents further rights, such as the right to know, correct, delete, and opt out of the sale or sharing of personal information, and the right not to be treated differently for using these rights. These laws may not apply to a service of our size, but we will answer such requests from any user in the same way.
13.5. Send requests to support@manage.tickets. We will confirm who you are, usually by asking you to sign in or to answer from your account's email, and we will answer within 45 days. You may appeal a refusal by replying to our answer.
14. Children
The Service is for adults running a business. It is not meant for anyone under 18, and we do not knowingly collect information from children under 13. If you believe a child has given us information, tell us, and we will delete it.
15. Where information is kept
The Service is offered in the United States, and information is stored and processed in the United States.
16. Changes to this policy
We may change this policy as the Service changes. Where a change is material, we will tell you by email or in the Service before it takes effect, and ask you to accept the new version. Each version, with its effective date, stays available on request.
17. Contact
Manage Tickets LLC - support@manage.tickets