Privacy policy
Last updated October 3, 2026.
1. Overview
TixTally is a product of Vinara Software Co. This policy covers two kinds of people: an Organizer running events on TixTally, and a Buyer purchasing a ticket to one. It describes what we collect from each, why, and for how long. It is part of our Terms of service and complements our Cookie policy, which covers browser-level tracking specifically.
2. What we collect
From an Organizer: account details (name, email, password), organization and event details you enter, and whatever Stripe requires to verify your connected account. We never see or store your card or bank details; that runs through Stripe directly.
From a Buyer: the email you give at checkout, and your name if you give one. We do not ask you for a phone number, though an Organizer can add one against a ticket they issued you. Each Organizer you buy from keeps one record of you rather than a new one for every order.
From anyone contacting support: whatever you write to us, plus your account or organization context so we can answer without asking you to repeat it.
Automatically: basic product-usage events (for example, that an event was published or an order completed), technical error details if something breaks, and page-timing data from a fraction of visits so we can tell a slow page from a broken one. See Third parties below for exactly how.
3. How we use it
- To operate the Service: create your account, run checkout, issue tickets.
- To deliver tickets and account emails, and to respond when you contact support.
- To detect and limit abuse, for example rate-limiting repeated requests from one source.
- To fix bugs, using the technical details an error report contains.
- To understand product usage in aggregate, so we know what to build next.
We do not sell personal data, and we do not use it for advertising. We do not run advertising cookies or trackers of our own; see our Cookie policy for the complete, short list of everything we do set.
4. Third parties
Running TixTally means some of your data is processed by companies working on our behalf. These are the purposes we use them for, and each one receives only what its purpose needs. None of them may use your data for their own purposes.
- Payment processing. Stripe, named here because you deal with it directly: card details go straight to Stripe and we never handle them. For Organizers it also verifies the connected account.
- Hosting and databases. Runs the Service and holds the records described above, including accounts, events, orders, tickets, and attendance.
- Email delivery. Sends ticket, invitation, and account emails. Receives the address it is sending to and what the message says.
- File storage. Holds files an Organizer uploads, such as an event or organization logo.
- Background processing. Runs work that continues after a request finishes, such as issuing tickets for a paid order. Receives the order and the Buyer's email address.
- Error monitoring. Tells us when something breaks, with the technical details around it such as the page you were on and your browser version, and samples page timings from a fraction of ordinary visits. It sets no persistent cookie or identifier here.
- Product analytics. How the Service is used. These calls run on our own servers rather than in your browser, and set no cookie on this site.
Your use of a provider's own functionality through TixTally, particularly Stripe's, is also subject to that provider's own privacy policy.
5. How long we keep it
Orders and tickets. Kept indefinitely, the same way a financial receipt is. An order is a transaction record between an Organizer and a Buyer, and both may need it later for taxes, a dispute, or a refund.
Account data. Kept while your account exists. We do not yet offer instant self-service deletion; contact us (see Contact) and we will delete what we can, keeping only what we are required to retain for financial recordkeeping.
Operational housekeeping. Rate-limit records are deleted after 24 hours once they can no longer affect any limit. Email delivery logs are deleted after 90 days. Both are removed automatically by a scheduled job; neither is a record you would ever need to look up yourself.
6. Your choices
You can ask us what personal data we hold about you, ask us to correct it, or ask us to delete it. An Organizer asks through Help and support in their TixTally dashboard. A Buyer has no account with us, so the route is the Organizer you bought from: they can send us your request directly from their dashboard, and we act on it the same way. We will honor a deletion request except where we need to keep a record for tax, fraud prevention, or another legal obligation, in which case we will tell you what we kept and why.
Deleting a Buyer means we overwrite the name, email, and phone number held against every order, attendee, and saved contact, at every Organizer you bought from. We keep the order itself: what was bought, when, and for how much. That record is the Organizer's receipt and part of their books, and it no longer says who you are.
7. Security
Data is encrypted in transit. Access to organization data is scoped so that only people with a reason to see it can, and every sensitive action taken on your behalf by our own staff is logged. No system is perfectly secure, and we cannot guarantee absolute security, but this is how we treat it.
8. Children
TixTally is not directed at children, and we do not knowingly collect personal data from anyone below the age described in our Terms of service. If you believe a child has given us personal data, contact us and we will remove it.
9. Changes to this policy
If what we collect or how we use it changes in a way that matters, we will update this page and the date at the top of it.
10. Contact
Email support@tixtally.app with any question about this policy, or any request about your own data. You do not need an account, and we answer requests from Buyers and Organizers at the same address.
An Organizer who is signed in can also use Help & support, or Account for a deletion request. Both reach the same place with your identity already established, which is faster, but neither is required. Our support page lists every route.