Data Handling Disclosure
This technical disclosure outlines the architecture, channels, data flows, storage security, access controls, and deletion mechanisms implemented by Yield Force. It is published for transparency and for the platform partner programs we use or have applied to: Meta, Google, Shopify, TikTok and LinkedIn.
1. Data We Currently Collect & Process
Yield Force ingests only scopes strictly required for real-time customer conversation resolution and order lookup, plus advertising campaign data when a business chooses to connect its own Google Ads account:
WhatsApp & Meta Channels
Scope: WhatsApp Cloud API, Instagram Messaging, FB Messenger
- Inbound customer message bodies, media attachments, timestamps
- Delivery receipts and message status updates (sent, delivered, read)
- Customer telephone numbers (hashed/masked in audit logs) and sender IDs
- Merchant WhatsApp Business Account (WABA) IDs and phone number IDs
Shopify Storefront & Admin
Scope: read_orders, read_products, read_inventory
- Order identifiers, fulfillment status, and carrier tracking links
- Product catalog details (titles, variants, pricing, inventory levels)
- Store policy URLs (returns, shipping terms, FAQ guidelines)
- Zero payment credentials or credit card PANs are ever accessed or stored
Google Ads (connected by the business)
Scope: https://www.googleapis.com/auth/adwords (OAuth 2.0, granted by the business)
- Google Ads account identifiers, campaign names and status (enabled / paused)
- Campaign performance metrics (impressions, clicks, cost, conversions), displayed to the business that connected the account
- Pause / enable instructions, sent to Google Ads only when an authorised user of the business requests them
- Google Ads data is stored per customer and never shared across customers; the access token is kept in a secrets vault
- When you ask our AI agents to work with your campaigns, relevant Google Ads data may be included in prompts sent to Google Vertex AI in the United States
- No Gmail, Drive, Contacts or other Google services are accessed
Use of information received from Google APIs adheres to theGoogle API Services User Data Policy, including the Limited Use requirements. Details:Privacy Policy, Section 8.
Upcoming Channel Integrations (Not Yet Active)
TikTok For Business
Status: Application pending platform approval
Intended scope: Lead Generation API, Campaign Reporting
- Aggregated campaign ad metrics (impressions, clicks, conversions)
- Instant Lead Form webhook payloads for automated conversation dispatch
- Lead timestamps and basic lead submission attributes
LinkedIn Marketing Solutions
Status: Application pending platform approval
Intended scope: Lead Gen Forms API, Ad Analytics
- Aggregated campaign performance metrics and engagement figures
- Lead Gen Form submission data for automated routing to merchant CRM
- Form metadata and consent timestamps
Data processing under these integrations will commence only upon:
- Platform approval of Yield Force's developer application; and
- Explicit merchant-level opt-in and channel activation.
This page will be updated to reflect active status at that time.
2. Storage, Cryptography & Encryption Standards
Encryption at Rest
All relational databases, conversational transcripts, vectors, and backups are encrypted at rest using industry-standard AES-256 encryption via hardware security modules (HSM) managed within our Supabase EU infrastructure.
Encryption in Transit
All data in transit across public networks is enforced via modern TLS (TLS 1.2 / TLS 1.3) cryptographic protocols with Perfect Forward Secrecy (PFS). Unencrypted plaintext HTTP traffic is strictly prohibited and automatically redirected.
Geographic Region
Servers: Paris, France. Database: Stockholm, Sweden. AI processing (Google Vertex AI) and document staging (Google Cloud Storage): United States.
3. Access Controls & Sovereign Multi-Tenancy
Yield Force enforces database-level isolation between merchants through PostgreSQL Row-Level Security (RLS):
- Tenant Partitioning via
sovereign_key: Every database query is scoped by an immutable, cryptographically generated sovereign key. Cross-tenant queries are rejected at the PostgreSQL query engine layer. - Zero Cross-Tenant Access: Merchant A's conversational threads, orders, and knowledge embeddings can never be accessed, queried, or leaked to Merchant B.
- No Model Training on Customer Data: We do not use customer data to train our system. The data remains the customer's data. We never sell data.
4. Data Deletion & GDPR Cascade Purge
We provide automated, end-to-end data erasure capabilities honoring merchant control and individual data subject requests:
- Merchant App Uninstall: Receipt of Shopify's
app/uninstalledwebhook triggers an automated GDPR cascade delete. All merchant credentials, active sessions, conversation logs, and catalog cache are permanently purged within 30 days of uninstall, in alignment with Shopify's mandatory GDPRshop/redactwebhook SLA. - Shopify Mandatory GDPR Webhooks: Yield Force natively processes
customers/data_request,customers/redact, andshop/redactwebhooks with cryptographic receipt logging. - Configurable Retention: Conversations expire and are permanently purged after 90 days by default, or immediately upon ticket resolution if configured by the merchant.
- Google Ads Disconnection: A business can disconnect Google Ads at any time from the dashboard or at myaccount.google.com/permissions. Disconnecting removes the stored connection and token.
- Leaving Yield Force: When a business stops being a customer, it can download its data, and Yield Force then removes its records.
- Deletion Requests: Step-by-step instructions for customers and businesses are on our Data Deletion page.
5. Subprocessors Reference
Below is the verified registry of infrastructure partners utilized by Yield Force:
| Subprocessor Name | Function & Purpose | Hosting Region | DPA Reference |
|---|---|---|---|
| Supabase Inc. | Primary relational database, tenant auth, row-level security | Stockholm, Sweden (EU) | supabase.com/legal/dpa |
| Google Cloud (Vertex AI, Cloud Storage) | AI inference, embeddings generation, and document staging | United States | cloud.google.com/terms/dpa |
| Resend Inc. | Transactional system notifications and merchant alerts | US / Global (Standard Contractual Clauses) | resend.com/legal/dpa |
| Cloudflare Inc. | Edge routing, Web Application Firewall (WAF), DNS, DDoS protection | Global Edge Network (EU Data Localization) | cloudflare.com/dpa |
| Meta Platforms Ireland Ltd. | WhatsApp Cloud API, Instagram Messaging API, Facebook Messenger API | Ireland (EU) | Meta Business Platform DPA |
| Shopify Inc. | Store API and webhook synchronisation (catalog, orders, inventory) | Canada / Global (EU SCCs) | shopify.com/legal/dpa |
| Google LLC (Google Ads API) | Source of campaign data a business chooses to connect; receives pause/enable instructions | USA / Global (EU SCCs) | Google Ads Data Processing Terms |
6. Security & Vulnerability Reporting Contact
For security audits, platform compliance documentation, or vulnerability disclosure under responsible disclosure guidelines, please contact our security team directly:
Data Protection & Security Enquiries: dev@yieldforce.dev
Operating Company: Gaia Holdings Limited
Governing Law: Uganda
Address: Nakasero IV, Nakasero, Kampala 10270, Uganda · P.O. Box 169035, Kampala GPO
Phone: +256 762 600 505 · +256 701 856 687
PGP encryption key available upon email request.