Security Overview
Till reduces routine distribution of upstream AI provider credentials. It is a proxy control layer, not a zero-knowledge system or a replacement for your provider’s billing and security controls.
Credential design
- Provider credentials are stored as AES-256-GCM ciphertext authenticated with tenant/provider context. Plaintext credentials are never returned after save.
- New scoped tokens contain an encrypted tenant-routing reference rather than provider credentials. Legacy fixed-provider tokens remain supported during migration.
- The running service decrypts only the selected provider connection to authorize a proxied request. Database contents alone are insufficient without the separate application encryption key.
- A stolen scoped token, compromised service host, or combined database and encryption-key compromise remains security-sensitive.
- Admin keys and scoped tokens are bearer credentials. Till currently does not offer MFA, SSO, or user-level roles.
Usage-control boundary
Activation and conservative token or spend capacity are reserved before a budgeted request is forwarded, then settled to provider-reported actual usage. A token- or spend-budgeted generation request must declare max_tokens, max_completion_tokens, max_output_tokens, or Google generationConfig.maxOutputTokens. Spend-limited requests require a model in Till’s pricing table; unknown-priced models are rejected. Cost remains an operational estimate and may differ from the provider invoice, so retain provider-side budgets and alerts.
Data path
Request and response bodies transit the Till proxy and the provider selected automatically from configured connections using route/model/default signals. Till does not intentionally persist those bodies in its application database. Infrastructure may retain metadata such as IP address, route, timing, status, and errors. See the Privacy Notice.
Customer controls
- Use the smallest practical activation cap, output-token cap, and expiry.
- Apply IP allowlists only after testing the exact network path.
- Keep admin keys outside browser-shared or collaborative environments where possible.
- Revoke lost scoped tokens. Rotate provider connections when credential, host, database-plus-encryption-key, or broader account exposure is suspected.
- Monitor Till counters and upstream provider usage independently.
Assurance status
Till is an early beta and does not currently claim SOC 2, ISO 27001, HIPAA, PCI DSS service-provider, FedRAMP, or similar certification. No public penetration-test report, bug bounty, uptime warranty, or service-credit program is currently offered. Operational response commitments are published in the beta support SLA.
Report a vulnerability
Follow security.txt and email security@till.ac. Do not include live credentials, personal data, or exploit payloads in an initial report. Confirmed critical issues target acknowledgment within 60 minutes; other material security reports target acknowledgment within four business hours. See the support SLA for scope and limitations.