Privacy Policy — MonitorMonitor

Your display settings and window layouts stay on your Mac. MonitorMonitor never reads what is on your screen, never uses screen recording, and never uploads window titles or positions. The only things that leave your Mac are your Bravely Account sign-in, your purchase state, the check for updates, usage analytics you can turn off, and a diagnostic report if you choose to send one.

MonitorMonitor adjusts brightness, contrast, and volume, switches inputs, and turns displays off at your request by talking to the monitor over the monitor's own control channel. When a monitor has no power control of its own and is the only screen still lit, turning it off uses macOS display sleep instead, which darkens every display until the next mouse movement or key press. Crisp scaling works by creating a sharper virtual display on your Mac and having the monitor mirror it; when you revert it, or the app quits, the virtual display goes away and the monitor goes back to its own look. Input switching and power commands go only to the monitor. None of this sends any data off your Mac, and the menu-bar controls need no macOS permission. While a display is turned off, the app watches for the mouse moving or a key being pressed only so it can turn the display back on, and records neither. To remember your settings per display, the app stores each display's identifiers (its model and serial number, as the monitor reports them) locally on your Mac.

Your brightness and volume keys, spots, layouts, and Cascade use the window control permission, which macOS lists under Privacy & Security › Accessibility. The app asks for it the first time you use one of them, not before, and you can revoke it there at any time; the menu-bar controls keep working without it. With that permission the app receives your brightness and volume key presses so it can apply them to the right display, and reads the position, size, and title of your open windows so it can capture a layout and put windows back. That information is stored on your Mac only. It is never uploaded, and it is never included in analytics or diagnostic reports.

MonitorMonitor does not use screen recording and does not read the contents of your screen. It does not record keystrokes or clicks. Window titles are used locally to match a window to its place in a layout, and nowhere else.

MonitorMonitor requires a Bravely Account, which is covered by its own policy at bravely.dev/privacy/bravely-account. It is sold only as part of the Mac Utility Bundle. The purchase is made through our website checkout and processed by the payment provider named under Sub-processors; we store the minimum record needed to know that your account owns the bundle. We do not collect or store payment card details.

Unless you turn it off, MonitorMonitor sends usage analytics so we can see which features matter and what breaks. Events record kinds, codes and counts: that the app was opened for the first time or opened again; that sign-in started, finished or failed, with the sign-in method and an error code when it failed; that checkout started or could not open, that a purchase was activated, and whether the app is unlocked when that changes; that Settings was viewed; that a display was detected and what kinds of control it offered; whether the brightness and volume keys are working, waiting for the window control permission, failing or off; that Good Defaults were applied and which ones, that their card was shown, that one was switched on or off, and that Undo all was used; that an input was switched, as the monitor's input codes only, and that a display was turned off, put to sleep or turned back on, and what triggered it; that crisp scaling was tried, kept, reverted or failed, with the mode's resolution and refresh rate and a short reason code; which built-in spot was used; that a custom spot was saved or used; that a layout was captured or applied, with how many windows were placed; that a cascade ran, with whether the windows were Terminal windows, how many there were, whether they were ordered by their Terminal Tags badges, and whether the pattern was built in or one you saved; and that the launch at login or beta updates setting was changed. Events never include a display's name, a window title, an app's name, the name you gave a custom spot, layout or cascade, or anything on your screen. Each of these events carries the app version, the macOS version, an installation identifier, and whether you are signed in and the app is unlocked. While you are signed in, each one also carries your Bravely Account identifier. None of them carries your email address. When you sign in, the app sends one more event that links this installation's earlier events to your account. The events about opening the app, signing in, checkout, unlocking and viewing Settings are also sent to our own account service, which is where we count installs, sign-ins and purchases. You can turn this off at any time in Settings, under General, with Share usage data, and it takes effect immediately.

A diagnostic report is sent only when you press the Send Diagnostic Report button. It contains the app's own recent log lines and information about your displays: the model, the control features each one reported, and any errors the app hit while talking to them. Window titles are removed before the report is sent.

MonitorMonitor checks our servers for a new version once a day and when you choose Check for Updates. That check tells us the version you are on and the usual information any download involves, such as your IP address. It does not carry anything about your displays or windows. If you turn on Install beta updates in Settings, the same check also offers beta versions.

Display settings, layouts, and display identifiers live on your Mac until you delete them or remove the app; we hold no copy. Purchase records are kept for as long as your account exists, plus whatever the law requires us to keep for tax and accounting. Usage analytics events are kept for as long as they are useful for understanding how the product is used. They never contain your display names, window titles or anything on your screen. A diagnostic report is kept so we can investigate the problem you reported; email privacy@bravely.dev to have one deleted. Deleting your Bravely Account works as described in the Bravely Account policy and has no effect on the settings on your Mac, which were never ours.

MonitorMonitor is intended for adults. We do not knowingly collect personal information from children under 13, or under 16 in places where 16 is the relevant age for information-society services.

We keep backups so that we can recover our customers' data if it is ever lost. Each night we copy the databases that hold accounts, purchases and the content our apps and services keep for their users, including sign-in records and the protected form of passwords, and we copy the files stored with us, such as documents, screenshots and attachments. Unless a section above says otherwise, the account, purchase and content records this policy describes, and the files you store with us, are in these backups. Where backups are kept Backups are kept in two places, both in the United States: on storage equipment that we own, and in Amazon S3, a storage service run by Amazon Web Services. Every copy of a database or of sign-in records is encrypted, with a key that only we hold, before it is stored in either place. The copies of stored files that we keep in Amazon S3 are also encrypted with a key that only we hold, file names included; the copy of those files on our own equipment is not separately encrypted. Amazon does not have our keys, so it cannot read your data in the backups. How long backups are kept Each night's copy of our databases and sign-in records is deleted after 90 days and fully purged within 30 days after that, so it is kept for about four months at most. One copy each month is kept for up to 12 months instead, and fully purged within 30 days after that, so it is kept for about 13 months at most. The backup of stored files keeps each file for as long as it is stored with us; when a file is deleted or replaced, the backup keeps the earlier version for 90 days and then deletes it. Separately, Cloudflare, which runs most of our databases, keeps a recovery history of each of them for 30 days. How backups are used We use backups and that recovery history only to restore data after it has been lost, for example in an outage, through a mistake or in an attack, and we also use backups to test that restoring works. Deleting something, or deleting your account, does not remove it from backups made before the deletion or from the recovery history: those copies stay until they are deleted on the schedules above. If we restore data from a backup or from the recovery history, we re-apply the deletions made after the point we restore to, including account deletions, so that the restore does not bring back data that had been deleted.

Depending on where you live, you have rights over the personal data we hold about you. We honor these rights for everyone who asks, regardless of where you live. • Access — ask what personal data we hold about you and get a copy. • Correction — ask us to fix data that is wrong or incomplete. • Deletion — ask us to delete your personal data by emailing privacy@bravely.dev from the address on your account. Where a product has a built-in Delete Account control you can use that instead; bravely.dev/delete-account explains what applies to each product. • Portability — ask for your data in a portable, machine-readable format. • Objection and restriction — ask us to stop or limit certain processing. • Withdraw consent — where we rely on consent (for example, marketing email), you can withdraw it at any time without affecting processing that already happened. • Non-discrimination — we will not degrade your service or charge you more for exercising any of these rights. EEA and UK residents also have the right to lodge a complaint with your local supervisory authority. California residents may use an authorized agent; we may verify the agent's authority and confirm the request with you first. Other US states with comprehensive privacy laws (including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, and others as they take effect) have equivalent rights, including a right to appeal a denied request — reply to our decision email with "Appeal" and we will respond in writing within the period the law requires. Canadian residents have access, correction, and consent-withdrawal rights under PIPEDA; Australian residents have access and correction rights under the Australian Privacy Principles. To exercise any right, email privacy@bravely.dev. We respond within the timeframe the applicable law requires — generally 30 days under GDPR and 45 days under the CCPA, with an extension where the law permits one. We may need to verify your identity before acting, usually by confirming control of the email address on the account.

If you are in the EEA or UK, we rely on these lawful bases under the GDPR and UK GDPR: • Performance of a contract — creating and securing your account, delivering the features you paid for, syncing your content, processing purchases, and providing support. • Legitimate interests — keeping the service secure and reliable, preventing fraud and abuse, understanding how our products are used through usage events tied to an installation or to your account, and improving the product. We balance these against your rights and do not use them to justify intrusive tracking. Where an app lets you turn its usage analytics off, doing so is one way to object. • Consent — marketing email, and anything else we ask your permission for before we collect it. You can withdraw consent at any time. • Legal obligation — keeping tax, accounting, and consent records, and responding to lawful requests.

Bravely Studios LLC is a US company. We and our sub-processors process data in the United States and in other countries where they operate. For personal data originating in the EEA, UK, or Switzerland, we rely on appropriate transfer safeguards in our processor agreements — such as the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum — where those safeguards are required. Email privacy@bravely.dev if you want more detail about the safeguards that apply to you.

For California residents, the categories of personal information we collect for this product are: • Identifiers: your Bravely Account identifier, email address, and device or installation identifiers. • Commercial information: the record of your Mac Utility Bundle purchase and entitlement, and any refund. • Internet or other electronic network activity: usage analytics events tied to your installation and, while you are signed in, to your Bravely Account identifier, with the app version and macOS version, and the contents of a diagnostic report if you choose to send one. • Coarse geolocation: a country-level signal derived from your network connection, used for consent rules and tax. We collect this from you, your device, and our own systems, and we use it to run the product, honor what you have bought, keep the service secure, and support you. We disclose it to the service providers listed under "Sub-processors," each for a business purpose under a written contract. We do not sell your personal information and we do not share it for cross-context behavioral advertising, as those terms are defined by the CCPA and CPRA, and we have not done so in the preceding 12 months. We do not use or disclose sensitive personal information for any purpose that would trigger the right to limit. If that ever changes we will update this policy and provide the required opt-out before the practice begins. Retention is described under "Data Retention" and "Backups" above and, for account-level data, in the Bravely Account privacy policy.

We use the following service providers to run this product. They receive only what they need to perform their service for us, and each is bound by the data-processing terms that apply to our use of their service. Where a provider is not yet covered by a written data-processing agreement with us, its entry below says so. If you need a data-processing agreement in place before you use this product, email privacy@bravely.dev: • Cloudflare, Inc.: hosting for bravely.dev and the account, purchase, and diagnostics services the app talks to. See cloudflare.com/privacypolicy. • Google LLC: Firebase Authentication, which backs Bravely Account sign-in (including Sign in with Google). See policies.google.com/privacy. • Apple Inc.: Sign in with Apple, when you choose that sign-in method. See apple.com/legal/privacy. • Paddle.com Market Ltd: our merchant of record for the Mac Utility Bundle purchase. Paddle handles checkout, payment processing, invoicing, and sales tax/VAT. See paddle.com/legal/privacy. • RevenueCat, Inc.: holds our record of what each Bravely Account owns. When MonitorMonitor checks your purchase, our account service looks up your Bravely Account identifier there, and when you buy the bundle it records the purchase there with your account identifier, the app you bought it from, and the date of your first purchase. See revenuecat.com/privacy. • PostHog Inc.: product analytics, receiving the usage events described under Analytics, which you can turn off in Settings. It also receives our account service’s own records of sign-ins, checkouts, and purchases, and records of update downloads, which that setting does not cover. See posthog.com/privacy. • Resend Inc.: sends our transactional email (sign-in codes, receipts, password resets, support replies). See resend.com/legal/privacy-policy. • Amazon Web Services, Inc.: Amazon S3, which stores our backups in the United States, as described under "Backups". The copies of your data that we keep there are encrypted, with a key that only we hold, before they leave our systems, so Amazon cannot read them. See aws.amazon.com/privacy. If we add or change a sub-processor in a way that materially changes how your data is processed, we will update this policy and give additional notice where the law or our data-processing commitments require it.

We protect your data with authenticated accounts, encryption in transit, access controls on our backend systems, and a deliberately small number of people who can reach production. No system is perfectly secure, and we do not claim guarantees we have not built and verified. Where a product makes a specific security claim, that claim appears in the app-specific sections above and is limited to what we have actually shipped. If we become aware of a breach affecting your personal data, we will notify you and the relevant regulators as required by law.

We may update this Privacy Policy from time to time. If we make a material change — a new category of data, a new sub-processor, a new purpose, or a new legal basis — we will update the "Last updated" and "Effective" dates and give additional notice where the law requires it. Where a change requires fresh consent under the GDPR, UK GDPR, CASL, or a similar regime, we will ask for it before relying on the new purpose. Non-material changes (typos, clarifications, link fixes) are reflected by updating the "Last updated" date.

Bravely Studios LLC Privacy and data rights: privacy@bravely.dev Product support: support@bravely.dev Website: https://bravely.dev Postal address: available on request to privacy@bravely.dev.