Legal
Privacy Policy
Effective November 2026
Who we are
TinShe Mirage is a personal, non-commercial project run by an individual developer under the name TinShe, not a registered company ("we", "us", "our"). We provide a mock, OpenAI-compatible image generation API for developers to use during development and testing. This policy explains what data we collect, why, and how we handle it.
What we collect and why
- Email address
- Used solely for passwordless authentication (magic links). We do not send marketing emails. Your email is stored by Supabase as part of your sign-in, sent through Resend only to deliver your sign-in links, and never sold or shared with third parties for marketing. The same sign-in works on other TinShe sites you've been given access to (TinShe Storyboard, TinShe Travel); each site keeps its own data, and the others can't see your Mirage key or usage.
- Daily request counts
- We record how many API calls your key makes per UTC day to enforce the daily limit (1440 requests). This counter is associated with your account and visible to you on the dashboard. We also record when your key was last used (shown on the dashboard); individual call timestamps are not stored.
- API key hash
- We store only the SHA-256 hash of your key — never the key itself. We cannot recover your key if you lose it. We also store the first 8 characters of the key so you can identify it in the dashboard.
- Prompts
- We do not log or store prompt text. Prompts are used only in memory to match against our image catalog and are discarded once the response is sent. One exception: when nothing matches and you ask for
urlresponses, the link to the placeholder picture contains the first 60 characters of your prompt, so it can appear in our hosting provider's request logs and CDN cache. Useb64_jsonto avoid that. - Sign-in sessions
- When you sign in, Supabase Auth records the session's IP address and browser (user agent), for security. They are kept with the session record and deleted with your sign-in.
- Server logs
- Our hosting provider (Vercel) and database provider (Supabase) may retain standard server-side logs (IP addresses, HTTP metadata) for security and abuse monitoring. These logs are subject to their respective privacy policies.
Cookies and session storage
We use essential cookies to maintain your signed-in session, managed by Supabase Auth, plus one cookie that remembers your cookie-consent choice. Neither requires consent — they're strictly necessary to run the site.
The dashboard may use your browser's sessionStorage to temporarily hold your API key within the current browser tab. If you opt in to "Remember on this device", it uses localStorage instead. This data never leaves your browser; it is used only to pre-fill the playground.
Analytics and error tracking
PostHog product analytics (pages viewed, feature usage) loads only after you accept analytics in the cookie banner, which you can reopen any time from "Cookie settings" in the footer. No advertising or cross-site tracking.
Sentry runs on every page and on our servers, without asking: it reports errors and a sample of slow pages so we can fix them, on the basis of our legitimate interest in running a reliable service. It uses no cookies, records no screen, and is set not to collect IP addresses, cookies, headers or URL query strings.
Sending feedback
The "Feedback" button sends the message you type, and your email only if you enter one, to Sentry so we can follow up or fix the bug. Nothing is sent until you press Send.
Data sharing
We do not sell, rent, or share your personal data with third parties for marketing or commercial purposes. We rely on the following sub-processors:
- Supabase — database and authentication (US, SOC 2)
- Resend — delivers sign-in emails (your email address only)
- Vercel — application hosting and edge delivery
- Cloudflare — image CDN (Cloudflare R2)
- PostHog — product analytics, only if you accept the cookie banner
- Sentry — error tracking
Each of these providers processes data only as needed to deliver the service.
Your choices (GDPR / CCPA)
Wherever you're visiting from, analytics are opt-in: we don't load them until you accept the cookie banner, and you can change your mind at any time via "Cookie settings" in the footer. We don't sell or share personal data for cross-context behavioral advertising, so there's nothing separate to opt out of under CCPA/CPRA beyond the analytics choice above.
Data retention
Your account data is retained as long as your account exists. Usage counters are kept for rolling historical purposes (no defined deletion window yet — we may prune data older than 90 days in a future update).
Your rights
You can exercise the following at any time:
- Access — view your key info and usage on the dashboard.
- Deletion — click "Delete my account" on the dashboard. This permanently removes your API key, usage data and Mirage access. Your sign-in and its sessions are deleted too, unless you still use another TinShe site with it.
- Contact — email us at hello@tinshe.com for any other privacy requests.
Security
We hash API keys with SHA-256 before storage, check on our server that you can only read and change your own key and usage, and never log or persist prompt text. The database is reached only from our server, with credentials that are never exposed client-side.
Children
This service is not directed at children under 13. We do not knowingly collect data from children.
Changes to this policy
We may update this policy. Material changes will be reflected by a new "Effective" date at the top. Continued use after changes constitutes acceptance.
Contact
Questions about this policy? hello@tinshe.com