DevWorkspace Pro Privacy Policy
Last updated: October 25, 2026
1. What Data We Receive
When you pay for DevWorkspace Pro, Polar.sh (and its payment processor, Stripe) collects information such as your name, email address, and billing details. They share purchase records with us so we can verify licenses and provide support.
Some features of the app send data to devworkspacepro.com. We get this data only when you use the feature. The table below lists it.
| Category | Source | Purpose |
|---|---|---|
| Name, email, billing address | Polar.sh / Stripe | License verification, support |
| License key, product ID | Polar.sh | Application access, updates & support |
| Technical cookie ("dev_workspace_pro_session") | First-party, essential | Keeps the site functional during your visit |
| Partner code cookie ("utm_source") | First-party, set only when you open a partner link | Credit the partner who sent you if you buy. It expires after 2 hours |
| Focus Pad Cloud Save copy, encrypted on your computer before it is sent | DevWorkspace Pro app, when you turn on Cloud Save | Keep your tasks the same on all your computers. We cannot read it |
| Telegram user ID, chat ID and username, and the text of each message you send to the bot | Telegram, when you link the bot and send it messages | Add each message as a task in Focus Pad |
| Uptime monitors (name, URL, check interval) and the result of each check | DevWorkspace Pro app, when you add a monitor | Check your sites and email you when a site goes down or comes back |
| GitHub Actions events (repository, workflow run, branch, commit and status) | GitHub, for repositories where you installed the DevWorkspace Pro GitHub App | Show workflow run updates in the app |
| Dashboard account: name, email address and password (we store only a hash of the password) | You, when you set up your account after you buy | Let you sign in to the dashboard to manage your license, Telegram link and monitors |
| License check-ins: a machine ID for each computer (a hash of the computer ID, not the ID itself), the app version, and the time of the last check-in | DevWorkspace Pro app, each time it checks your license | Check your license and see which app version each computer runs |
| Checkout details: email address, name, country, product and amount | Polar.sh, when you start a checkout | Send you up to 3 reminder emails if you do not finish the checkout. The reminders stop when you pay or reply |
2. How We Use the Data
- Verify that your license is valid.
- Provide support if you request it.
- Run the features you turn on: Cloud Save, the Telegram bot, uptime monitoring and GitHub Actions updates.
- Remind you about a checkout that you did not finish.
- Find and fix errors and slow pages on the site.
- Comply with legal or tax obligations.
3. Who Sees the Data
- Processors. Polar.sh and Stripe act as our payment and licensing processors. These services also work for us, and each keeps data under its own retention rules:
- Resend sends most of our emails, for example account set-up and monitor alerts. It gets your email address and the email text.
- Google (Gmail) sends the thank-you email after you buy, the checkout reminder emails and the emails in section 5. It gets your email address and the email text.
- Laravel Nightwatch watches the site for errors and slow pages. It gets request details such as the URL and your IP address, and, when you are signed in, your user ID, name and email address.
- Cloudflare sits in front of the site and stores the app downloads. It sees each request to the site, including your IP address.
- Telegram and GitHub. When you use the Telegram bot or the GitHub App, Telegram and GitHub send us the data in section 1 under their own privacy policies.
- Legal requirements. We may disclose information if required by law (e.g., a valid subpoena).
We do not sell, rent, or share data with advertisers or any third parties that do not help us run the site and the features above.
4. Data Retention
We keep purchase and license records only as long as necessary for support, bookkeeping, and legal compliance, then securely delete them.
For the features in section 1:
- Cloud Save copy: until you ask us to delete your account. Each save replaces the copy before it.
- Telegram messages: until the app on your computer gets them. Then we delete them. Your Telegram link stays until you ask us to delete your account.
- Uptime monitors and their check results: until you delete the monitor.
- GitHub Actions events: we delete them after 1 day.
- Dashboard account: until you ask us to delete it.
- License check-ins: one record for each computer, updated at each check-in, until the license is deleted.
- Checkout details: until you ask us to delete them.
5. Outreach Emails
Now and then we email people who bought DevDb Pro (our VS Code extension) or started a DevDb Pro checkout, to tell them about our other products. We check our customer lists first, so we do not email DevDb Pro customers about a product they already have.
Once an email is sent, we delete your name, your email address and the email text. We keep only a one-way code made from your address, so that we do not email you twice and we respect your choice to stop.
To stop these emails, click the unsubscribe link in any of them, or reply and ask us to stop.
6. Your Rights
Depending on where you live, you may have rights to access, correct, or delete personal data we hold. Contact us at [email protected] and we'll help, subject to verification.
7. International Visitors & GDPR
If you are in the European Economic Area or United Kingdom, our lawful basis for processing is "performance of a contract" (your DevWorkspace Pro purchase) or "legal obligation." For checkout reminders, site monitoring with Laravel Nightwatch and the emails in section 5, our lawful basis is "legitimate interests": to help you finish a purchase that you started, to keep the site working, and to tell developers about a tool for their work. We rely on Polar.sh and Stripe, both GDPR-compliant processors, to safeguard your data related to payments.
8. Children
DevWorkspace Pro is intended for developers and are not directed to children under 13. We do not knowingly collect personal data from children.
9. Security
We follow industry-standard practices (HTTPS, limited access, encryption at rest on third-party platforms) to keep data safe.
Cloud Save copies are end-to-end encrypted. The key stays on your computers, so we cannot read your tasks. Telegram messages and GitHub Actions events are not end-to-end encrypted: we keep Telegram messages as plain text until the app gets them. Our own real-time server passes Telegram messages and GitHub Actions events to the app and does not store them.
10. Changes
We'll post any Privacy Policy changes on this page and update the "Last updated" date. Material changes may also be announced via email.
11. Contact
Questions or requests? Email [email protected].