Privacy Policy

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

What we don’t do

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.

What OpenReplay masks. Masking happens in your browser, before anything is sent, so we never receive the masked values:

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:

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].