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

2. Information we process

User identity and account information

Contacts and messages

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

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:

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

DataRetention
Messages, their media, and their delivery recordsThe 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 recordsLife 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 registrationFull 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 sidebar30 days
Webex event records used to avoid duplicates30 days
Operational logsAbout 30 days (Google Cloud Logging default)
Webex tokensA token revoked in Webex stops working immediately; stored tokens are deleted on request and when the Customer's subscription ends
Account, usage, and audit recordsLife 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.

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:

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