Sigma Overages

Privacy Policy

Effective date: November 13, 2026

Overages is a live-event management service (deals, settlements, tour logistics, expenses and related tools) operated by Sigma Application Solutions LLC ("Sigma," "we," "us"). This policy explains what information we collect when you use Overages at sigmaoverages.com (the "Service"), how we use it, who we share it with, and the choices you have.

1. Who this covers

  • Account holders — people who sign up for and log in to Overages.
  • People added by an account holder — for example crew members, touring party members, contacts and counterparties whose details an organization enters into the Service, even if they never log in themselves.
  • Visitors to our public pages, including people who join our waitlist or email us.

Most information in Overages belongs to an organization (a promoter, venue, artist team, agency or similar business) that uses the Service. The organization decides what to put in and who in it can see what. When we handle that information, we do so to provide the Service to that organization. If you are a crew member or contact and want something changed or removed, you can contact the organization that added you, or contact us (section 10).

2. Information we collect

Information you give us

  • Account details: your name, email address (and any alias email addresses you confirm), password (stored only in a scrambled, one-way form by our authentication provider), phone number if you add one, and your organization memberships and roles.
  • Business records you enter or upload: tours, shows, venues, artists, deals, budgets, ticket sales, settlements, payments, contracts, documents, day sheets and schedules, notes, and chat messages between members.
  • People's details: names, roles, nicknames, email addresses, phone numbers and pay rates for touring party and crew; contact details for venue, promoter and other business contacts.
  • Travel details: flights, hotel stays, rooming lists and ground transport, including passenger names and booking or confirmation details.
  • Expenses: receipt photos and PDFs, expense amounts and categories, and card or bank statement files you upload (which list transactions). We do not collect or store full payment card numbers from those files beyond what the file itself contains, and we never ask for card security codes or bank logins.
  • Support and feedback: messages you send us, bug reports, and questions you ask the in-app Help assistant.
  • Waitlist: if you join our waitlist, your email address and anything else you choose to tell us.

Information from services you connect

  • Google Calendar or Microsoft Outlook calendar (only if you connect one): read-only access to the calendar you pick, so its events can appear on your Overages calendar. See section 5.
  • Eventbrite (only if you connect it): event and ticket sales information for importing into your shows.
  • QuickBooks Online (only if your organization connects it): the account list we need to match categories, and the IDs of records we send there.
  • Calendar subscription links (iCal feeds) you paste in.

Information collected automatically

  • Sign-in and session information: cookies and similar browser storage that keep you logged in, remember which organization you have selected, and keep the app working offline (for example, a saved copy of pages and messages waiting to send).
  • Technical logs: IP address, browser and device type, pages requested and error information, recorded by our hosting and database providers for security and troubleshooting.
  • Abuse prevention: to limit repeated attempts on our public forms (such as the waitlist and password reset), we briefly keep a scrambled, one-way code (a "hash") made from your IP address, and a count of recent attempts. We use it only to count those attempts.
  • Error reports: when something in the app breaks, a technical report of the error (see section 6, Sentry).
  • Usage of AI features: for each AI request, which feature was used, the model, the amount processed and its estimated cost, so we can enforce usage limits.
  • Push notification subscriptions: if you turn on notifications, your browser gives us a subscription address so we can send them.

We do not use advertising cookies, third-party analytics trackers or cross-site tracking.

Payments. Subscription and purchase payments are handled by Stripe. Your card details go directly to Stripe; we receive only a record of the payment (for example amount, date and status) and never see or store your card number.

3. How we use information

We use information to:

  • provide, run and maintain the Service, including calculating deals and settlements, generating exports (Excel, PDF), sending notifications and keeping data in sync between devices;
  • let organizations share specific records with the counterparties and people they choose (for example a settlement shared with an artist team, or travel shared with another organization);
  • process documents and receipts with AI features when you use them (section 4);
  • send service emails, such as alias confirmations, invitations, password resets, share links, hold requests, deposit reminders and digests, and account or security notices;
  • provide support and respond to you;
  • bill organizations for paid plans and enforce plan and usage limits;
  • protect the Service and its users, including preventing fraud and abuse and enforcing our Terms of Service;
  • improve and fix the Service; and
  • comply with law.

We do not sell personal information, and we do not use it for targeted advertising.

4. AI features

Some features use artificial intelligence: the Document Scanner and Total Tour Scanner (deal sheets, offers, settlements, contracts, budgets, day sheets, itineraries), receipt scanning, the Ask search tool and the Help assistant. When you use one, we send the document, image or question, together with the related records needed to answer it, to an AI provider for processing, and store the result in your account for you to review.

  • By default we use Anthropic (Claude). Under the commercial API terms that apply to us, Anthropic does not use this content to train its models.
  • An organization can choose to use its own AI account instead (for example its own Anthropic or OpenAI key). Then that content is processed under the organization's own agreement with that provider. When we send content to OpenAI, we ask it not to store the request.
  • AI output can be wrong. Every scanner shows its results for review before anything is saved; please check figures against the source document.

5. Google and Microsoft calendar data

If you connect a Google or Microsoft (Outlook) calendar, we request read-only access (Google: calendar.readonly; Microsoft: Calendars.Read). We use it only to show that calendar's events (title, time and location) on your own Overages calendar. We do not create, change or delete anything in your calendar. We store the connection's access and refresh tokens so the connection keeps working. Event details are fetched when you view your calendar and may be held briefly in a temporary cache; they are not saved as records in your account. We do not use calendar data for advertising, do not sell it, do not use it to train AI models, and do not let people read it except where you ask us to for support, where needed for security, or where required by law.

Overages' 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.

You can disconnect a calendar at any time in Overages, and you can also revoke access from your Google or Microsoft account settings.

6. Who we share information with

Within the Service, as you direct. Members of your organization see what their role and permissions allow. Records you or your organization share with another organization or person (counterparties on a deal, a linked artist or venue, a Tour Accountant, travel sharing, view-only share links) are visible to them as shared.

Service providers that process information on our behalf to run Overages:

ProviderWhat it does
SupabaseDatabase, authentication and file storage (documents, receipts)
VercelWebsite hosting and running the application
ResendSending service emails
StripePayments and billing
AnthropicAI processing (default provider)
SentryError monitoring: when something in the app breaks, a technical report of the error (what failed, on which page, browser and device type). We configure it not to collect IP addresses, names, emails, cookies or form contents.
OpenAI / GoogleAI processing, only for an organization that chooses one of them with its own key
Web push services (run by browser makers such as Google, Apple, Mozilla and Microsoft)Delivering push notifications you turn on
OpenStreetMapMap images; your browser requests them directly, so OpenStreetMap's servers see your IP address
HEREMap, address and route calculations for tour routing (place and route data, not account details)
FrankfurterCurrency exchange rates (no personal information is sent)

Services you connect. When you or your organization connect Google, Microsoft, Eventbrite or QuickBooks, we exchange the information needed for that connection; for QuickBooks, that includes the expenses, receipts and settlement amounts your organization chooses to send. If your organization creates an API key or webhook (for example to use with Zapier or a spreadsheet), the records that key can read are available to whatever tool holds it.

Legal and safety reasons. We may disclose information if required by law, or to protect the rights, property or safety of users, the public or Sigma.

Business transfers. If Sigma is involved in a merger, acquisition or sale of assets, information may be transferred as part of it, subject to this policy.

7. How long we keep information

  • Account and organization data is kept while the account or organization is active.
  • Deleting your account or organization disables it immediately: it can no longer be signed into, and it stops appearing in the Service. The disabled data is held for 30 days, so a deletion made by mistake can be reversed if you contact us in that time, and is then permanently deleted, including uploaded files. You can ask us to delete it permanently sooner (section 10).
  • Records shared with other organizations stay with them. Records your organization already shared with another organization, such as a settlement they received or a contract they signed, remain part of their records. Signatures and approvals you gave on another organization's records keep your name. If an organization's records are shared like this, we review them before permanently deleting the rest, so the other organization keeps its copy.
  • An organization can't be deleted while it still has upcoming shows, or recent shows whose settlement isn't fully approved, with another organization.
  • Abuse-prevention counts (section 2) are kept for about a day.
  • Logs are kept for a limited time by our hosting and database providers.
  • We may keep information longer where the law requires it (for example billing records) or to resolve disputes.

8. Security

We use encryption in transit (HTTPS), database access rules so each organization sees only its own records and what is shared with it, encrypted storage for certain credentials (for example QuickBooks connections and an organization's own AI key), and automatic sign-out after inactivity. No system is perfectly secure, and we cannot guarantee absolute security. Please use a strong password and tell us right away if you think your account has been compromised.

9. Your choices and rights

  • Access and correct: you can view and edit most of your information in the Service.
  • Export: many records can be exported (for example to Excel or PDF).
  • Delete: you can delete your account from the Account page, or ask us to delete information.
  • Calendar and other connections: you can disconnect them at any time.
  • Notifications and emails: you can turn off push notifications in your browser or the app, and manage reminder settings. Service emails that are needed to run your account (such as security notices) can't be turned off while you have an account.

Depending on where you live (for example in California, other U.S. states with privacy laws, the European Economic Area, the United Kingdom or Canada), you may have additional rights: to know what personal information we hold about you, to get a copy, to correct or delete it, to object to or restrict certain uses, and not to be discriminated against for using these rights. To make a request, contact us (section 10). We may need to verify your identity. If your information was added by an organization that uses Overages, we may pass your request to that organization or ask you to contact it, since it controls those records.

International users. Overages is operated from the United States, and our service providers may process information in the United States and other countries. By using the Service from outside the U.S., you understand your information will be processed there.

10. Contact us

Email: privacy@sigmaoverages.com
General support: support@sigmaoverages.com
Mail: Sigma Application Solutions LLC, 4539 N 22nd St, Ste N, Phoenix, AZ 85016

11. Children

Overages is a business tool and is not intended for anyone under 18. We do not knowingly collect personal information from children. If you believe a child has given us information, contact us and we will delete it.

12. Changes to this policy

We may update this policy. If we make material changes, we will tell account holders by email or in the Service before the changes take effect. The effective date at the top shows when it was last updated.