Sub-processor List
BeMyWords — operated by Skiwo AS Effective date: 2026-04-25 Last updated: 2026-04-25
This page lists the sub-processors Skiwo AS engages to operate the BeMyWords service. Sub-processors are third parties we rely on to deliver the Service, each bound by data protection obligations equivalent to those in our Data Processing Agreement.
We will notify customers of material changes to this list at least 30 days in advance via email to the workspace owner. Customers may object to a proposed change within that period; if the objection cannot be resolved, the customer may terminate their subscription.
Infrastructure
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Heroku (Salesforce) | Application hosting, managed Postgres, managed Redis, file attachments, automated database backups | All workspace content, account data, operational data, uploaded screenshots, system error logs | EEA |
Heroku is the only cloud-infrastructure sub-processor Skiwo AS engages directly. Heroku in turn runs on AWS infrastructure under Heroku's commercial terms; that is Heroku's choice of underlying provider, not a separate engagement by Skiwo.
Email delivery
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Amazon Simple Email Service (SES) | Transactional email — account notifications, invitations, password resets | Email addresses, email content | EEA (eu-central-1) |
Machine translation and vision
| Sub-processor | Purpose | Data processed | Location | Safeguards |
|---|---|---|---|---|
| Anthropic (via Heroku Inference) | Machine translation via Claude; vision-based string matching when a customer uploads a screenshot for in-context translation | Source strings submitted for translation; uploaded screenshot images and the project's source-language strings, when the screenshot feature is used; context provided by customer | Routed via Heroku (EEA) | Anthropic API terms (no training on submitted data); Heroku acts as delivery path |
BeMyWords does not use OpenAI, DeepL, or any other external MT providers. Claude is accessed through Heroku's inference routing; customer data is processed by Anthropic under their commercial API terms, which exclude the data from model training.
Screenshot images are forwarded to Anthropic for vision processing and discarded when the request returns. Only the resulting list of extracted strings is persisted on the Service; the image itself is not stored on Skiwo's database, logs, backups, or filesystem. The uploader's browser may keep a local copy in IndexedDB for up to 8 hours so the image remains visible during a single session; that local cache is the user's browser, not a sub-processor.
Billing and invoicing
Billing is not active during the private-beta period; pilot customers are invoiced manually outside the Service. When automated invoicing is enabled, it will be processed by Payout Partner AS (a Skiwo AS group company, Norway/EEA) and this list will be updated, with at least 30 days' notice to active customers.
Error tracking and observability
Error tracking is handled internally — exception details are persisted to the application database (the system_errors table) on Skiwo's own infrastructure. No third-party error-tracking service (e.g. Sentry, Bugsnag, Rollbar) is engaged, so customer data in stack traces stays within Skiwo's systems.
Notes on this list
- This list is the canonical statement of BeMyWords's sub-processors. If the list on the Service's public website differs from this file, this file prevails for active customer DPAs.
- Sub-processors engaged only for Skiwo AS's own internal operations (e.g. accounting software) that do not process customer data are not listed here.