Privacy Policy

This Privacy Policy explains how Jame Agent OS ("we," "our," or "us"), operating as a secure stateless gateway application, handles client data during transit to the Meta Graph API (Facebook & Instagram), and other destination networks. We operate strictly as a data-neutral connector, facilitating safe endpoint transmission without persistent local storage.

1. Absolute Stateless Architecture Commitment

Unlike typical SaaS platforms that store User Access Tokens, Page Access Tokens, and media payloads inside persistent databases, Jame Agent OS utilizes a zero-retention architecture:

• Transient Memory Transmission: User credentials and payloads are kept exclusively within your self-hosted webhook's active HTTPS request lifecycle. They are written only to ephemeral volatile memory (RAM) and are immediately garbage-collected upon transmission success or failure.
• No Databases: We do not configure or maintain user databases, data disks, log collectors, or indexing clusters that retain access keys.
• No Server Logs of Tokens: We actively strip sensitive HTTP Authorization headers and query parameters (such as access_token) before any debugging or routing logs are stored in system health outputs.

2. Information Handled in Real-Time Transit

During the momentary transit window (typically less than 1.5 seconds), the gateway temporarily coordinates:

• Webhook Post Payloads: Text captions, image links, video URLs, and target resource group identifiers.
• API Credentials: Ephemeral or Long-Lived System User Access Tokens configured directly in your self-hosted workflows (e.g. n8n, Make).
• Client Metadata: Client IP addresses and routing speeds for basic security and DDoS prevention (expelled hourly).

3. Meta Data Deletion Alignment

Because Jame Agent OS does not store, index, or retain any personal data or access tokens, there is no database for us to delete information from. However, we provide clear step-by-step guidance on how users can revoke access permissions directly via their Facebook profiles, ensuring real-time de-authorization in compliance with Meta's developer program guidelines. Detailed instructions are available on the Data Deletion Page.

4. Direct Third-Party Transit

All communications processed by Jame Agent OS are routed securely over HTTPS (TLS 1.3) directly to destination server clusters:

• • https://graph.facebook.com/*
• • https://graph.instagram.com/*

We do not rent, sell, or proxy data transit payloads to any other advertisement platforms or analytical brokers.

5. DPO and Jurisdiction

Our operations align with the strictest guidelines of user control and security. For legal inquiries, please contact our appointed Data Protection Officer mapped in Texas, United States of America at: