How we handle information.

SixStack Relay (“Relay”) is provided by SixStack LLC, an Idaho limited liability company (“SixStack,” “we,” “us”). Relay helps service businesses take customer requests, send quotes, schedule and dispatch visits, give technicians a phone app for the day’s work, send invoices and take payments, offer a customer portal and memberships, and email or (optionally) text their customers. It also has an optional AI drafting assistant called Relay Assist.

This policy covers three groups of people:

• visitors to our website, sixstackrelay.com;
• businesses that use Relay, and the owners and team members who sign in for them; and
• customers of those businesses, whose information a business keeps in Relay or who use a business’s quote, invoice, booking, membership or portal pages.

For a business’s customer data, the business is in charge. When a business keeps information about its own customers in Relay, that business is the controller (it decides why and how the information is used) and SixStack is its processor and service provider. We handle that information only to provide, secure and support Relay for that business, as described in this policy and our Terms of Service, or when the law requires it.

For our own account and website records, we are in charge. SixStack is the controller of information about the businesses that sign up, their team members’ accounts, subscription billing, support conversations and our website.

If you are a customer of a business that uses Relay and you have a question or request about your information, please contact that business first. It controls your records and can view, correct, export or delete them. We will help the business respond.

• Account and team information: names, email addresses, phone numbers, roles, and sign-in records. Passwords are stored only as salted, one-way scrypt hashes, never as plain text.
• Business settings: company name, logo, colors, contact details, services and prices, tax rates, business hours, message templates, and other settings.
• Customer records a business keeps: customer names, email addresses, phone numbers, service addresses, equipment, requests, notes, visits, checklists, inspection reports (with customer signatures and when the customer opened the report link), multi-day job schedules and day notes, change orders (with customer signatures and when the customer opened the change order link), photos, quotes, invoices, payment records, memberships, message history, language preference, and records of consent to texts and opt-outs from email or texts.
• Job expenses: amounts, categories, vendors, notes and receipt photos that team members add to visits and requests. Receipt photos are re-encoded without camera location data and stored privately. Costs are shown only to the business’s team; customers see an expense only when the business bills it as an invoice line.
• Technician location while on the way: when a business sends live tracking links with its on my way messages and a team member chooses to share their phone’s location (their browser asks first, and they can turn it off in their profile), Relay keeps only that person’s latest approximate position (about 100 meters) for the visit they are driving to. It is shown only on that visit’s private tracking link, never after they arrive, and it is deleted when they arrive, start or finish the job. Relay keeps no location history. The customer’s tracking link records when it was first and last opened.
• Team chat: messages, mentions, notes and photos that a business’s team members send each other inside Relay, including notes kept on a visit, customer or request. Team chat is internal to the business and is never sent to or shown to customers.
• Pay and commissions: when a business uses tech pay, each team member’s pay rule (hourly rate, flat rate or salary, and commission percentages), bonuses and deductions with their reasons, and an approved copy of each pay period (hours, gross pay and the quotes, invoices and customer names that earned a commission), with who approved or reopened it. Pay is sensitive: it is shown only to the business’s owners, to managers an owner allows, and to each person for their own pay when the owner turns that on. Relay works out gross pay for the business to enter in its own payroll; it does not calculate taxes, run payroll or file anything.
• Truck stock: the parts a business keeps in its shop and on each truck, the team member a truck is assigned to, and a log of who received, moved, used, counted or adjusted stock and when.
• Information customers give directly: through a business’s website request form, online booking, quote approval, invoice payment, membership sign-up or customer portal (including visits they reschedule or cancel and the reason they give), and replies to emails and texts. When a customer approves a quote, Relay records the name they typed, the time and the options they chose. When a customer opens a quote or invoice link, Relay records when it was first and last opened so the business knows it was seen. When a quote is presented as a sales proposal, Relay also counts each time the link is opened, how long the page stays in view, whether the screen is phone sized, and the option last picked; no IP address or browser details are kept with it.
• Subscription billing: Stripe customer and subscription references, plan, user count, text count and invoice status. We do not store full card or bank account numbers.
• Security and operations records: activity history (who changed what, and when), message delivery results, error details, and short-lived rate-limit records based on network address that help us block abuse.
• Support: what you send us by email or live chat.

We use information to:

• provide Relay, keep each business’s data separate, and sign people in;
• send the emails and texts a business asks Relay to send, and deliver replies back to the business;
• send account emails, such as invitations, password resets, billing notices and important service notices;
• bill subscriptions and usage;
• answer support requests;
• protect Relay and its users, investigate misuse, and keep records of security events;
• understand and improve how Relay works, using operational information about the service itself; and
• meet legal obligations.

We do not sell personal information. We do not share it for cross-context behavioral advertising, build advertising profiles, or let our service providers use it for their own advertising. We do not use customer data to train AI models.

Email. Staff write and send customer emails from Relay. A business can also turn on automatic emails (visit booked, visit time changed, reminder the day before, on my way, thank you, and unpaid invoice reminders). Each kind is off until the business turns it on. On my way emails and texts can carry a private tracking link that shows the visit’s status and, while the technician is on the way and has chosen to share it, an approximate location and an arrival estimate. The link stops working shortly after the visit. Marketing emails, such as campaigns, include an unsubscribe link, and Relay stops sending marketing email to anyone who unsubscribes or marks a message as spam. Service emails about visits, quotes and invoices can still be sent. Relay stops emailing addresses that permanently bounce.

Text messages. Texting is off until a business turns it on, and each automatic text kind is off until the business turns that on too. Relay texts only customers whose consent the business has recorded, or who opted in themselves (for example, on an online booking page). Texts are sent through Twilio from a phone number SixStack operates for the businesses that use Relay, and each text starts with the business’s name. Message frequency varies. Message and data rates may apply.

• Reply STOP (or STOPALL, UNSUBSCRIBE, CANCEL, END or QUIT) to stop texts. Relay records this right away and stops sending. Because businesses currently share one Relay number, STOP stops texts from that number for every business that uses Relay.
• Reply HELP for the business’s contact details. Reply START to receive texts again.
• We do not share mobile numbers or text-message consent with anyone for their own marketing. Text consent and opt-out records are used only to send and stop the business’s messages.

Each business is responsible for having permission to email and text its customers. See our Terms of Service for the rules businesses agree to.

Subscriptions. Businesses pay for Relay through Stripe Checkout and manage billing in Stripe’s billing portal. Card details are entered on Stripe’s pages and go straight to Stripe.

Payments customers make to a business. If a business connects its own Stripe account through Stripe Connect, its customers can pay invoices, deposits and memberships by card or, if the business allows it, by US bank account. The customer enters payment details on Stripe’s page, and the money goes to the business’s Stripe account. SixStack never receives or holds those funds. Relay receives a confirmation of the payment, the amount, the card brand or bank name, the last four digits, and a Stripe reference, so the invoice can be marked paid.

Saved payment methods and autopay. If a business turns on saved cards, its customers can ask Stripe to keep a card or US bank account on the business’s Stripe account for later payments to that business, and can agree to autopay so new invoices are charged automatically. Relay stores the Stripe references, the card brand or bank name, the last four digits and the expiry date, the consent wording the customer agreed to and when, whether autopay is on, and a record of each charge and whether it went through. Full card and account numbers stay with Stripe. A customer can remove a saved method or turn autopay off at any time from their customer account, or by asking the business.

Stripe handles payment information under its own privacy policy at stripe.com/privacy.

Relay Assist is off for every business until an owner turns it on and chooses which features to allow. When it is off, nothing is sent to an AI provider.

When it is on, it runs only when a team member asks for it on a specific record, such as a request summary or a quote draft. Relay sends Anthropic only the information needed for that task, for example the request text, the service asked for, and the business’s saved services and prices. The result is always a draft that a person reviews. Relay Assist never sends messages to customers, sets prices on its own, or changes records unless a person saves the change.

SixStack does not use customer data to train AI models. Under Anthropic’s commercial terms, Anthropic does not train its models on data sent through its API, and it keeps that data only for a limited time.

These companies process information on our behalf to run Relay. Each receives only what it needs for its job.

• Vercel

  Hosts the Relay website and app and runs the servers that handle every request.

  When: Always

• Supabase

  Runs the PostgreSQL database where Relay stores account and business records, and stores uploaded files such as job photos.

  When: Always

• Stripe

  Processes SixStack subscription payments. Through Stripe Connect it also processes card and bank payments that a business's customers make to that business.

  When: Subscriptions always; customer payments only if a business connects Stripe

• Resend

  Delivers email: account emails such as invitations and password resets, and the customer emails a business sends.

  When: Always

• Twilio

  Sends and receives customer text messages.

  When: Only if a business turns texting on

• Anthropic

  Provides the AI model behind Relay Assist, the optional drafting assistant.

  When: Only if a business turns Relay Assist on

• Google

  Syncs visits with Google Calendar.

  When: Only if a business connects Google Calendar

• Intuit (QuickBooks Online)

  Receives finished invoices, receipts and payment records for the business's bookkeeping.

  When: Only if a business connects QuickBooks Online

• U.S. Census Bureau Geocoder

  Turns service addresses into map locations for scheduling and dispatch.

  When: When a service address is placed on a map

• OpenStreetMap

  Supplies the map images inside the app. Your browser loads them directly from OpenStreetMap's servers, which see your IP address and the map area shown.

  When: When a map is displayed

• Chatwoot

  Runs the live chat on our website.

  When: Only if you choose Start live chat

• Browser push services (such as Apple, Google and Mozilla)

  Deliver phone and browser notifications to team members.

  When: Only for team members who turn notifications on

Some links in Relay open other services in your browser, such as Google Maps for driving directions. Those services have their own privacy policies.

We may also disclose information if the law requires it, to protect the rights, safety or security of people or of Relay, or as part of a merger, acquisition or sale of our business, in which case this policy would continue to apply to the information transferred.

Relay uses only the cookies it needs to work. We do not use advertising or analytics cookies.

• Sign-in cookies keep team members and customers signed in.
• A language cookie remembers the language a customer picks on customer-facing pages, such as quotes and invoices.
• A short-lived cookie protects the step where an owner connects QuickBooks Online.
• A short-lived cookie remembers which visit a customer was changing when they ask for a sign-in link, so the link opens that visit (it lasts an hour and holds no personal information).
• Browser storage remembers small conveniences, such as a dismissed notice, an unsaved draft, or a Relay Assist draft handed to the quote form (cleared after 10 minutes).

Our website’s live chat loads only after you choose Start live chat, and then Chatwoot uses its own cookies and storage to keep your conversation. Stripe’s checkout and billing pages are on Stripe’s own site and use Stripe’s cookies. Because we don’t sell or share personal information for advertising, we have nothing to change when a browser sends a Global Privacy Control or Do Not Track signal.

• Connections to Relay and to its database are encrypted in transit (HTTPS/TLS).
• Every request is checked against the signed-in person’s business and role, so one business cannot see another’s data and team members see only what their role allows.
• Passwords are stored as salted scrypt hashes. Google and QuickBooks connection tokens are encrypted.
• Messages from Stripe and Twilio are checked for a valid signature before Relay acts on them.
• Important changes are recorded in an activity history.

No system is perfectly secure, and we cannot promise that information will never be accessed without permission. If a security incident affects information in Relay, we will notify affected businesses as the law requires and help them meet their own obligations. Relay is not built to store payment card numbers, Social Security numbers or health records, and businesses should not enter them in notes or forms.

We keep a business’s information while its account is open. When a trial ends or a subscription is canceled, Relay does not automatically erase workspace records. The workspace stays available read-only, so owners can sign in, review records and export what they need. We do not promise a fixed automatic deletion deadline.

An owner can ask us to delete the workspace at any time (see the next section). Even after deletion, we may keep:

• billing, tax and payment records we must keep by law;
• security and activity records needed to protect the service or resolve disputes;
• text and email opt-out records, so a person who said stop is not contacted again; and
• copies in backups until those backups are replaced in the normal course.

Some information is kept for a short time by design: a technician’s shared position is deleted as soon as it can no longer be shown (and within 30 minutes in any case), and on my way tracking links are deleted a week after they are made.

Businesses. Owners can download CSV exports of customers, requests, quotes and invoices, the schedule, reports and other records at any time, including after canceling. Owners and managers can correct or remove most records directly in Relay. To delete a whole workspace or ask about other records, email us from an owner’s account address. Before changing or deleting anything, we verify the identity and authority of the person asking.

Customers of a business. Please contact the business that keeps your records. If you contact us instead, we will pass your request to that business and help it respond.

Privacy rights under state law. Depending on where you live, you may have the right to know what personal information we hold about you, to get a copy, to correct it, to delete it, and to opt out of its sale or use for targeted advertising (we do neither). You can make a request yourself or through an authorized agent, and we will not treat you differently for using these rights. Email us to make a request, and we will respond within the time the law requires.

Relay is a business tool. It is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has given us personal information, email us and we will delete it.

Relay is run from the United States for businesses in the United States. Information is stored and processed in the United States. Customer payments through Stripe Connect and customer texts are available only in the United States. If you use Relay from outside the United States, your information will be transferred to and processed in the United States, where privacy laws may differ from those where you live.

We will update this policy when Relay or the law changes. The date at the top shows when it last changed. If we make a significant change, we will tell account owners by email or in Relay before it takes effect.

Questions or requests about privacy: contact@sixstackrelay.com. You can also reach us through our support page.

Legal business name: SixStack LLC
Effective date: 2026-10-13