Privacy Policy

This Privacy Policy explains how TortillaNet (“TortillaNet,” “we,” “us,” or “our”) collects, uses, and shares personal information when you use our website at tortillanet.app and related services (the “Service”). We built TortillaNet to help small communities organize in-person events, and we treat your information with that intent — respectfully and only as needed to run the Service.

As we add features we will update this policy and post the new effective date above. Material changes will be communicated via the Service or by email.

1. Information we collect

You provide it to us

• Account information: your email address and password (or magic-link verification), and optionally your phone number for future SMS notifications.
• Profile information: your display name and (optional) avatar.
• Community and event content: communities you create or join, event details, RSVPs, contribution items (e.g. “what I'm bringing”), announcements / broadcasts you send, messages you post in an event's group chat, and photos, videos or captions you upload — to an event, or, if you host or manage a community, to that community's own page. If you join an event's waitlist, we also collect the names you give for anyone you're bringing.
• Tickets: when you get a ticket — paid or free, with or without an account — we record your name, your email address, what you ordered, what you paid, and any coupon code you used. The event's host and the people they have working the event can see this, along with whether each ticket has been checked in. Hosts who restrict a coupon to particular people give us those people's email addresses for that purpose only. Your tickets are reachable through a private link we email you; anyone you share that link with can see them. If you transfer a ticket, or a host issues one to you, we use the name and email address given for the new holder to send them that ticket. If you join a waitlist for a sold-out event, we keep your name and email address to tell you when tickets open up, the host can see that you are waiting, and every such email has a link that takes you off the list.
• Co-host invitations: when a host invites someone to co-host an event by email, we store the address they enter and use it only to send that invitation (and any resend they ask for); the host can see the address they entered and whether the invitation is still waiting. A host can instead share a one-time invitation link. If you open a shared link without an account and give us your email address, we use it only to email you a link that confirms the address is yours; no account is created until you open it. When you accept, your name appears as a co-host on the event, you are added to the event's community as a member (unless the event is a host's one-off event), and we record that you accepted and when.
• API keys and exports: if you host or manage a community and create an API key, we record its name, who made it, what it can read, when it expires, when it was last used and how many requests it made each day; a host who lets a key read names and email addresses also gives us, in their own words, what those addresses will be used for. Each time a key reads names or email addresses we log which key, when, what it asked for, how many people it covered, and a value derived from the requesting server's IP address. We never store a key itself, only a one-way fingerprint of it, and it is shown to the person who made it once.
• Billing information: if you host, your plan and billing status; if you contribute supporter credits, the amount, your display name, and any note you add, which are shown to the host you support. Card details are entered directly with Stripe and never reach our servers.
• Communications: messages you send us for support or feedback. If you call or text our phone line, we collect your phone number, the messages you send, and — if you leave a voicemail — a recording and automated transcript of your message.

Collected automatically

• Authentication cookies: required to keep you signed in. We do not use third-party advertising cookies or behavioral-tracking pixels.
• Access cookies: when you open a community or an event through an invite link or an event's unique link, we remember that code in a cookie so the page still opens after steps that drop it from the address bar — for example returning from a ticket payment. It grants nothing on its own; the code is checked against the community or event every time.
• Server logs: standard request data (IP address, user agent, timestamp, requested URL) for security, debugging, and abuse prevention. This includes views of our event widgets embedded on other websites: the widget loads from our servers, so we receive the same request data as for any page view, even though you are on someone else's site. Embedded widgets set no cookies.
• Error reports: when a page or our servers hit an error, we record what went wrong, the page it happened on (with invite codes, ticket and order links, and other private codes removed from the address), your browser's user agent, and your account ID if you are signed in. These are used only to fix bugs and are deleted after 60 days.
• Abuse limits: to stop automated guessing of coupon codes, hoarding of tickets, and use of our forms to send unwanted email, we count recent attempts on a few endpoints. Each counter is keyed by a one-way hash of the IP address (or, for limits on how often we email one person, of their email address), not the address itself, and is deleted within a few hours.

2. How we use information

• To operate the Service: authenticate you, store your communities, events, RSVPs, and uploads, and deliver announcements and reminders.
• To send transactional emails (account confirmation, password reset, RSVP confirmations, host broadcasts, event reminders, and — when a host removes your RSVP and chooses to tell you — that notice with the host's name and any reason they gave).
• To improve and secure the Service: detect abuse, prevent fraud, and fix bugs.
• To comply with legal obligations.

3. How we share information

We do not sell personal information. We share information only with service providers that help us run the Service, and only as needed:

• Supabase (database, authentication, file storage) — stores your account, communities, events, RSVPs, and uploads on our behalf.
• Resend — sends transactional emails on our behalf.
• Stripe — processes payments for host plans, supporter credits, tickets, and donations. Stripe receives the payment details you enter and your email address, and handles them under its own privacy policy.
• Twilio — provides our phone line: routes calls and text messages to and from us, records and transcribes voicemails you choose to leave, and processes the associated phone numbers and message content. Phone support is offered to members on current or past paid plans, so when you call, the number you call from may be matched against account phone numbers to route your call.
• Venmo — a host may publish one or more Venmo handles, shown as a QR code and a link. Both are ordinary links to venmo.com; nothing about you is sent to Venmo by us, and no payment made this way passes through TortillaNet or is recorded here. Following one takes you to Venmo (or opens its app), where what happens is between you and Venmo under its own privacy policy.
• Netlify — hosts the website.
• Embedded video players — when a host adds a video link to an event, the player is loaded directly from that service (YouTube, Vimeo, or Collectivision, whose videos are delivered by Bunny.net). Opening such an event page means your browser contacts that provider, which can see your IP address and may set its own cookies under its own privacy policy. We do not send them your account information, and no video player loads on an event that has no video.
• Maps — tapping an event's address lets you open it in Google Maps, Apple Maps, or OpenStreetMap; nothing is sent to any of them until you choose one. If you choose OpenStreetMap, your browser first asks OpenStreetMap's place-search service (Nominatim) where that address is, so the map opens on it. That request carries the event's address and, like any web request, your IP address, but nothing about your account. Each service handles what it receives under its own privacy policy.
• Your community's hosts, through their own tools — a community's hosts and managers can connect their own websites and software to TortillaNet with an API key. Depending on what the key allows, it can read the community's events (never street addresses), and lists of who RSVP'd, bought a ticket, joined a waitlist or belongs to the community, as identifiers and statuses. Only a community's hosts can let a key also read names, email addresses and what people said they're bringing. While a community has such a key, the email box on its ticket, waitlist and sign-up forms says so, and shows the host's own description of what the addresses are for. An email address is only available through a key if it was given while that notice was showing: addresses given to a community before it turned on email export are never exported this way, though the host can still see them inside TortillaNet as before. Once exported, that information is held in the host's own systems and governed by the host's own practices and privacy notice, not this policy; please ask the host about it. Phone numbers are never available through a key. The community's hosts are emailed whenever a key that can read email addresses is created, can see a log of every such read, and can revoke a key at any time. A key stops working by itself when the person who made it no longer has the role it needs.
• Law enforcement or legal process — when required by law, or to protect the safety, rights, or property of TortillaNet or others.
• In a business transfer — if TortillaNet is acquired or assets are transferred, your information may be transferred under the same protections described here.

Within the Service, content you create is visible according to context: event details and photos are visible to members of the community where they're posted. If you host an event without putting it in a community, we keep it in a personal space of your own that is titled with your display name and has a web address made from it (for example, tortillanet.app/your-name), so guests opening that event or that page will see your display name as its host; broadcasts you send go only to the audience you select. Other users do not see your email address or phone number unless you choose to share them. Each event's host chooses who can open it. By default, a new event can be opened by anyone holding that event's unique link, including people who are not signed in — that link opens that event alone and not the rest of the community. Such an event also opens for anyone holding the community's invite link. A host may instead limit an event to people who are signed in and have joined the community; people holding the community's invite link still see that event's title, date, place name and poster in the community's list of events, marked as for members, but not its description, address or anything else on its page. A community's hosts and managers may instead make an event public: anyone can then open it without a link, search engines may list it, and it can be shown on other websites, including through the widgets and API described in section 3. On a public event, the title, time, venue name, poster, description and the host's name are public, along with how many people are going; the street address, parking notes and the names of who is coming are shown only to the community's members, the event's hosts, and people who have RSVP'd as going or maybe or hold a ticket. If you RSVP to a public event you don't join its community, but the event appears on your dashboard. The rest of the community stays private. These limits are enforced by our database as well as by our pages. A host can replace that link at any time, which immediately stops the old one working. A community's hosts and managers may also publish photos and videos to the community page itself, above its event list; those are visible to everyone who can open that page. Each event's host decides whether guests may add photos and videos to it; where that is switched off, only the host, co-hosts and community staff can add to those galleries, and everyone who can see the event can still view what is already there. An event's group chat is visible to members of its community and, unless the host turns this off, to anyone else who can open the event page, including people without an account. A host may also let people without an account post in the chat; their messages appear under the name they gave when they RSVP'd.

4. Your choices and rights

• Access & update: you can view and update your profile from the dashboard at any time.
• Delete your account: contact us at the address below to permanently delete your account and associated personal information. Some information may be retained where required by law or for legitimate business purposes (e.g. anti-abuse logs).
• Communications: transactional emails (event reminders, host announcements) are part of the Service. You can leave a community to stop receiving its announcements, or delete your account to stop all email.

Depending on where you live, you may have additional rights under laws such as the California Consumer Privacy Act (CCPA) or the EU General Data Protection Regulation (GDPR), including the right to know, delete, correct, or port your information, and to non-discrimination for exercising those rights. To exercise these rights, contact us at the address below.

5. Children

TortillaNet is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us and we will delete it.

6. Data retention

We retain account information for as long as you have an account, and content (events, RSVPs, photos) for as long as the community it belongs to exists. Co-host invitations, including any email address entered for one, are kept with the event as a record of who was invited and by whom, and are deleted with it. Error reports are deleted after 60 days. The log of API reads of names and email addresses, and the daily request counts for API keys, are deleted after 13 months; a revoked key's record stays with its community for as long as the community exists, so its hosts can see what it did. Backups may be retained for a limited additional period for disaster recovery. When you delete your account or content, we remove it from our active systems within a reasonable period.

7. Security

We use standard administrative, technical, and physical safeguards designed to protect your information. No system is perfectly secure; please use a strong password and notify us promptly if you suspect any unauthorized access to your account.

8. International users

TortillaNet is operated from the United States. If you access the Service from outside the United States, your information may be transferred to, stored, and processed in the United States and other jurisdictions where our service providers maintain facilities.

9. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date at the top of this page. Continued use of the Service after an update constitutes acceptance of the revised policy.

10. Contact us

Questions or requests? Email privacy@tortillanet.app. TortillaNet is based in Eugene, Oregon, USA.