Privacy
Dev Scenario is local-first. It runs on your machine, talks to your devices, and writes its configuration to your home directory. Your projects, flows and devices stay on your machine, and no account is required to use the platform.
Last updated 5 November 2026
Who we are
Dev Scenario (“we”, “us”) is responsible for the personal data described here (the data controller). Contact: [email protected].
The platform
Dev Scenario reads and writes only the directories it explicitly tells you about. Apart from the update check, remote settings, trial registration and license renewal described below, and usage statistics and crash reports unless you switch them off, network traffic only leaves your computer when you use features that call services you chose (Firebase, Zephyr Scale and so on), with credentials you provide.
Product analytics
On first launch the app shows what it would send and suggests usage statistics switched on; you can switch them off before you continue, or any time later. Nothing is sent before you answer. When they're on, it sends which features are used (for example that a run started and how long it took), with basic setup details such as the app version, operating system and whether it runs on a trial or a license. They never include your code, flows, screens, device data, package names, file paths, names or emails. They carry a random id the app creates on your computer, so they are pseudonymous: we can't tell who you are, but the events of one install can be grouped. You can switch them off any time in Settings › Privacy; the app stops sending at once. They're stored with PostHog in the EU, with IP addresses discarded.
Crash reports
Crash reports are suggested on in the same first-launch question; you can switch them off there or in Settings › Privacy. When they're on and the app hits an unexpected error, it sends the error, its stack trace, the app version, the operating system and processor type, the plugins you have enabled and the last warnings from the app log to Sentry in the EU. Before sending, the app removes your home folder path, email addresses, tokens and passwords it finds in that text; an error message can still name a value it was about. No user id or computer name is sent.
Updates and remote settings
The app checks GitHub for updates and downloads the app and its plugins from there. It also reads remote settings from PostHog, which let us switch off a broken plugin or ask for an update that fixes a security problem. This check runs whether or not usage statistics are on. It sends the app version, operating system, processor type, installed plugin versions and whether it runs on a trial or a license (with the days left), with a random id that is new every time the app starts, so these checks can't be linked over time. It never sends who the license belongs to, and PostHog builds no profile from it.
The trial
On first launch, the app sends a machine ID (a one-way hash of your computer's id, not your hardware serial number) to our license server, which records when this computer's trial started and sends back a signed trial file. The app checks in at launch and about once a day while the trial runs. It sends only that ID and the trial start recorded on your computer: no name, email or computer name. This stops the 6-week trial from being restarted by deleting its files. If the server can't be reached, the trial still starts on your computer, with 2 weeks until it can check in. Organisations can turn this off with a managed setting.
Buying a license
Payments are handled by Paddle, our reseller and Merchant of Record. Your card or wallet details go to Paddle, never to us. Paddle shares with us your name, email address, country and the plan you bought, so we can issue and support your license. See Paddle's privacy notice.
Activating a license
When you activate, the app sends your license key, a machine ID (a one-way hash of your computer's id, not your hardware serial number) and your computer's name, so you can tell your computers apart and stay within the seat limit. The app renews the license about once a day with the same information. Deactivating a computer deletes its record.
Team and Enterprise licenses have named seats: you also give your work email, and we email a one-time code to it to confirm the seat. On licenses set up for managed deployment, IT can claim a seat without a code, and the license contact is told by email. The person who manages the license signs in to the team page with a link sent to their email. There they see each seat holder's email, their computers' names, when each was activated and last checked in, and they can invite people by email.
Contacting us
When you write to us or use the Enterprise enquiry form, we receive your name, email, company, the number of seats if you give it, and your message, and use them to answer you. The form uses Cloudflare Turnstile to check that a person, not a bot, sent it.
The roadmap
Voting and requesting features on roadmap.devscenario.com needs a Google sign-in. We store your name, email address and profile picture, and keep you signed in with a cookie. Other visitors see your first name and last initial next to your requests, never your email.
Security and abuse limits
To stop abuse, the license server counts requests per IP address and per email address (for example activations, code requests and contact messages). These counters are deleted after about two days.
Services we use
These services process data on our behalf, only for the purpose named:
- Paddle: checkout, payments, invoices and tax (Merchant of Record).
- Cloudflare: hosting of this website and the license server, and the Turnstile bot check.
- Resend: sending license keys, one-time codes and sign-in links by email.
- Sentry: crash reports, stored in the EU.
- PostHog: usage statistics (unless you switch them off), remote settings and website analytics, stored in the EU.
- GitHub: update checks, and app and plugin downloads.
- Google: sign-in on the roadmap.
Why we may use your data
License, seat and purchase data: to provide the license you bought (a contract with you). Usage statistics and crash reports: our legitimate interest in finding and fixing problems and learning which features are used; you can object at any time by switching them off in Settings › Privacy, which stops sending at once. Remote settings and update checks: our legitimate interest in keeping the app safe to use, for example switching off a broken plugin. Website analytics: our legitimate interest in knowing which pages help visitors and which need work. Request counters and trial records: our legitimate interest in preventing abuse. Records kept after a subscription ends: tax and accounting law.
Data outside the EU
Some of these services are based outside the EU and the EEA, for example in the United Kingdom or the United States. Where they receive personal data, the transfer relies on an adequacy decision of the European Commission (such as for the United Kingdom, or the EU-US Data Privacy Framework for certified companies) or on the European Commission's Standard Contractual Clauses. Ask us for a copy of the safeguards that apply.
Keeping and deleting data
We keep license records while your subscription is active and as long as tax and accounting rules require after it ends. A trial record (the hashed machine ID and its dates) is deleted a year after the trial started. Seat codes expire after 10 minutes and team sign-in links after 15 minutes. Crash reports are kept for at most 90 days and usage statistics and website analytics for at most 12 months. Emails to us are kept as long as we need them to answer you and to keep a record of a purchase or a request.
Your rights
You can ask to see, correct, export or delete your personal data, or object to how we use it. Write to [email protected]; we answer within 30 days. You can also complain to the data protection authority where you live.
This website
devscenario.com and its roadmap use an analytics service, with data stored in the EU, to see how the site is used: which pages
are visited, how long they're read, what is clicked and where visitors leave. This covers usage data such as
page addresses, the referring page, clicks and browser and device type. It uses no cookies, stores nothing in
your browser, never records what you type into forms, and discards IP addresses after turning them into an
anonymous ID that changes daily. There are no session recordings or advertising, and browsers that send Do
Not Track aren't counted. Our only cookies are the
sign-in cookies on the roadmap and on the team page. The pricing page loads Paddle's checkout script and
Cloudflare Turnstile, which receive your IP address and browser details; see Paddle's privacy notice. Fonts
are served from our own site. While you sign in with Google, the roadmap keeps the vote or request you
started in your browser's sessionStorage (key ds-roadmap-pending) and never sends it anywhere else.
Questions
If you have a privacy question, reach us at [email protected].