Privacy Policy

This Privacy Policy describes how AEC DX Labs ("we", "us") collects and uses personal data when you use our desktop applications (such as REVIFF), the AEC DX Labs account portal and related services (the "Services").

1. Data We Collect

• Account data — your email address and, if you set one, a display name, used to create and secure your account and to communicate with you. If you sign in with Google or Microsoft and haven't set a display name, we use the name that account shares.
• Profile photo — a photo you upload in the portal, or the photo of the Google or Microsoft account you sign in with. We keep a small square copy (256 × 256 pixels). A Google or Microsoft photo is copied when you sign in, unless you have already removed or replaced your photo in the portal; after that we never import one again. To get a Microsoft photo, our server asks Microsoft for it once, with the permission to read your basic profile that you grant when you sign in. Your photo is shown to you in the portal and to our support staff, including on your support tickets. It is stored at a public link that is hard to guess, so anyone who has the link can see it. You can remove it at any time on the Profile page.
• Sign-in data — we don't use passwords. You sign in with a one-time code we email you (the same email also contains a sign-in link), or with your Google or Microsoft account. If you use Google or Microsoft, we receive your email address and the basic profile details that provider shares, such as your name and photo. If you connect more than one of these sign-in methods, we keep the email address of each. If you turn on two-step verification, we store what is needed to check the codes from your authenticator app. Our sign-in provider also keeps a record of your signed-in sessions, including the IP address and the browser or app each session came from. The portal's Security page shows you your sessions from the last 90 days, with that browser or app, its IP address and when it was last used, so you can sign them out.
• Licensing and device data — your licenses and trials for each app (plan, status and dates). When you sign in to one of our desktop apps on a PC, and each time it checks your license after that, the app sends us a salted hash of that PC's Windows machine ID (the ID itself never leaves your PC), the computer's name, its Windows version and the app's version. We record when each device was first and last seen. We use this to apply your plan's device limit for each app, to allow only one free trial of each app per PC, and to show you your devices so you can rename or deactivate them.
• App check-ins — when you use one of our desktop apps while signed in, it checks in with us about once a day. It sends which app and version you use and a pseudonymous ID for your PC (a hash that doesn't identify the PC or you on its own). We record the day, the first and last check-in that day and how many there were, and when an app is activated or starts a trial on a PC. We use this to show when your devices were last active and whether an update is available, and to count how many people use each app.
• Promo codes — when you redeem a promo code, we record the code, the app it unlocked, when you redeemed it and until when it gives you access.
• Settings backups — when you use one of our desktop apps (such as REVIFF) on a PC where it is activated with your license, the app saves a copy of its settings to your account, so your other PCs can start from the same settings. We store each copy (up to 1 MiB) with the app it belongs to, the app's version, the name of the PC it came from and when it was saved. The apps add these copies; in the portal you can see and download them.
• Support tickets — the subject, category and app (if any) you choose, your messages, and any attachments you add (images, plain-text files or zip archives, up to 1 MiB each and 5 MiB per ticket). Feature requests are support tickets too, and only you and our staff can read them. For each of our replies, we also keep whether and when it was emailed to you, with the ticket.
• Billing data — when paid plans are available, purchases are handled by Paddle as merchant of record, and Paddle collects your payment details. To start a checkout, we share your email address with Paddle to create your Paddle customer account, and we keep its Paddle customer ID. Paddle sends us notifications about your transactions, subscriptions and refunds, which we store. They include what you bought, the amounts and the status, and may include limited payment details such as the card brand, the last four digits, the expiry date and the cardholder name. We never receive your full card number.
• Notifications and email — the notices we show you in the portal (for example a reply to your support ticket, a license that is about to end, a new version of an app you use or an announcement from us) and whether you have read them, which kinds of email you have turned off, and a record of each notice we email you: when it was sent and through which email provider.
• Error reports — when something goes wrong in the portal in your browser, the portal sends us a report so we can fix it: the error message and where in our code it happened, the page's path (never the rest of its address, which can contain sign-in codes), the portal version, your browser's user agent and, if you are signed in, your account. Our server adds a scrambled (hashed) form of your IP address that changes every day. We use it only to limit how many reports one address can send and to tell whether many reports came from the same place, and we never store the IP address itself. Only our staff can read error reports.
• Staff activity records — when our staff take an administrative action, such as changing a ticket's status, granting a license, or suspending or deleting an account, we record who did it, what changed and when. We also record when you ask to delete your account, or keep it, yourself, when a staff member opens a read-only view of your account to help you, and when staff download a list (such as licenses or devices) from the admin tools. The record of an account deletion includes that account's email address. If staff suspend an account, they note the reason with it until the suspension is lifted; the activity record keeps it.

2. How We Use Data

We use personal data to provide and secure the Services, enforce license terms (device limits and one free trial of each app per PC), respond to support requests and feature requests, limit spam, send service emails (such as sign-in codes, replies to your support tickets, license and billing notices and expiry reminders) and show notifications in the portal, tell you about new versions of the apps you use and show announcements (such as planned maintenance), find and fix errors, count how many people use each app, comply with legal obligations and improve the Services. We do not sell personal data, and the portal contains no advertising or analytics trackers: its error reports go only to us.

You can turn off each kind of optional email (licenses and billing, support, product updates) under Notifications → Email preferences, or with the unsubscribe link in any such email. Notices about your account itself (a device signed out by our team, account deletion, a two-factor reset) are always sent, and notifications in the portal can't be turned off.

3. Processors and Sub-processors

We rely on a small set of service providers:

• Supabase — database, sign-in, file storage (settings backups, support attachments and profile photos) and the server functions behind the portal and our desktop apps.
• Cloudflare — hosting and DNS for the account portal, our scheduled maintenance jobs (daily, and every 15 minutes to send queued email and scheduled announcements), and storage (Cloudflare R2) for our encrypted nightly backups.
• GitHub — GitHub Actions runs the nightly job that exports our database and copies our stored files (settings backups, support attachments and profile photos), encrypts both copies and uploads them to Cloudflare R2.
• Brevo — email delivery: sign-in codes and links, support-ticket and billing notifications and notices about your account (such as a scheduled deletion).
• Paddle — payments and merchant of record, once paid plans are live. From then on, the billing page also loads Paddle's script (Paddle.js) to show prices and run checkout.

These providers process data on our behalf under their own security and data-processing commitments. If you sign in with Google or Microsoft, that sign-in is also handled by Google or Microsoft under their own privacy policies.

4. Retention

• Account data is kept while your account exists.
• Profile photos are kept until you remove or replace them, or your account is closed. A replaced or removed photo is deleted straight away, or by our daily maintenance job if that fails.
• Settings backups: we keep the newest 3 for each app. When an app saves a new one, older ones are deleted. All of them are deleted when your account is closed.
• Support tickets and their messages are kept while your account exists. Attachments are deleted automatically 180 days after the ticket is resolved or closed.
• Device records are kept for each app: an active device that hasn't been seen for 90 days is removed the next time you activate that app. A device you deactivate stays on record for as long as your account exists, so that PC can't take a seat for that app on your account again.
• Trial records: we keep a record of which PCs (by their hashed machine ID) have used a free trial of each app, including after an account is closed, so a trial of that app can't be started again on the same PC.
• App check-ins are kept for 90 days and the activation and trial events that go with them for 400 days, then deleted automatically. Before the check-ins are deleted we keep monthly totals (how many people and PCs used each app that month), which are only counts and aren't linked to you.
• Promo code redemptions are kept while your account exists.
• Notifications in the portal are deleted 90 days after you read them, and at the latest 365 days after they were created.
• Email delivery records (which notice went to which account, when, and through which provider) are kept 30 days. For an email with no account behind it, such as the confirmation that an account was deleted, we remove the address as soon as the email has been sent.
• Error reports are deleted automatically 30 days after they are sent.
• Staff activity records are kept as a security record, including the email address of a deleted account.
• Billing records: the full content of each Paddle notification we store (which can include your name, email address and limited payment details) is deleted 90 days after we process it. We keep a record that it arrived and how it was handled, including after an account is closed. Paddle keeps its own records under its own privacy policy.
• Backups of our systems: our encrypted nightly copies of the database and of stored files are deleted 35 days after they are made, so deleted data can remain in them until then.

When an account is closed

You can delete your account yourself with "Delete account" on the Profile page, or ask us to (see Your Rights). A deletion you ask for in the portal has a 7-day grace period: your account is locked straight away (your apps and other browsers are signed out and changes are paused) and deleted on or shortly after the seventh day. Until then you can sign in and keep your account. When you ask, an active subscription is set to end at the end of its current billing period, so you aren't charged again; if you keep your account before it ends, it renews as before (one you had already set not to renew stays that way). An overdue or paused subscription is canceled straight away, and keeping your account doesn't restart it. A subscription still running when the account is deleted is canceled then, and nothing is refunded automatically. We email you when the deletion is scheduled, when you keep your account and when the deletion is done, and we keep your email address with the pending deletion only until then. The address we send the final email to is removed from our email records once it's sent.

When the account is deleted, we delete your sign-in account and profile, your profile photo, licenses, device records, settings backups, support tickets (feature requests included) with their messages and attachments, app check-ins and promo code redemptions, and the link to your Paddle customer account. Error reports you sent are no longer linked to you and are deleted when they expire. The records listed above as kept after an account is closed are not deleted.

5. Cookies and Storage on Your Device

We don't use cookies. The portal keeps a few items in your browser's storage so that it works as expected:

• A localStorage key starting with sb- — your sign-in session, so you stay signed in until you sign out.
• aecdx-theme (localStorage) — your light or dark theme choice, if you pick one.
• postSignInRedirect (sessionStorage) — the page to return to after you sign in.
• aecdx-dismissed-announcements (localStorage) — the announcements you closed in the portal, so they stay closed in this browser.
• oauthIntent (sessionStorage) — while you are away at Google or Microsoft, whether you are signing in or connecting that account to your profile.
• aecdx-support-draft:… (sessionStorage) — replies to your support tickets that you haven't sent yet.
• aecdx-deletion-subscriptions (sessionStorage) — after you ask to delete your account, how many subscriptions the request set to end or canceled, whether keeping the account turns their renewal back on, and when the first one ends, so the page can tell you.

Items in sessionStorage last only until you close the browser tab. Once paid plans are live, the billing page also loads Paddle.js, which is covered by Paddle's own privacy policy.

On your PC, each of our desktop apps (such as REVIFF) keeps its own encrypted file with your license, your sign-in session and your email address. Windows protects it so that only your Windows user account can read it.

6. Security

Data is encrypted in transit, and database access rules limit what each account can read and change. There are no passwords: you sign in with a one-time email code or link, or with Google or Microsoft, and you can add an authenticator app as a second step in your account's security settings. Our staff need two-step verification to use the admin tools. Your PC's machine ID is hashed before it leaves your PC, and our nightly backups are encrypted before they are stored. To stop abuse, we count how often each account (and, for error reports, each hashed IP address) uses some features, such as replying to support tickets, saving settings backups or activating apps, and delete these counts after 2 days. No system is perfectly secure; keep your email account and authenticator app safe, since they control access to your account.

7. Your Rights

Depending on where you live, you may have rights to access, correct, export or delete your personal data, and to object to or restrict certain processing. To exercise them, email us at hello@aecdxlabs.com from the email address on your account.

You can also do much of this yourself in the portal. On the Profile page, "Download my data" gives you a copy of your account as a JSON file: your profile, sign-in methods, licenses, devices, the list of your settings backups, billing records, support tickets (feature requests included), notifications, email preferences, promo code redemptions and your apps' check-ins without the PC ID (each settings backup itself downloads from the Backups page). "Delete account" on the same page closes your account after a 7-day grace period (see When an account is closed). You can also change your display name, photo and email address, sign out your other sessions and deactivate devices yourself.

8. Children

The Services are not directed to children and we do not knowingly collect personal data from children.

9. Changes to This Policy

We may update this Policy from time to time. Material changes will be announced by email or an in-portal notice before they take effect.

10. Contact

Privacy questions and requests: hello@aecdxlabs.com. See also our Terms of Service.