Scribe Privacy Policy
Last updated: November 19, 2026
This Privacy Policy describes how Virtual Guardians, LLC ("Virtual Guardians," "we," "us") collects, uses, and protects information in connection with Scribe, our business texting service that sends and receives text messages (SMS and MMS, and RCS where it is turned on) on a customer's own Webex Calling phone numbers. Scribe includes the web application at scribe.virtual-guardians.com, the "Scribe texting" embedded sidebar app inside the Webex App, the Scribe bot and Webex integration that bring texts into Webex spaces, the administrative consoles, and the text registration (10DLC) tools (together, the "Service").
Scribe is a business-to-business service. We provide it to companies (our "Customers"), whose staff ("Users," such as agents and administrators) use it in the course of their work to text the Customer's own contacts ("Contacts"): the Customer's clients, prospects, and other people who text the Customer's business numbers.
1. Our two roles
- As a processor (service provider). Text messages, Contacts, media, and the Customer's texting records flow through Scribe on behalf of, and under the instructions of, the Customer that subscribed to the Service. The Customer decides whom it texts, what it sends, and how long Scribe keeps its messages.
- As a controller. We are responsible for the account, billing, and support information we need to run our own business (for example, administrator contact details and subscription and usage records).
2. Information we process
User identity and account information
- For each User: name, work email address, and the User's Webex identity (Webex person ID, Webex organization ID, email address, and display name), which Webex provides when the User signs in with Webex or opens the Scribe texting sidebar;
- The User's role and the business numbers assigned to the User;
- Organization details: company name, Webex organization ID, the Customer's business phone numbers, and the Customer's settings (including its message retention period).
Contacts and messages
- Contacts: phone numbers, names, companies, and notes that Users enter or import, and, where the Customer uses it, the caller name that the telephone network returns for a phone number;
- Message content: the text of messages sent and received, the time of each, which User sent it, and its conversation;
- Media: pictures and other files sent or received as MMS, stored in a private Google Cloud Storage bucket and shown to Users only through short-lived signed links;
- Delivery metadata: the Customer's Twilio phone numbers, message identifiers, and delivery status and error codes reported by Twilio and the carriers;
- Consent records: opt-in and opt-out (STOP) records for each Contact, including when and how consent was given or withdrawn, and, where the Customer uses a Scribe-hosted opt-in form, the name, phone number, and consent the person submits on that form, with the IP address it was sent from and the page the form was on.
Webex spaces
When a Customer turns on Webex texting, Scribe's bot creates Webex spaces for conversations and posts incoming texts into them, and Scribe reads the messages Users write in those spaces so it can send them as texts. Scribe stores the Webex space and message IDs it needs to link a conversation to its space. Webex also notifies Scribe of messages, and of people leaving or being removed, in a connected User's other spaces; Scribe drops those at once without storing them. Messages posted in Webex spaces are also kept by Cisco Webex under the Customer's own Webex agreement and settings.
Text registration (10DLC) information
To register a Customer's texting program with the carriers, Scribe collects the Customer's business details: legal business name, business type and industry, address, website, the name and contact details of an authorized representative, the federal tax ID (EIN), sample messages, and the addresses of the Customer's privacy, terms, and opt-in pages. These are sent to Twilio for brand and campaign registration with The Campaign Registry and the carriers. The full EIN is kept in Google Secret Manager; our database keeps only its last four digits. It is deleted after the registration uses it, or after 60 days if it is never used.
Authorization tokens and keys
Scribe stores the Webex tokens that Users grant it and each Customer's Twilio credentials in Google Secret Manager; our database holds only the name of each secret. Scribe never stores passwords: sign-in always happens on Webex's own pages. A token a User revokes in Webex stops working immediately. We delete stored tokens on request and when a Customer's subscription ends.
Technical and diagnostic information
- Service logs: tenant, user, and message identifiers, timestamps, IP address and browser type, and processing and delivery status, kept for troubleshooting. Sign-in links and secrets are masked in logs; logs never contain message text or tokens;
- Diagnostics a User chooses to send from the sidebar (browser and Webex App version, sign-in state, and error codes);
- Web push subscriptions for Users who turn on notifications;
- Audit records of administrative actions (who did what, and when).
3. How we use information
We use the information above only to provide, secure, support, and bill for the Service: to send and receive the Customer's texts, show them to the Customer's Users, register the Customer's texting program, keep consent and opt-out records, notify Users of new messages, and fix problems. We do not use personal information for any other purpose. In particular:
- We do not sell personal information, and we do not share it for cross-context behavioral advertising;
- We do not use message content or Contacts to train AI or machine-learning models;
- We do not text a Customer's Contacts for our own purposes or build a marketing list from them;
- We use no advertising, analytics, or behavioral tracking technologies;
- We do not make automated decisions that produce legal or similarly significant effects concerning individuals.
4. Cookies and browser storage
Scribe uses only essential cookies: a session cookie that keeps a User signed in and short-lived cookies that protect sign-in and registration flows. Scribe's own cookies are HttpOnly. In addition, our hosting provider, Google Cloud, sets a load-balancing cookie (named GAESA) on every page of scribe.virtual-guardians.com, including this one, so that a browser keeps reaching the same server; it identifies no one and is not used for advertising. None of these cookies is used to track anyone across other sites, and Scribe sets no advertising or third-party tracking cookies. The installable web app stores its own interface files in the browser so it loads quickly.
5. How long we keep information
| Data | Retention |
|---|---|
| Messages, their media, and their delivery records | The Customer's retention setting (365 days unless the Customer chooses between 1 day and 10 years); deleted automatically each day once older |
| Contacts and consent and opt-out records | Life of the Customer's subscription, because opt-out records must be kept to honor STOP; deleted at the end of the subscription as described below |
| EIN collected for text registration | Full EIN deleted after the registration uses it, or after 60 days if it is never used; its last four digits stay with the registration record |
| Diagnostics sent from the sidebar | 30 days |
| Webex event records used to avoid duplicates | 30 days |
| Operational logs | About 30 days (Google Cloud Logging default) |
| Webex tokens | A token revoked in Webex stops working immediately; stored tokens are deleted on request and when the Customer's subscription ends |
| Account, usage, and audit records | Life of the Customer's subscription; usage and billing records as required by law |
When a Customer's subscription ends, we delete its messages, media, Contacts, and Webex links within 90 days, except records we must keep by law. Copies Twilio and Cisco Webex keep under their own services are governed by the Customer's settings and agreements with them.
6. Who we share information with (sub-processors)
We use the following service providers to run Scribe. Each receives only what it needs for its part of the Service and is contractually bound to protect it.
- Twilio Inc. carries every text message and its media to and from the carriers, reports delivery status, looks up caller names and line types for phone numbers where the Customer uses those features, and registers the Customer's brand and campaign (10DLC) with The Campaign Registry and the carriers.
- Google LLC (Google Cloud Platform) hosts Scribe in the us-east1 (South Carolina, USA) region: Cloud Run (the application), Cloud SQL (the database), Cloud Storage (media), Secret Manager (tokens, credentials, and EINs), and Cloud Logging.
- Resend delivers Scribe's service emails (such as administrator notices) to Users' work email addresses.
- Anthropic PBC reviews the Customer's public website, privacy, terms, and opt-in pages against carrier registration rules, and reads business details from registration information the Customer sends us, so we can prepare the Customer's text registration. We do not send text message content or Contacts to Anthropic, and Anthropic does not use this information to train its models.
- Cisco Webex provides the Webex App, sign-in, and the spaces where Scribe posts texts, under the Customer's own agreement with Cisco. Scribe exchanges data with Webex only as the Customer's administrators and Users authorize.
- Web push services. When a User turns on notifications, a short preview of a new message is delivered through the push service of the User's browser (for example Google, Apple, Mozilla, or Microsoft), encrypted so the push service cannot read it.
We may also disclose information if required by law, or to protect our rights, our Customers, or the public; we will notify the affected Customer first whenever we are legally permitted to. In a merger or sale of our business, information may be transferred with notice where lawful, and the successor remains bound by this Privacy Policy until a replacement takes effect. We will notify Customers before adding or replacing a sub-processor.
7. Security
All traffic is encrypted in transit (HTTPS/TLS). Webhooks from Twilio and Webex are verified by their signatures. Tokens, credentials, and EINs are kept in Google Secret Manager, media in a private bucket reached only by signed links, and the application keeps each Customer's data separate from every other Customer's. Administrative access is limited to authorized personnel and is audit-logged. No method of transmission or storage is completely secure, but we use industry-standard measures, and we will notify affected Customers without undue delay if we become aware of a personal-data breach.
8. Your rights: access, correction, deletion, and transfer
You may ask us to:
- Access the personal information Scribe holds about you;
- Correct information that is inaccurate;
- Delete your personal information;
- Transfer your information: receive a copy in a portable, machine-readable format (for example, a conversation exported as a CSV file) so you can move it to another service.
Send your request to info@virtual-guardians.com. We will verify the request and respond within 30 days. Because Scribe processes messages and Contacts on behalf of the Customer, we may pass a request about a Customer's data to that Customer (your employer, or the business you texted) and help it respond. To stop receiving texts from a business, reply STOP to any of its messages. We do not discriminate against anyone for exercising privacy rights. We act as a "service provider" for Customer data under the California Consumer Privacy Act, and we do not sell or "share" personal information as that law defines it.
9. Where data is processed
Scribe is operated from the United States and hosted in the us-east1 Google Cloud region. If you use the Service from outside the United States, your information is transferred to and processed in the United States.
10. Children
Scribe is a workplace tool and is not directed to children under 16. We do not knowingly collect personal information from children.
11. Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version at this address and update the "Last updated" date; for material changes we will also notify Customer administrators.
12. Contact us
Virtual Guardians, LLC
3045 Lochgreen Circle, Leland, NC 28451, USA
info@virtual-guardians.com ·
(910) 530-1600