GlamOps Subprocessor List
Contents
Effective date: October 9, 2026 Last updated: October 28, 2026
1. What this list is
1.1. GlamOps LLC ("GlamOps") uses the third-party service providers below ("subprocessors") to help provide the GlamOps service. Each may process personal information that GlamOps processes on behalf of Businesses (including Client information) or that GlamOps controls (such as Business account information).
1.2. This list forms part of our Data Processing Addendum at https://glamops.net/legal/dpa. Terms like "Business," "Client" and "Customer Data" have the meanings in our Terms of Service at https://glamops.net/legal/terms. Our Privacy Policy is at https://glamops.net/legal/privacy.
2. How we choose and manage subprocessors
2.1. Before using a subprocessor, we review its security and privacy practices to confirm it can protect personal information appropriately.
2.2. Each subprocessor is bound by a written contract that:
- limits its use of personal information to providing services to GlamOps, on our instructions;
- prohibits selling the information or using it for its own purposes, including advertising and AI model training;
- requires confidentiality and reasonable security safeguards;
- requires it to notify us of security breaches;
- requires deletion or return of data when its services end; and
- passes on obligations at least as protective as those in our Data Processing Addendum.
2.3. GlamOps remains responsible to Businesses for its subprocessors' performance of these obligations, as set out in our Data Processing Addendum.
3. Current subprocessors
| Subprocessor | Purpose | Personal information processed | Location of processing |
|---|---|---|---|
| Vercel Inc. | Hosting of glamops.net, the GlamOps web app, Booking Sites and Client Portals; content delivery; serverless functions | All data passing through the application, including account, Client, appointment and form data in transit; IP addresses and request logs | United States |
| Supabase, Inc. | Primary database, user authentication and file storage | Business account data; Client contact details, appointment history, notes, intake and consent forms (including health-related answers), photos, payment records, messaging consent and opt-out records, Client Portal sign-in data; booking-site analytics | United States |
| Stripe, Inc. | Payment processing for Businesses (Stripe Connect), GlamOps subscription billing, payouts, and identity verification | Business owner identity and banking details (collected directly by Stripe); Client name, email and payment card details (collected directly by Stripe — card numbers are never stored by GlamOps); transaction amounts, tips, deposits and refunds; for Tap to Pay in the GlamOps app, the card the client taps (read by Stripe’s software and sent encrypted to Stripe) and the phone’s location while the payment is taken | United States |
| Resend (Plus Five Five, Inc.) | Email delivery: account emails, booking confirmations, reminders and Business marketing campaigns | Recipient email addresses and names; email content; delivery, bounce, complaint and unsubscribe events, and open and click events | United States |
| ImprovMX | Forwarding of email sent to glamops.net addresses (such as admin@glamops.net) | Sender and recipient email addresses and names; content and attachments of emails sent to glamops.net addresses | Email in transit for forwarding |
| Twilio Inc. | Text messaging (not yet live; used when text messaging launches): sending and receiving texts, opt-in confirmations, STOP and HELP handling; sending-number registration (toll-free verification) | Client and Business phone numbers; message content; delivery status; consent and opt-out replies; Business legal name, EIN, address and contact for number registration | United States |
GlamOps does not currently use any error-monitoring or third-party analytics provider.
4. Notice of changes
4.1. Advance notice. Before we add or replace a subprocessor that will process personal information we handle on behalf of Businesses, we will update this page and notify each Business's Account Owner by email and in-app notice at least 30 days before the new subprocessor begins processing that information.
4.2. Subscribe to updates. Account Owners receive these notices automatically. Others can ask to receive them by emailing admin@glamops.net.
4.3. Emergency replacements. If we must replace a subprocessor urgently to keep the service secure or running (for example, if a provider suddenly stops operating), we may give notice as soon as reasonably possible after the change, and the right to object below still applies.
5. Right to object
5.1. A Business may object to a new subprocessor by emailing admin@glamops.net within 30 days after our notice, explaining its reasonable, data-protection-related grounds.
5.2. If a Business objects, we will work with it in good faith to address the concern, for example by suggesting configuration changes or confirming additional safeguards.
5.3. If we cannot resolve the objection within 30 days, the Business may terminate its GlamOps subscription by notice to us, without penalty, and we will refund any prepaid fees for the period after termination, as stated in the Data Processing Addendum (Section 9.5) and the Terms of Service (Section 6.9).
6. Contact
Questions about our subprocessors: admin@glamops.net, or GlamOps LLC, Attn: Privacy, 11918 SE Division Street #2046, Portland, OR 97266.