Legal
Privacy policy
What Tweetsim collects, what it doesn't, and where the images you make are processed.
Last updated: September 28, 2026
About Tweetsim
Tweetsim provides mock tweet and account-status generators for entertainment, parody, and creative use, plus a tool for converting public X/Twitter posts to images. This policy explains how information is handled when you use the site. Tweetsim is operated by Enki Studios LLC, which is responsible for the information handled on this site. Contact us at shri@openspeechai.com.
Our Terms and Conditions explain acceptable use. An entertainment purpose does not remove anyone's privacy or other legal rights.
Text, Photos, and Generated Images
The mockup editors process the text, names, handles, engagement counts, and photos you enter in your browser. Selected image files are read locally. The current editors do not upload this content to a Tweetsim database, and image exports are generated in your browser. Tweetsim does not automatically publish your creations to X or another social network.
Editor state is not intentionally saved by the app between visits. Your browser may retain cached data or restore a session. Downloaded files remain on your device until you delete them; copies you share are outside our control. Avoid entering sensitive information or using someone else's personal information or images without appropriate permission or another lawful basis.
Public Posts and External Images
When you select Generate in the tweet-to-image converter, the post ID extracted from your URL is sent from your browser to the public react-tweet service at react-tweet.vercel.app to retrieve the post. Embedded photos and other media may load from X/Twitter's media services. These requests disclose your IP address and normal request information to the receiving providers. The app does not request your X password or access to private posts.
Some default images are served through GitHub-hosted resources and our hosting infrastructure. Retrieving remote images can involve network requests and caching. External services process requests under their own policies, including Vercel's privacy notice, X's privacy policy, and GitHub's privacy statement.
Analytics and Cookies
Tweetsim uses Google Analytics on the production website to understand traffic and improve the tools. It can collect page and referral information, device and browser information, approximate location, cookie identifiers, and usage events. Our custom tool events report fixed labels such as tool started, export succeeded, download initiated, or error category; they do not include entered tweet text, names, handles, uploaded images, or pasted post URLs.
Google Analytics may use cookies and similar technologies to distinguish visits and measure activity. Analytics information is not necessarily anonymous, and Google also processes information under its own policies. See how Google uses information from partner sites.
You can manage cookies through your browser and use Google's Analytics opt-out browser add-on where supported. Deleting cookies does not delete previously collected information. Where applicable law requires prior consent for optional tracking, that consent must be obtained separately; reading this policy or continuing to browse is not consent.
Advertising
Some pages contain Google AdSense ad placeholders. The site's standard AdSense loading script is currently disabled. If Google advertising is enabled, Google and its partners may use cookies or similar technologies to deliver and measure ads, including personalized ads where permitted. Advertising activation requires a review of the relevant disclosures and consent controls. See Google's advertising controls and Google's advertising information.
Hosting and Contact Information
Tweetsim uses Cloudflare infrastructure to deliver the site. Hosting and security providers may process IP addresses, requested URLs, timestamps, browser information, and technical logs for delivery, reliability, and abuse prevention. See Cloudflare's privacy policy.
If you email us, we receive your email address, message, and any attachments you choose to send. We use these to respond to questions, investigate reports, and manage related follow-up. Please do not send passwords or unnecessary sensitive information.
Purposes, Sharing, and Retention
Information is processed to provide requested tools, respond to support requests, understand usage, and maintain security. Where data-protection law requires a legal basis, relevant bases may include providing a requested service, legitimate interests in support and security, legal obligations, and consent for optional processing where required. This does not override any separate cookie-consent requirement.
Information may be processed by the providers described above or disclosed where legally required. Providers may process information outside your country. Their policies and applicable service agreements describe their processing and transfer safeguards.
Browser editor content is handled as described above. Support correspondence is retained as needed to resolve the request and related disputes or legal obligations. Analytics and infrastructure records follow the applicable provider retention settings and policies; they are not necessarily deleted when you close the site. No method of storage or transmission is completely secure.
Your Rights and Questions
Depending on your location and applicable law, you may have rights to access, correct, delete, or obtain a copy of personal information, restrict or object to processing, withdraw consent, and complain to a data-protection authority. Contact shri@openspeechai.com with your request. We may need proportionate information to verify your identity and locate relevant records. We cannot retrieve or delete copies stored solely on your device or by people you shared them with.
The service is not directed at children under 13. If you believe a child has provided personal information to us, please contact us so we can investigate and address it.
Updates
We will update this policy as our practices change and show the revision date above. Material changes will be highlighted on this page. Any new consent required by law must be obtained separately.