Privacy & Data Handling
A straightforward look at what we store, what we don't, and how we keep things secure.
Data Controller
TwitterAPIs operates this service. For any privacy or data-handling questions, contact emma@twitterapis.com.
We Only Store Your Email & Name
When you sign up, we store your email and name, that's it. We don't collect unnecessary personal data or build user profiles beyond what's needed for your account.
Bring-Your-Own-Credentials for Write Endpoints
TwitterAPIs uses a bring-your-own-credentials model for writes, and you choose how we handle the values. Pass your auth_token and ct0 in the request and they are used for that single call, with nothing written to disk or database. Or register a session against an API key, in which case both values are stored against that key and encrypted at rest with AES-256-GCM, and remain until you replace them by registering again. We never hold either value unencrypted. There is no OAuth token to store because we never issue one.
HTTPS Everywhere
All traffic between your app and TwitterAPIs is encrypted over HTTPS with TLS 1.2+. Connections cannot be downgraded to plain HTTP.
No Data Sold to Third Parties
We don't sell, share, or monetise your data in any way. Your usage data and account information stay with us and are only used to operate the service.
Questions about how we handle your data?
Email usNext read
Continue exploring related pages:
Twitter API security and key safety
How keys, write credentials, and data are secured: Bearer auth, TLS 1.2+, and credentials used per request or encrypted at rest.
TwitterAPIs pricing
Brand pricing page with endpoint-level costs and quick totals.
Twitter API use cases
14 use cases from sentiment analysis to lead generation.
How to get a Twitter (X) API key
Step-by-step walkthrough of the X developer console plus a 30-second alternative.
Last updated: May 2026