Who Else Touches Your Data
Every company RuleInside and ElevenLabs use to deliver the service. What each one handles, where it’s processed, and the safeguard that covers the transfer.
Every sub-processor listed · What each one handles, and where · 14 days’ notice before changes
Ruleinside LLC (trading as RuleInside)
Wyoming filing ID 2023-001209068 · 30 N Gould St, Ste 32376, Sheridan, WY 82801, United States of America
Contact: info (at) ruleinside.com
RuleInside uses the companies below to deliver the service. Where we act as a processor for a merchant, these are our sub-processors under Article 28 GDPR. Each is bound by a written contract imposing data protection obligations substantially equivalent to those we owe our merchants, and we remain fully liable for their performance.
How you are told about changes
We give at least 14 days' notice before adding or replacing a sub-processor. Notice is given by updating this page and writing to your registered contact address.
You may object on reasonable grounds relating to data protection within that period. If we cannot resolve the objection together, you may terminate the affected part of the service without penalty and be refunded any fees pre-paid for the terminated portion.
Engaged directly by RuleInside
| Sub-processor | What it does | What it receives | Where | Transfer safeguard |
|---|---|---|---|---|
| ElevenLabs | Runs the voice agent: speech recognition, turn-taking, speech synthesis, conversation storage, and places cart reminder calls | Everything spoken on a call, and the transcript. For a store that uses cart reminder calls: the shopper's phone number, the store's name, the cart and its total, and a link back to the cart, kept for a year with the record of the call. | United States | EU-U.S. Data Privacy Framework, Swiss-U.S. Framework, UK Extension |
| Supabase | Database, secrets storage, file storage | The platform's stored data | Ireland | EU-hosted; no transfer arises |
| OpenAI | Generates the search embedding when a shopper asks about a product | The shopper's product query | United States | Standard Contractual Clauses |
| Stripe | Merchant billing | Merchant billing identity. No shopper data. | United States | Standard Contractual Clauses |
| Resend | Email we send to merchants; the confirmation email a shopper receives after asking a store's agent for a refund; and, for a store that uses cart reminders, the reminder emails, the receipt of the shoppers' replies and our forwards of them to the store, from a separate Resend account that RuleInside uses only for that, shared by every store that uses cart reminders; and the daily campaign report we email to a store's owners on each day one of its phone campaigns made calls | Merchant email addresses. For a refund request: the shopper's name, email address, order number, refund amount and what they said about the refund. For a cart reminder: the shopper's email address, the store's name and the cart, and any reply the shopper sends, in full (sender address, subject, text and attachments). For a daily campaign report: for each contact who booked an appointment or a call-back, or whose booking or call-back did not go through, or who asked for a colleague, their name and phone number, with the appointment's day, time and address or the call-back's time | United States | Standard Contractual Clauses |
| Better Stack | Operational monitoring and alerting | Alert data, which carries a store identifier and can carry a contact identifier | United States | Standard Contractual Clauses |
| Google (Google Workspace) | Hosts RuleInside's own mailbox | A copy of each daily campaign report (see Resend above) | Any country where Google or its sub-processors keep facilities | Standard Contractual Clauses, or another transfer solution Google adopts under its data processing terms |
| Vercel | Hosts the merchant portal | Request metadata | United States | Standard Contractual Clauses |
Where a store brings its own phone number, its calls, reminder calls included, are carried by the store's own telephone provider.
Engaged by ElevenLabs
These are not our direct sub-processors. They are engaged by ElevenLabs, and our obligations as to them flow through our contract with ElevenLabs rather than from any direct relationship. We name them because a merchant assessing risk needs to see the whole chain, not the first link.
| Party | What it does |
|---|---|
| Twilio | Telephone connectivity for inbound and outbound calls |
| Meta (WhatsApp) | WhatsApp message delivery for a store whose messaging runs through ElevenLabs rather than through its own connected number. |
| The language model that composes the agent's replies, on some agents | |
| Anthropic | The language model that composes the agent's replies, on other agents |
| OpenAI | The language model that composes the agent's replies, on some agents |
ElevenLabs maintain their own list at compliance.elevenlabs.io.
WhatsApp (Meta)
Where a store connects its own WhatsApp Business Account, the store accepts WhatsApp's business terms itself, and WhatsApp (WhatsApp Ireland Limited for a store in the European Economic Area, WhatsApp LLC elsewhere) processes the messages as the store's processor. RuleInside sends and receives messages through it on the store's instruction. WhatsApp states that it transfers European data to the United States under the EU-U.S. Data Privacy Framework. Where the store's messaging runs through ElevenLabs, Meta is engaged by ElevenLabs (table above).
Which language model answers
The language model is selected per agent. The platform may complete a reply on a different provider's model than the one configured, when the selected model is slow to respond. The table above therefore names every provider that may handle a conversation, not only the one configured for a given agent.
Where your data is processed
Our database is in Ireland, inside the European Economic Area. The voice pipeline is processed in the United States: that is where call audio and the primary transcript are handled.
Our email, including cart reminder emails and the shoppers' replies to them, goes through Resend, which stores its data in the United States. The copy of each daily campaign report that we keep in our own mailbox is held by Google (Google Workspace), which may store it in any country where Google or its sub-processors keep facilities.
Transfers to the United States rely on the recipient's Data Privacy Framework certification or on the Standard Contractual Clauses, both permitted mechanisms under Chapter V of the GDPR.
EU-only processing of call audio is not currently available. If your organisation requires it, tell us before you sign rather than afterwards.
Questions: info (at) ruleinside.com.