This page lists the third-party service providers (“subprocessors”) that Develop Digital Media, LLC doing business as Service Anchor (“Service Anchor,” “we,” “us,” or “our”) uses to deliver the Service Anchor platform (the “Service”).
We use subprocessors to provide infrastructure, payment processing, communications delivery, authentication, and analytics. Each subprocessor processes only the data needed for its function. We select subprocessors we believe are commercially reasonable for our scale and use case, and we evaluate the security and privacy posture of each one.
This list is incorporated by reference into our Privacy Policy at getserviceanchor.com/privacy-policy and our Terms of Service at getserviceanchor.com/terms-of-service.
Current subprocessors
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Infrastructure hosting and email delivery | All Service data at rest and in transit | United States |
| Clerk, Inc. | Authentication and user session management | Account email, password hash, session tokens | United States |
| Stripe, Inc. | Payment processing and subscription billing (platform billing and Stripe Connect) | Payment method on file, billing history, invoice records | United States |
| Twilio, Inc. | SMS and voice delivery, Trust Hub / A2P 10DLC business verification, Campaign Registry brand and campaign registration | Phone numbers, message content, call metadata, brand registration data, business Tax Identifier (forwarded only; the full value is not retained by Service Anchor) | United States |
| Loops.so | Lifecycle and transactional email | Customer email addresses, email content, delivery metadata | United States |
| Resend, Inc. | Transactional email delivery (backup and failover) | Customer email addresses, email content, delivery metadata | United States |
| OpenRouteService GmbH | Route optimization | Addresses and geographic coordinates submitted for routing. No personal data is retained by OpenRouteService beyond the request. | European Union |
| Google LLC (Google Analytics 4) | Website analytics on getserviceanchor.com |
IP address, device and browser information, pages viewed | United States |
| Functional Software, Inc. (d/b/a Sentry) | Application error tracking and exception aggregation | Stack traces, request URLs, user and tenant identifiers, browser and device metadata, git release SHA | United States |
How to be notified of changes
We commit to providing at least 30 days’ written notice before any material change to this list that affects how personal data is processed. Notice is delivered:
- By email to the primary contact address on file for active customer accounts.
- By posting an updated version of this page with a new “Last updated” date.
- In the customer dashboard as a visible notification banner for the duration of the notice period.
Material changes include: adding a new subprocessor that processes Customer Data or End-Customer Data; replacing one subprocessor with another performing the same function; changing the data residency of a subprocessor in a way that affects cross-border transfer obligations.
Non-material changes (such as a subprocessor’s company-name change without a change in service) may be made without advance notice.
Right to object
If you have a reasonable, good-faith objection to a new or replacement subprocessor (for example, because the subprocessor presents a compliance issue specific to your business), contact us at privacy@getserviceanchor.com within the 30-day notice period. We will work with you in good faith to address the concern. If we cannot accommodate the objection and you choose to terminate your subscription as a result, we will pro-rate any prepaid platform fees back to the date of termination.
This right does not apply to subprocessors already in use as of the effective date of this page.
Service Anchor as a subprocessor
When you use Service Anchor to manage your business, you are loading data about your own end customers (End-Customer Data, as defined in our Privacy Policy) into the Service. With respect to that data, you are the controller and Service Anchor is the processor. The subprocessors listed above are our subprocessors, and may be considered subprocessors of yours under applicable data protection law.
If your contracts with end customers require you to disclose the subprocessors you use to process their data, this page is a stable URL you can reference. If your contracts require you to obtain consent before adding subprocessors, please review this page before adding such customers and contact us if you have questions about a specific subprocessor.
Contact
For questions about this list or about a specific subprocessor:
Develop Digital Media, LLC d/b/a Service Anchor
80 Rainey St., Unit 3506
Austin, TX 78701
Privacy questions: privacy@getserviceanchor.com
General support: support@getserviceanchor.com
