GigOps.AI
Privacy Policy
Last updated: October 11, 2026 · Operated by GigOps Inc. ("GigOps", "we", "us").
This policy explains what personal information GigOps collects, how we use and share it, and the choices you have. It applies to the GigOps web application, the GigOps iPhone and iPad apps, the gigops.ai website and related services.
Information we collect
- Account information: your name, email address, job title, and a securely hashed password when you register or are invited to a workspace.
- Workspace content you enter: tours, shows, budgets, tasks, schedules, travel, catering, and documents you upload (e.g. riders, stage plots, contracts, W-9s).
- Third-party personal data you provide: details about crew and other team members, venue contacts, vendors, and guests that you add to run your operations.
- Billing information: for paid plans, the name, billing address and payment card entered at checkout. Card details go straight to our payment processor, Stripe; we keep only the Stripe customer and subscription references, plan, seat count and payment status.
- Phone numbers: for crew members and others you choose to send SMS updates to.
- Signing records: when a GigOps customer sends someone a document to sign with GigOps Sign, including people who have no GigOps account. See People who sign documents with GigOps Sign below.
- Agreement records: when you agree to our Terms of Service and this policy, we record the version, the time, your IP address and browser, as evidence of that agreement.
- Mobile app data: in the GigOps iPhone and iPad apps, and only when you use the feature, a driver's or runner's location during a shift, receipt photos, gate scan records and a device token for notifications. See Our mobile apps below.
- Technical data: IP address, browser/user-agent, and session cookies needed to keep you signed in and protect against cross-site request forgery.
- Demo requests: the name, company and work email you enter in the Book a demo form on the gigops.ai website, the page you sent it from and the product you asked about. They go to a Google Sheet through Google Apps Script, where only the GigOps team reads them, to reply to you about a demo. To have them deleted, email hello@gigops.ai.
- Website analytics: on the gigops.ai website (not the GigOps app), our analytics provider HeyCatch records the pages you view, the links and buttons you click, the page you came from, your browser and device, and your approximate location from your IP address. It keeps a random ID in a first-party cookie and your browser's local storage, so visits from the same browser count as one visitor. It does not record your screen or what you type into forms.
How we use information
To provide and secure the service, authenticate users, process subscription payments, send transactional email and SMS (password resets, invites, advances, day sheets, billing notices), deliver in-app and push notifications you enable, keep a record of agreement to our Terms, to see which pages of the gigops.ai website visitors read, and to operate, debug, and improve GigOps.
Cookies
We use a strictly-necessary, HTTP-only session cookie to keep you signed in and a paired CSRF token to protect form submissions. On the gigops.ai website only, HeyCatch analytics sets a first-party cookie holding a random visitor ID (see Website analytics above). We do not use third-party advertising cookies.
Service providers (subprocessors)
We share the minimum data necessary with infrastructure and feature providers:
| Provider | Purpose | Data shared |
|---|---|---|
| Render | Application hosting & database | All stored data |
| Cloudflare | Network proxy and content delivery for the website and the app; object storage (R2) for uploaded files and signed documents | All traffic to the service, including IP address and request contents; uploaded files, stored encrypted with a key Cloudflare does not hold |
| Stripe | Subscription payments, invoices, sales tax | Company name, billing contact name and email, billing address, payment card, seat count |
| Resend | Outbound email | Recipient email, message contents, and attachments such as a signed copy of a document |
| Twilio | Outbound SMS (when you send one, or a one-time signing code) | Recipient phone number, message contents |
| Anthropic | AI parsing of advances, flight emails and tech packs (when you use it) | The text or document you submit to parse |
| Apple Push Notification service | Notifications to the GigOps iOS apps | Device token, notification contents |
| Web push services (your browser's vendor, e.g. Google, Mozilla, Apple) | Browser push notifications you turn on | Push subscription endpoint and an encrypted message it cannot read |
| Google Maps Platform | Address autocomplete, drive-times, geocoding | Venue/hotel addresses, coordinates |
| Google Fonts | Web fonts on GigOps pages | IP address and browser details of the device loading the page |
| Google (Apps Script and Sheets) | The Book a demo form on the gigops.ai website | The name, company and work email you enter, the page you sent it from and the product you asked about |
| HeyCatch | Analytics for the gigops.ai website | Pages viewed, clicks, the referring page, browser and device details, IP address (for approximate location) and a random visitor ID |
| AeroDataBox | Flight lookup/status (when configured) | Flight numbers & dates |
| Open-Meteo | Weather forecasts | Show coordinates/location |
We do not sell personal information.
Data retention
We retain workspace data for as long as your account is active. You may request deletion of your account and associated data as described below; backups are purged on a rolling basis. Documents your company sent for signature are the exception: other people signed them and rely on them, so they are kept after your account is deleted, as described in the next section.
People who sign documents with GigOps Sign
GigOps customers use GigOps Sign to send documents such as contracts, settlements and deal memos to be signed, often to people who do not use GigOps. If you received a link to sign, this section is for you.
What we collect. From the company that sent the document: your name, your email address, and, if they chose these, your mobile number (to text you a one-time code), your role and the business you sign for. When you use your link: when you opened it, your IP address and browser, and whether you confirmed who you are with a code (the codes themselves are kept only in a one-way form nobody can read back). When you sign: the image of your signature and initials, the name you typed, anything you type into the document, the time, your agreement to sign electronically and, when you sign for a business, your statement that you may. We also keep the changes and notes you suggest, a reason you give for declining, and, if you pass the document to someone else to sign, the name and email you give us for them.
How we use it. To show you the document, check who you are where the sender asked us to, record your signature, and make the signed copy: the document with every signature on it and a certificate page, sealed so that any change to it shows. We keep an audit trail of what happened, linked so that an edited entry shows too. We email you the request, reminders and the signed copy, and we let anyone holding a copy check it on its verification page.
Who sees it. The company that sent the document, and the other people signing it. The signed copy's certificate shows each signer's name, email address, IP address, the time they signed and how they confirmed who they are, and everyone who signs gets that copy. Anyone with a document's code (the QR code on each page) can open its verification page: it shows whether the document is signed, the signers' names, their email addresses partly hidden, when they signed, and the trail without IP addresses. It also shows the whole signed document, unless the sender chose to show only the summary.
Who decides. The company that sent the document decides what is sent and to whom, and is the controller of the document and its signing record; GigOps processes them on its behalf. Questions or requests about a document go to that company first, and we will help it answer. After that company's account is deleted, GigOps keeps its signed records so that the people who signed can still rely on them, and for those records GigOps is the controller.
How long we keep it. A document that has been sent cannot be deleted by the sender, so its record stays whole for as long as the sender has a GigOps account. If that account is deleted, we keep each document that was sent for signature, its signed copy, its verification page and its trail (without IP addresses or browser details) for 7 years from the deletion, and then delete them. We keep no signature images, codes or signing links apart from what is printed on the signed copy; each signing link is kept only in a one-way form, so that it still opens its record. Drafts that were never sent are deleted with the account.
Your rights. You have the rights described below. Because a signed document is a record other people rely on, we may not be able to remove your signature from it or delete it while it is kept, except where the law requires; we can correct, restrict or explain what we hold. Contact the sender, or us at hello@gigops.ai.
Our mobile apps
GigOps has iPhone and iPad apps: GigOps (for company users), GigOps Crew, GigOps Athlete and GigOps Scan (the gate scanner), and GigOps Admin for the GigOps team. They show the same workspace data as the web application and follow this policy. On top of what is described above, they collect the following, and only when you use the feature:
- Location (GigOps Crew): when a driver or runner starts a shift, the app sends the phone's precise location to GigOps while the shift runs, including while the phone is locked, so their company's crew and managers can see where the shuttle or runner is. It stops when the shift ends, and the app does not use location at any other time. We keep only each crew member's most recent position, not a history; it is shown only during a shift, replaced by the next update, and deleted with the crew member's profile.
- Photos (GigOps Crew): a runner can attach a receipt photo to an expense. The photo is chosen with the system photo picker, so the app receives only the picture you pick, and it is stored with the expense in your company's workspace.
- Camera (GigOps Crew and GigOps Scan): used only to read QR codes, such as a credential at a gate or the scanner link or crew badge that connects a scanner. The code is read on the device and no images are kept.
- Scan records (GigOps Scan): each scan is recorded with its time, verdict, zone and the pass holder's name, on the device and in the company's scan log in GigOps. So the scanner keeps working offline, the event's pass list is stored on the device with every pass code hashed, so the stored list cannot be used as a pass. A PIN that locks the device to a zone is kept on the device only as a salted hash.
- Face ID and Touch ID: optional, to sign in or unlock the app. Recognition happens on the device through Apple's system, and GigOps never receives face or fingerprint data. If you turn on Face ID sign-in in GigOps Crew or GigOps Athlete, your email and password are kept in the device's keychain and released only after Face ID or Touch ID succeeds.
- Notifications: if you allow them, the app registers a device token with GigOps so we can send notifications through Apple Push Notification service. The token is deleted when you sign out of the app.
- Sign-in: the apps keep your session in the device's keychain.
The apps contain no advertising and no third-party analytics or tracking code, and we do not track you across other companies' apps or websites. To delete your account, use Delete your account on the app's account screen, which emails us the request, or write to hello@gigops.ai.
Your rights
Depending on your location (e.g. GDPR/UK GDPR/CCPA), you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise these rights, contact us at hello@gigops.ai.
Controller vs. processor
For data you enter about your own crew, vendors, venues, and guests, your organization is the data controller and GigOps acts as a processor on your behalf. Direct data-subject requests about that data to the relevant organization. The same applies to documents your organization sends for signature, until your account is deleted (see People who sign documents with GigOps Sign).
Security
We use industry-standard measures including encrypted transport (HTTPS), hashed passwords, scoped access controls, and tenant isolation. No system is perfectly secure; please use a strong, unique password.
International transfers
Your data may be processed in countries other than your own, including the United States. Where required, we rely on appropriate safeguards for such transfers.
Children
GigOps is not directed to children under 16 and we do not knowingly collect their data.
Changes
We may update this policy; material changes will be posted here with a new "Last updated" date.
Contact
GigOps Inc., 4117 N Wolcott, Chicago, IL 60613: hello@gigops.ai.