Legal
Sub-processors
- Effective
- Last updated
We keep the vendor list short on purpose: fewer companies touching your data means fewer places for it to go wrong. Everything below is a vendor we actually use in production, not a permissive catch-all list.
1.What a sub-processor is
A sub-processor is a third party we engage to process personal information on our behalf, in order to run the Service. Each one is bound by a written contract that limits it to our documented instructions, requires appropriate security, and imposes confidentiality obligations at least as protective as ours.
This page is the current, authoritative list. It is referenced by the Privacy Policy and by our data processing addendum, which is available to business customers at privacy@smartordercapture.com.
2.Current sub-processors
| Sub-processor | Purpose | Data processed | Processing location |
|---|---|---|---|
| Stripe, Inc. | Payment processing, subscription billing, marketplace payouts, tax calculation | Name, email, billing address, card details (collected directly by Stripe), transaction and subscription records | United States |
| DigitalOcean, LLC | Application and database hosting; Spaces object storage for screenshot actions | All customer data stored by the Service, including any screenshots a workflow uploads | United States |
| SMTP2GO (Cloudsmith Ltd) | Transactional email — verification, password reset, invitations, failure digests | Recipient email address, name, message content and delivery events | United States and European Union |
| Google LLC — Firebase Cloud Messaging | Push notifications to paired Android devices, including cloud-initiated workflow triggers | Device push token and the notification payload (a workflow identifier; no screen content) | United States |
| Cloudflare, Inc. | Turnstile bot mitigation on authentication endpoints; network and DNS services | IP address, user-agent and challenge signals | Global edge network |
| PostHog, Inc. | Server-side product analytics — only if enabled for the deployment | Pseudonymous user identifier and product events | United States (or European Union, depending on configured region) |
3.Tools we run ourselves
These are not sub-processors — the data stays on infrastructure we control — but they process personal information, so we list them for completeness.
| Component | Purpose | Data processed |
|---|---|---|
| Umami (self-hosted) | Website analytics — cookieless page views and product events | Aggregated page views and event names; no cookie or cross-site identifier |
| Bugsink (self-hosted) | Error monitoring for the web application, the API and the Android application | Error messages, stack traces, page or endpoint, browser and OS versions. Personally identifying request data is disabled by default and sensitive headers are scrubbed |
| PostgreSQL and Redis (self-managed) | Primary database and job queue | All customer data stored by the Service |
4.What is not on this list
Destinations you configure inside a workflow are not our sub-processors. If an action calls your webhook, writes to your spreadsheet, sends an SMS through your carrier, or uploads a screenshot to your own storage bucket, the data goes from your device to that destination at your instruction. You are the controller of that transfer, and the recipient’s own terms and privacy notice apply.
Applications your workflows interact with on the device are likewise not our sub-processors. We do not receive their contents.
5.International transfers
Where a sub-processor processes personal information outside the EEA, the UK or Switzerland, we rely on the European Commission’s Standard Contractual Clauses and the UK International Data Transfer Addendum, supplemented by encryption in transit and at rest and by access controls. Copies of the relevant transfer mechanisms are available on request at privacy@smartordercapture.com.
6.Changes and how to object
We will update this page before a new sub-processor begins processing personal information, and we will change the “Last updated” date above. Business customers with a data processing addendum in place can subscribe to change notifications by emailing privacy@smartordercapture.com; we give at least 30 days’ notice before a new sub-processor is engaged.
If you have a reasonable, documented objection to a new sub-processor on data-protection grounds, tell us within that notice period. We will work with you to find an alternative, and if we cannot, you may terminate the affected subscription and receive a refund of the unused prepaid portion.