Privacy policy

1. Who runs FeedShots

FeedShots is run by an independent developer acting as an individual. Questions about this policy go through the contact form.

2. What we collect

• Account information: your email, account name, ID, invite status and account dates, to manage access and send sign-in and email-change codes.
• Sign-in and security information: essential authentication cookies, session records, IP address and browser information. A normal sign-in session lasts 7 days and may be renewed while you use FeedShots. Sign-in codes expire after 10 minutes. We also use your IP temporarily to limit abuse of the contact form.
• History and preferences: post IDs, saved settings, request times, request type and related account or API key IDs. Your history does not store post text, authors’ names or media; these are loaded again when you view it. We also store your saved default style. Your theme choice stays in your browser until you change it or clear browser storage.
• API key records: key names, hashes, short prefixes, settings and usage information. We do not store the full secret key in our database.
• Usage records: when a request happened, its type, how long it took, file sizes and whether it failed. These can be associated with your account, API key and post IDs. Error logs may contain diagnostic details. We use these records for security, limits, support and operating costs.
• Messages you send us through the contact form, with the email you give, the topic and any post link. The message is sent to our inbox; its body is not saved to the application database.

3. Posts from X

When you ask for an image or PDF, we load public posts from X through data providers. We reuse post and thread data in server memory for up to 1 hour and generated image files for up to 10 minutes. PDFs are generated for the response and are not saved to a PDF library. Signed image download links are valid for 24 hours; this is a link lifetime, not a file-retention period.

Photos and avatars can also pass through a separate image-delivery cache on disk, with a normal freshness period of at least 4 hours, or longer when the source’s cache headers allow it. Your browser can cache media too. These freshness periods are not deletion deadlines. Cached media may be served while it is refreshed and may remain longer on disk until cleanup. We don’t build profiles of the people whose posts you capture.

4. Translation

When you translate a post, we send the public text of the post and its author’s name and username to a language model: to Anthropic, or to OpenRouter, which passes it to Google or OpenAI. The name helps the model get grammatical gender right. This can include a quoted post and any personal information in the public text. We do not include your account email or other account details in the translation request.

A finished translation is reused from our server’s memory for up to 1 hour, and is shared by everyone who translates the same post into the same language in that time. We never save translations to our database. We record who asked for a translation, which post and what it cost, to apply daily limits and track costs. These logs follow the retention approach below. Each provider’s own handling of requests is also governed by its terms and privacy practices.

5. Who else handles data

• Railway hosts the service, its databases and operational logs.
• Resend delivers sign-in and email-change codes, account notices and contact form messages.
• Data providers load the public posts and threads you ask for. They receive post identifiers and public metadata needed to retrieve them, never your email or account details.
• Anthropic and OpenRouter translate post text when you ask for a translation.

Your browser may also connect directly to media hosts to load photos or avatars, which sends normal connection information such as your IP address. Providers may process data outside your country. We don’t sell personal data or share it for cross-context behavioral advertising.

We use no third-party analytics or advertising cookies. The service does not change its behavior in response to browser Do Not Track signals; we do not use cross-site advertising tracking.

6. How long we keep it

Account data, keys, saved style and history stay until you delete a record or delete your account on the Account page, where the relevant option is available. Usage and translation logs have a 12-month retention target. Cleanup is not immediate, so some older records may remain longer.

Sign-in and verification records expire under their security settings and are cleaned up during normal operation. Contact emails remain in our inbox and may stay after a request is resolved; there is no automatic deletion schedule for them.

Volume backups, daily and manual, are deleted within 30 days and can still contain data from before an account was deleted. Railway hosting logs and Resend’s sent-email records, including email addresses and message subjects, are not removed by account deletion and follow their providers’ separate retention settings.

7. Your choices

You can delete your account yourself on the Account page. Deletion immediately removes your account and sign-in sessions, API keys, saved style and history from the live application databases. API keys stop working immediately.

Deletion replaces your account ID in existing usage and translation records with a deidentified ID. These records contain no account email or name and remain for budgets and cost totals. Requests already in progress can finish after deletion and may add records with the former account ID; that ID no longer points to a live account. Deleting an account does not remove public posts from X, files already downloaded or the separate copies and records described above.

Ask for access, correction or deletion through the contact form. We may need to verify your identity.

You may have additional rights depending on where you live, including portability, restriction or objection to processing, and the right to complain to your local privacy regulator. These rights are subject to the applicable law and its exceptions. For concerns about your post, choose Remove my post or copyright.

8. Children

FeedShots is not directed to children under 13, and they may not create an account or use the service. If you believe a child under 13 has provided personal information to us, please use the contact form so we can review it and take the steps required by law.

9. Changes

When this policy changes, we update the date at the top. We email you about important changes before they take effect.