Privacy policy

• Your sign-in identity (email) is stored separately from your public profile.
• Published prompts, results, comments and your profile are public. Drafts, bookmarks, collections, notification settings and notifications are private to you.
• No analytics run unless the operator configures a provider, and even then only coarse event names and public identifiers are sent.
• Only session cookies are used; there are no advertising or tracking cookies.
• You can export your data as JSON and delete your account from Settings.

• Sign-in identity. Your email address and sign-in method (email code) are held by Supabase Auth, separately from your profile. Your email address is never shown publicly and is not part of any public read.
• Profile (public). Username, display name, bio, avatar image, join date and public counts (published prompts, public results).
• Content you publish (public). Prompts and every published version (title, summary, instructions, variables, usage notes, category, tags), results (model attribution, settings, variable values, the resolved input, output text or images, notes, excerpt/edited flags, source link), comments and replies, together with who published them and when.
• Votes. Your up- or downvote on a prompt. Only aggregate counts are public; the direction of your own vote is visible to you alone.
• Private state (never public). Drafts and unpublished working versions, bookmarks, collections, notification preferences and notifications. These never enter feeds, search, social previews, notifications to other members or telemetry.
• Reports you file. Reason and details, stored with your account and visible to moderators together with your username. The reported member never sees who reported.
• Moderation records. An append-only log of moderation actions (who acted, on which item, the reason or note, the status before and after). Prompt, output and profile text are not copied into this log.
• Abuse-prevention counters. Per-account counters for rate limits and request de-duplication (action name, time window, request fingerprint), kept only as long as the limit window requires.
• Operational logs. Error codes and correlation ids used to diagnose failures. Logs never contain sign-in codes, session tokens, uploaded files, draft bodies or full result outputs.

Visibility is enforced by the database for every request, including direct API calls, so the rules below hold regardless of which page or client asks.

• Anyone, including signed-out visitors and search engines: published prompts and versions, public results and their images, visible comments, and profiles.
• Only you: your drafts and working versions, withdrawn content, your vote directions, bookmarks, collections, notification preferences and notifications.
• Moderators (and administrators): in addition, content that moderation hid, the report queue with reporter usernames, and the moderation log. Moderators cannot see drafts or content you withdrew yourself.
• Administrators: in addition, account status and role for every member.

Hidden, withdrawn and nonexistent items answer identically (not found) to anyone without access, so nobody can learn that a private item exists.

PromptByte ships with a no-op analytics adapter. This deployment has no analytics provider configured: no usage events are sent anywhere.

When a provider is configured, only these event names are emitted, each with public object identifiers and small fixed-vocabulary values (for example the sort order or output type):

prompt_viewed, search_performed, prompt_copied, prompt_shared, draft_created, prompt_published, result_published, comparison_opened, vote_changed, report_submitted

Never sent: raw search queries, prompt or output text, variable values, email addresses or persistent anonymous identifiers. Telemetry never blocks a page or action, and counts shown in the product never depend on it.

• Session cookies. When you sign in, Supabase Auth sets session cookies (names starting with sb-) that keep you signed in and are refreshed as you browse. They are removed when you sign out. Signed-out visitors receive no identifying cookies.
• Theme preference. Your light/dark/system choice is kept in your browser's local storage so the page renders in the right theme without a flash.
• There are no advertising cookies and no third-party tracking cookies.

• Uploads go to a private storage bucket through a short-lived, server-issued upload address; the browser never writes to storage directly.
• The server decodes each image, checks its type and size (JPEG, PNG or WebP, up to 25 megapixels), strips embedded metadata such as camera and location data, and re-encodes it as WebP (up to 2048 px, plus a 640 px thumbnail; avatars 256 px).
• Images are served only through /api/media/…, which checks visibility on every request and redirects to a signed address valid for 60 seconds. When a result or prompt is hidden, withdrawn or deleted, new addresses stop being issued immediately and any link already handed out expires within a minute.
• Rejected or abandoned uploads, replaced images and the images of deleted accounts are removed from storage by scheduled cleanup jobs.

From Settings you can download a JSON export of your profile, drafts, published prompt versions, your results (with references to your image files), your comments, bookmarks and collections, notification preferences and notifications. It never includes other members' private data or internal moderation notes.

An export requires a fresh sign-in confirmation, is streamed page by page rather than assembled in memory, and is limited to three exports per day. Image references in the export are temporary links or storage keys with a manifest explaining how to download the files while your account exists.

Account deletion is started from Settings and requires an explicit confirmation and a fresh sign-in. It removes your prompts, and therefore every result other members attached to those prompts. Other members' prompts stay, and your comments on them become author-less placeholders.

1. Immediately, in one step: your account is marked as deleting and no further changes are accepted even with an open session; your prompts (drafts included) and results are withdrawn from public view; your comments are replaced by empty placeholders; your votes, bookmarks, collections and notifications are deleted; your profile is reduced to “Deleted member” with no bio or avatar.
2. Cleanup job: the storage keys of your images (including images under your prompts) are handed to a background job that removes them from storage. The job is retried until it succeeds; no content is copied into the job.
3. Final removal: once storage is clean, your sign-in identity is deleted and your profile row is removed, which removes your prompts, versions, results and every dependent row. Active sessions are ended.
4. What remains: only minimal operational records proving the job completed and moderation log entries that reference opaque identifiers. No content or profile text is kept in them.

Deleted material cannot be recovered through PromptByte. Copies that other people made while the content was public are outside PromptByte's control.

Operator must confirm: the backup retention period for this deployment has not been stated yet.

Deleted data may persist in database backups until those backups age out under that retention; backups are used only to restore the service after a failure, never to bring deleted content back into the product.

• Supabase provides the database, authentication and file storage that hold everything described above.
• The hosting provider chosen by the operator runs the PromptByte application and its scheduled cleanup jobs.
• Email delivery for sign-in codes uses the email service the operator configured in Supabase Auth.

Operator must confirm: Contact information has not been provided by the operator yet.