Privacy Policy
Last updated: October 30, 2026
Screenmint Staging is run by Plexsicity, who is responsible for the data described here. This policy describes what Screenmint Staging collects, why, and how it is handled. The short version: we collect the minimum needed to run an API with accounts and billing, we don’t sell data, and payment details never touch our servers.
What we collect
- Account data — your email address and the account identifier we get from Plexsicity Identity, which handles sign-in. Screenmint Staging does not receive your password.
- API keys — each key’s name, its first characters, when it was last used, and a hash of the key. The signing secret that goes with a key is stored so we can check signed URLs.
- Usage records — one row for every render request and every cache hit or signed-URL view: the account, the API key (if any), whether it came from the API, an AI agent (MCP) or the dashboard playground, the type of render (screenshot, video or OG card), whether it came from cache, how long it took, how much quota it used, the time, the target URL you asked us to render, the render parameters, and the address of the stored result. Of the parameters, we keep the numbers, true/false settings and choices from a fixed list (such as size, format, full page and dark mode), not the text you send, such as selectors, custom CSS or JavaScript, or OG card text; records made before this policy’s last update may also hold those. They power quota enforcement, your usage and history pages, and abuse prevention.
- Rendered content — the screenshots, videos and OG cards you ask for are stored in Cloudflare R2 and served from
cdn-smstaging.plxi.us. They are public: anyone who has a file’s address can fetch it, without signing in. See “Retention & deletion” for how long they are kept. - Things you set up — webhook endpoints (URL and signing secret) and a log of each delivery attempt (event, response status, error), templates, notification settings, batch and video job records, and in-app notifications.
- Team data — invitations (the invited email address and role) and who belongs to which team. Renders made by team members are recorded against the team owner’s account.
- Billing data — handled by Stripe. We store your Stripe customer reference, your plan and your billing period, never card numbers.
- Server logs — our web server logs each request to this site and the API (time, method, URL, response status, browser or HTTP client, and the visitor’s IP address), for security and debugging. For rendering requests made with GET, the URL includes the target URL.
- Error reports — when the API or this website hits an error, details of it (the error message and stack trace, the page or endpoint, and for browser errors the browser and operating system) are sent to our self-hosted GlitchTip. They can include an account or Stripe customer identifier. This is error reporting only; it does not record sessions.
What we don’t do
- No selling or renting of personal data.
- No advertising trackers, and no third-party analytics services.
- No browsing of your rendered images beyond what’s needed for operations, debugging, or abuse investigation.
Analytics & session recording
Both tools below run on Plexsicity’s own servers, not an outside analytics company’s. Your data is not sent to Google Analytics, Hotjar, or any other third-party service. They are loaded on every page of this site, including the dashboard.
- Page analytics (Umami, analytics.plxi.us). Counts page views and referrers, and records the browser, operating system, device type and approximate location of visits. It also counts three sign-up steps: a sign-up button clicked (
signup-started), an account created (account-created) and a first API key created (first-api-key-created), with nothing about who you are. It sets no cookies and we do not use it to identify individual people, so it runs without asking. - Session recording (OpenReplay, openreplay.plxi.us) — off unless you allow it. If you click “Allow” on the prompt, we record how you use the pages: clicks, scrolling, mouse movement, navigation, the page addresses you visit, browser console messages, and the address, status and timing of the network requests the page makes (not their bodies). Our OpenReplay server also sees your IP address and browser details when it receives a recording. We use recordings to find confusing or broken parts of the product. We do not attach your account or email address to a recording.
What OpenReplay masks. Masking happens in your browser, before anything is sent, so we never receive the masked values:
- everything you type into a form field;
- email addresses and numbers in the text shown on screen;
- API keys and signing secrets when they are shown on screen (the one-time key display on the API Keys page, with the agent setup commands that contain the key, and the one-time webhook signing secret).
Everything else on the page is recorded as you see it. That includes target URLs, key names, plan details, and previews of your renders. While recording is on, the tool also keeps its own session identifier in your browser’s storage. We ask once; if you decline, or simply ignore the prompt, nothing is recorded. To change your mind later, clear this site’s data in your browser and answer the prompt again.
Cookies & local storage
Cookies we set: your sign-in session (sm_session, 30 days) and a short-lived cookie used only while you sign in (sm_oidc_tx, 10 minutes), both secure and httpOnly so JavaScript can’t read them, and a light/dark theme cookie (sm_theme, one year). After your very first sign-in we also set sm_new_account (at most 10 minutes, readable by the page), which only tells the dashboard to count one new account in Umami; the dashboard deletes it as soon as it has done so. The session cookie holds your sign-in tokens, encrypted so that only our server can read them. When you sign out, we record the time against your account identifier, so that the cookie, and any copy of it, stops working on every device; these sign-out records are kept. In your browser’s local storage we keep which team you’re viewing, whether you allowed session recording, and the colours and light/dark mode you picked under Customize colors. We set no advertising or cross-site tracking cookies anywhere on the site.
Subprocessors
We share data only with the providers required to operate the Service, each receiving only what it needs:
- Stripe — payment processing; card details are handled entirely by Stripe and never reach our servers.
- Cloudflare — R2 storage and CDN delivery of your rendered images and videos, and a private R2 bucket that holds our older off-site backups (see below).
- Resend — email delivery. We send a welcome email when you sign up, team invitations (to the address you invite) and render-quota alerts.
- Plexsicity Identity (auth.plexsicity.com) — authentication and sign-in. It is run by Plexsicity and shared across its products.
- Our cloud hosting provider — application servers and the database.
Umami (page analytics), OpenReplay (session recording) and GlitchTip (error reporting) are self-hosted by Plexsicity on its own infrastructure and are therefore not subprocessors — that data is never handed to another company.
Retention & deletion
Rendered files. A cleanup job runs every day and deletes stored files that are past their plan’s period: screenshots and OG cards after 90 days (Free), 1 year (Starter), or 2 years (Pro); videos after 7, 45, or 90 days respectively. The period is counted from the most recent request that returned the file, and a file is kept as long as any account’s request for it is still inside its period. After a move to a plan with a shorter period, the previous plan’s period applies for 30 more days. When a file is deleted, the entry stays in your render history, marked as expired, with its target URL and parameters. Copies that Cloudflare’s CDN or a browser already cached can still be served for a time after the file is deleted. Our render cache, which points requests at stored files, expires within 24 hours.
Everything else. Account data, API-key records, usage records (including target URLs and render parameters), webhook and template records, batch records and notifications are kept while your account is active. Smooth-video job records are deleted 30 days after the job finishes. The records we use to process each request and send its webhooks are deleted about a week after they finish, and records of quota-alert emails 90 days after the alert is processed. Dashboard sign-in sessions expire after 30 days.
Account deletion. To delete your account and associated data, or to request earlier deletion of specific renders, email [email protected] and we’ll process it promptly. Your sign-in profile itself is held by Plexsicity Identity; say in your email if you want that deleted too.
Backups. Every night at 03:05 we dump the Screenmint Staging database to a file on the application server and keep the 14 most recent. At 03:35 a backup server run by Plexsicity copies the newest dump and also keeps its 14 most recent copies. Until this policy’s last update, the nightly dumps were copied to a private (not publicly reachable) Cloudflare R2 bucket instead, and we do not currently delete those copies on a schedule. So data you delete (or ask us to delete) is removed from the live database but remains in the nightly backups for up to 14 days, and in the older R2 copies until those files are deleted. Backups are not edited after the fact. They hold database records only (for example your usage records and target URLs); rendered files are not backed up.
Your rights
You can request a copy of your data, correction, or deletion at any time via the email above. If you are in a jurisdiction with specific data-protection rights (e.g. GDPR or CCPA), we honor requests accordingly.
Changes
If this policy changes materially, we’ll post the update here with a new date.
Contact
Privacy questions: [email protected].