PRIVACY NOTICE / VERSION 2026-11-06-agent

Know what is stored.
Control what comes next.

Jordan Rule, operating as ShieldVPC, operates this service and is responsible for the personal information described here. Contact privacy@shieldvpc.com for privacy requests. This notice covers the free control-plane preview; paid workloads require a further processing assessment and applicable contracts.

1. Information and purposes

We use verified email, an identity-provider subject and workspace membership to provide accounts, authorize access and communicate about service/security or privacy requests. We record terms acceptance, proposals, assigned rental references, operational audit events, limited conversation history and privacy-request records to operate and protect the service.

Application logs are designed not to contain credentials or chat text. Cloudflare may process IP addresses, timestamps and request/security metadata. Login rate-limit buckets temporarily include an IP address to deter abuse and are removed after expiry. We do not use customer signup as permission for marketing or sell personal information.

2. Identity and essential cookies

Google Firebase Authentication handles Google and email/password authentication, email verification, password storage and recovery. ShieldVPC receives verified identity claims, not your passwords. The Firebase SDK uses temporary in-memory sign-in state and its Google popup handler. ShieldVPC uses an HttpOnly, Secure session cookie lasting up to eight hours. Only session token hashes are stored in D1. These essential cookies provide requested account/security functionality, not marketing tracking.

3. Assistant and administrative processing

The Shield assistant sends your message, up to six retained recent conversation messages and relevant tool results to Cloudflare Workers AI using the Llama 3.3 70B model. Tools can discover offers, read your workspace's rentals and prepare proposals. Never submit secrets, personal datasets, regulated information or third-party confidential material.

Up to twelve conversation messages per workspace are retained in D1 to provide continuity and restore the conversation. Unsuccessful turns may have created proposals even if no final reply was stored; review proposals before retrying. Model processing and infrastructure security metadata follow applicable provider terms. We do not promise a specific processing region or independently certify provider retention.

Owner-created site/campaign drafts and publication records may also be stored in D1. The embedded assistant cannot access them. External personal administrative agents are not connected to customer chat. Campaign delivery and recipient-list import are not provided.

4. Service providers and international processing

Providers may process data internationally. Any required data-processing agreement, transfer safeguards and region restrictions must be established before a deployment relying on them. Model licensing does not imply a separate direct customer connection to its model developer.

5. Retention and deletion

Account identity, workspace membership and accepted agreements are kept while the account is active and during necessary deletion review. Sessions last up to eight hours. The assistant retains at most twelve conversation messages per workspace; hourly cleanup removes messages older than thirty days, expired turn locks, sessions and rate-limit buckets. Proposals are removed after thirty days, drafts after ninety days and control-plane audit entries after 365 days. Published site copy remains until replaced.

Deletion requests immediately revoke sessions and lock the workspace. The operator must handle Firebase and applicable provider records, then complete deletion of workspace data, including retained chat. Completed request contact details are cleared; completed request records are removed after thirty days. Pending requests remain until resolved. Legally necessary records and provider backups may follow separate schedules; deletion from every backup is not instantaneous.

6. Your controls and requests

Use Account & privacy to export control-plane data, including retained conversation history, or request deletion. Exports include up to 10,000 recent workspace audit events and exclude credentials, other customers and independent provider logs. Contact us for older records, provider records, access, correction, objection or other applicable privacy rights. We may verify identity before acting and explain any lawful limitation.

We aim to acknowledge requests within 7 days and resolve them within 30 days, or the applicable legal deadline. If additional time or retention is necessary, we will explain it. Applicable law may give you rights to complain to a competent data protection authority. Withdrawal of optional marketing permission will not affect core service access.

7. Security, children and changes

We use tenant-scoped authorization, verified identity, protected session cookies and limited-purpose tools. These controls do not make a third-party GPU host confidential; see the Security Architecture. No service guarantees absolute security. The service is for adults 18 and older. Material changes are versioned and presented in onboarding; acknowledgment is not consent to unrelated marketing or a waiver of privacy rights.

Last updated November 6, 2026. Contact mailboxes and the privacy-request process must be monitored by the operator. Jurisdiction-specific counsel should review these initial documents before paid or regulated-data services.