1. Introduction
TokenGate is operated by Salvador Aceves ("TokenGate", "we", "us", or "our"). This policy explains the information TokenGate handles when a customer manages an account or routes application traffic through the service. Our public trust page gives the same data path in a shorter, end-user-facing format.
2. Information We Collect
Customer account data
We keep a customer's email address, organization and project names, authentication records, account preferences, billing status, and service-related communications. We use this information to operate and secure the customer's TokenGate account.
Keys and published instructions
Customers may save AI-provider keys and the system instructions or request templates they intend to publish. Provider keys are encrypted using envelope encryption and decrypted only when TokenGate makes a provider request for that customer.
Usage metadata
Detailed usage records contain token counts, model and prompt references, timestamps, authorization status, a cost estimate or provider-reported cost when available, and a project-scoped installation fingerprint. They do not contain the end-user request or AI response.
Installation identity
A customer app must send a random UUID v4 in the installation identity header. TokenGate validates it and applies a secret-keyed, project-specific function before persistence. TokenGate does not use an email address, username, phone number, or customer database ID to meter an installation.
An ordinary in-place app update normally keeps that UUID. Uninstalling the app or clearing its storage creates a new installation and a new allowance.
Google Play Subscriptions
For applications that offer a Google Play subscription, TokenGate receives a purchase token long enough to verify and acknowledge the purchase. We store a project-scoped keyed digest of that token, the anonymous installation fingerprint, plan, entitlement state, product and base-plan identifiers, expiry, and verification timestamps. We do not store the raw purchase token, Google account, email, profile, order ID, billing address, payment method, price, billing region, or cancellation survey.
Technical and security data
Routine reverse-proxy access logging is disabled. If limited logs are needed to investigate a security incident, we may process IP address, request path without URL parameters, response status, and time. We do not intentionally place request or response bodies, credentials, authorization headers, raw installation UUIDs, or URL parameters in those logs.
3. Application Traffic
TokenGate receives end-user request content and the selected AI provider's response so it can complete the customer's request. This conversation content is processed in memory and is not persisted in TokenGate client, usage, or authorization-cache records.
TokenGate stores the published instructions that a customer intentionally configures. Published instructions are separate from conversation content. If a customer enables its own authorization webhook, TokenGate forwards the installation UUID and the payload fields the customer selects, but stores only the allow or deny result and an expiring cache-key fingerprint.
4. How We Use Your Information
We use the collected information to:
- Provide, maintain, and improve our services
- Process transactions and manage your account
- Track and enforce usage quotas
- Send service-related communications
- Detect and prevent fraud or abuse
- Meet legal obligations that apply to us
5. Data Retention
- Detailed usage events are retained for 90 days.
- Monthly app-level totals without installation fingerprints are retained for 24 months.
- Expired authorization-cache entries are deleted promptly.
- Inactive installation fingerprints expire after 90 days unless they carry an explicit block or custom quota.
- Limited incident access logs, when generated, are retained for no more than seven days.
Customer account, billing, and security records may require different retention periods while an account is active or when law, fraud prevention, dispute handling, or service security requires them.
6. Data Security
We implement appropriate technical and organizational measures to protect your personal information, including:
- Envelope encryption for stored API keys
- Secure HTTPS connections for all data transmission
- Access controls and authentication mechanisms
- Project-scoped access and management credentials
However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security.
8. Access, Correction, and Deletion
Depending on your location, you may have the right to:
- Access the personal information we hold about you
- Request correction of inaccurate data
- Request deletion of your data
- Object to or restrict certain processing
- Data portability
A TokenGate customer may contact us through our support page. An end user should first contact the publisher of the app they use. The publisher can authenticate to TokenGate and forget the relevant installation, which deletes detailed usage and any custom quota. A deny-only fingerprint may remain while an abuse block is active.
9. Cookies
We use essential cookies for authentication and session management. These cookies are necessary for the service to function and cannot be disabled.
10. International Data Transfers
Your information may be transferred to and processed in countries other than your country of residence. Customers are responsible for determining whether TokenGate and their selected AI provider are suitable for the transfers their application makes.
11. Children and Regulated Use
TokenGate does not offer children's-privacy, HIPAA, medical, biometric, or financial-compliance commitments. Customers must not send regulated data that requires those contracts or controls. Non-retention reduces exposure; it does not make every use case compliant.
12. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new policy on this page and updating the "Last updated" date. Your continued use of the Service after changes constitutes acceptance of the updated policy.
13. Contact Us
If you have questions about this Privacy Policy or our data practices, please contact us through our support page.