Privacy Policy — Bravely Help

If you write to a support address that Bravely Help handles, or to one of the addresses Jeff Schiesser, our founder, writes from, your email, its attachments and our team’s replies and notes about it are stored in Bravely Help so the team can answer you. Team members sign in with a Bravely Account; Bravely Help stores their name, role and settings, and the iPhone, iPad or Mac they use the app on. We do not sell any of this, we do not use it for advertising, and Bravely Help does not send email or tickets to any AI provider. Bravely Help has no purchase step, so we hold no payment records for it.

A team connects a support mailbox to Bravely Help, and Bravely Help turns the email sent to that address into tickets. For our own team this is support@bravely.dev, which includes the messages sent from the contact form on bravely.dev. When you write to it, Bravely Help stores: • Your message: who it is from, its reply-to address, the addresses it was sent and copied to, its subject, its date, its text, a copy of its formatted (HTML) version with anything that could run removed, and the original message exactly as it arrived. • Its attachments, including images inside the message, with their names, types and sizes. • A contact record with your email address and the name your email program sent with it. If your message reached us through a mailing list or our contact form, Bravely Help records the real sender rather than the list or form, and for the contact form it records the app and platform you chose. • What our team does with it: the ticket number, its status, who it is assigned to, its group and tags, internal notes that are never sent to you, and the replies the team sends you, with the name of the team member who wrote each one. • A search index of the subject, text and sender of each message, so the team can find past tickets. Replies are sent to you from the support address through the mailbox's email provider, and they appear in the same email thread as your message. Copies of support email also stay in our team members' own email accounts, as they did before Bravely Help. We use all of this only to answer you, to keep a record of what was said, and to support you later. Rules that a team sets up can file, tag, assign or close a ticket automatically, based on what the message says; they act only inside Bravely Help.

Jeff Schiesser, our founder, writes to customers from jeff.schiesser@bravely.dev, and also receives mail at jschiesser@bravely.dev and jeffs@bravely.dev. These three addresses deliver to a shared mailbox, team@bravely.dev, that the members of our support team can open in their own email, so they can read the mail sent to these addresses, and anything else that arrives in that mailbox, there as well as in Bravely Help. Bravely Help reads only the mail addressed to these three addresses, not the mailbox's other mail, and turns it into tickets that the whole team can see and answer, the same way as support email. A few kinds of mail sent to these addresses are left out by fixed rules and never stored in Bravely Help: mail from addresses that do not accept replies (such as no-reply addresses), automatic replies, bulk and mailing-list mail, and mail the email provider has marked as spam. Every other message becomes a ticket. These rules look only at the sender, the message's technical headers and the email provider's spam marking; no automated assessment of what a message says decides whether it gets in, and no message is held back for one person. Our team can also start a new email to you from Bravely Help, from one of these addresses or from the support address, one recipient at a time. When Jeff's welcome and getting-started emails, described in the Bravely Account policy, are sent, Bravely Help keeps a record of each one (your email address, your name if we have it, the subject and when it was sent) so that a reply to it joins the right ticket. Replies to those emails come into Bravely Help like any other mail to these addresses. A record that nobody replied to is deleted after 180 days.

You can text our support number, (316) 333-5345, in our Bravely Studios Support texts program, and your texts come into Bravely Help as a ticket, the same way support email does. We text only people who have texted us first, and only to answer them: we never send unsolicited, marketing or promotional texts. We do not share mobile numbers or text-messaging consent with third parties or affiliates for marketing or promotional purposes. If you text our support number, Bravely Help stores your phone number, your texts, any pictures you send (up to 10 per text), our replies, which are usually signed with the first name of the team member who wrote them, and whether each reply was delivered. We keep these the same way, and for as long, as support email, as described under "Data Retention", and our team's notifications can show your phone number and the first line of your first text in place of a name and subject. Our service logs record a shortened form of your number, never the full number or what you wrote. Reply STOP at any time and we will send you no more texts; reply START to receive them again, and HELP for help. We keep a record of a STOP, or of a carrier telling us you have opted out, so that we do not text you again, until you text START. If you call the number, you hear a short recorded message asking you to text or email us instead; calls are not put through to anyone, and we do not record calls or keep voicemail. Message frequency varies; we only send replies to your texts. Message and data rates may apply. The terms for these texts are at bravely.dev/terms/bravely-help.

To bring email in and send replies out, a team member connects each mailbox that receives the mail Bravely Help handles, by signing in to their email provider and allowing Bravely Help to read and send mail. For our own team these are two mailboxes with our email provider: one that receives support@bravely.dev, and the shared team@bravely.dev mailbox described under "Email to Jeff’s Addresses". The provider's permission covers the whole of each mailbox, so Bravely Help is built to read only the messages filed under the label set up in that mailbox for the addresses it handles, and the team's own replies in those conversations, and to refuse anything else. When a mailbox is first connected, Bravely Help reads the last 30 days of that mail. The access granted by the provider is stored encrypted, and Bravely Help checks for new mail about once a minute.

Images that an email loads from somewhere else on the internet are blocked when a team member opens the message. If the team member chooses to show them, their browser or device loads those images from the servers they are on, which can tell the sender's servers that the message was opened and the network address it was opened from. Images attached to the email itself come from Bravely Help.

Bravely Help needs a Bravely Account, which is covered by its own policy at bravely.dev/privacy/bravely-account. Only people a team has invited can see its inbox. An invitation is made with your email address, a display name and a role, and it is linked to your Bravely Account the first time you sign in with that address. For each team member, Bravely Help stores: • Your email address, display name, role, whether you are invited, active or removed, who invited you, and when you were last active. • Your settings: your signatures, your templates and the team's shared ones, your saved views, your theme and keyboard settings, and your notification settings and hours. • Which tickets you have read or marked unread. • While you have a ticket open or are writing a reply, a short-lived note of that, so the rest of the team can see that you are viewing or replying. It expires about 20 seconds after you leave. • An activity log of changes in the inbox, such as assigning a ticket, changing its status, sending a reply or changing a setting, with who made the change and when. The log holds identifiers and the kind of change, never the text of a message. Signing in to the web app sets cookies that keep you signed in and protect your session. They are not used for advertising or analytics.

While you are signed in, the iPhone, iPad and Mac apps register your device with Bravely Help: an installation identifier, whether it is an iPhone, iPad or Mac, the app version, whether notifications are allowed, and your notification settings for that device. If you allow notifications, the registration also holds the notification token Apple gives the app, and Bravely Help sends notifications through the Apple Push Notification service for new tickets, new replies and tickets assigned to you, as your settings allow. A notification shows the ticket number and, unless you turn off Show names and subjects for that device, the customer's name or email address, the subject and, for an assignment, the name of the team member who assigned it. With that setting off, it shows only the ticket number and the kind of notification. Outside the notification hours you set, Bravely Help sends only an update to the app's badge. Apple delivers the notification and so handles its contents. Without permission for notifications the device is registered without a token and is sent nothing. Signing out asks Bravely Help to remove the device's registration and clears the app's notifications from the device. A registration that has not been renewed for 180 days is deleted automatically.

The iPhone, iPad and Mac apps keep a copy of the tickets you have opened, your unsent drafts and your settings on the device, so they open quickly and keep your work if you lose your connection. On a Mac, the copies and drafts are in folders named BravelyHelp under Application Support and Caches in your user Library, one folder per account, the settings are in the app's preferences file, and your sign-in is kept in the macOS Keychain. An attachment you open is copied to a temporary folder, and email is displayed without keeping any website data. Signing out removes that account's data from the device: it unregisters the device, ends the sign-in, and deletes the account's copies, drafts and settings, its notifications and badge, and the temporary attachment copies. A few things that belong to the device rather than to an account stay after sign-out: a random installation identifier, the app's diagnostics files and its diagnostics settings, and, on a Mac, the update settings and downloaded updates.

The Mac app is downloaded directly from us. Apart from showing notifications, which it asks your permission for, it asks for no macOS permissions. It 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 carries nothing about your tickets or your account, and it does not send a profile of your Mac. There is no setting to turn the daily check off in this release. When an update is found, the update window lets you choose to download and install updates automatically in the future. Beta versions are offered only if you turn on Get beta updates in Settings, which is off until you turn it on and is kept for each account. When the app downloads an update, or you download the app, our website records the download, as it does for our other apps.

A team member can create a personal API token in Settings so that a script or tool, including an AI assistant they connect through Bravely Help’s interface for automated tools, can read or change tickets and rules on their behalf, within the permissions they choose. We store only a fingerprint of a token, its last four characters, its name, its permissions, when it expires and when it was last used, and we count its requests to limit them. Our request logs record which token made a request and what kind of request it was, never the token itself. Whatever a connected tool does with what it reads is governed by that tool’s own policy, not this one. A token stops working as soon as it is revoked.

The iPhone, iPad and Mac apps send four usage events: that the app was opened, with the platform and app version; whether you allowed notifications when asked; that you opened a notification, with its kind; and that you signed out. Each event carries your Bravely Account identifier and never your email address or anything from a ticket. There is no setting to turn these off in this release. The web app and our servers send no usage analytics for Bravely Help. Our account service also records your sign-ins, as the Bravely Account policy describes.

The error reports and diagnostic reports described under "Error Reports and Diagnostic Reports" are sent by the iPhone, iPad and Mac apps. The web app sends neither.

• Tickets, messages, attachments, notes and contact records are kept for as long as the team uses Bravely Help, so the team can see the history when you write again. This release has no control that deletes a ticket or a contact. • The activity log is deleted after 400 days. • Records of notifications and their delivery are deleted after 30 days. A device registration is deleted when you sign out, or after 180 days without being renewed. • Records of rules that have run are deleted after 7 days. • Team members' records and settings are kept until we delete them. Templates, saved views and rules that are deleted are hidden and kept, so the activity log can still name them. • API token records are kept, marked revoked once they are revoked. • Request logs used to operate the service are kept for a short period and then expire. • Our backups keep earlier copies of these records and files for the periods described under "Backups" below. To have your messages or your contact record deleted, or, as a team member, your membership, email privacy@bravely.dev from the address involved and tell us what to remove. Deleting your Bravely Account does not by itself remove tickets you wrote or messages you sent in Bravely Help.

Bravely Help is intended for adults working on a team. 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, through Bravely Help.

Bravely Help can send us two kinds of technical report, which you control from Help & Diagnostics in its Settings. Automatic error reports do not carry your Bravely Account identifier or your email address. Diagnostic reports carry your Bravely Account identifier. We use both only to find and fix problems, and we do not sell them or use them for advertising. Automatic error reports When the app records an error or a warning, it can send us a short report about it. It collects these on your device and sends them in small batches, about once a minute while problems are happening. A report names the app, the platform, the app version and your operating system version. For each problem it gives: • its category and type, and a short description of it with details removed • how many times it happened, and when it was first and last seen • whether you were signed in, whether you had an active plan, and whether the device was online Some apps also add how long the app had been running, the names of up to three functions in the app's code where the problem happened, and up to ten of the app's own log entries from just before it, with details removed. Before a report leaves your device, the app removes details such as email addresses, account identifiers and file paths from its text. Our server removes those details again before the report is stored, and also removes network addresses, long strings of hexadecimal characters and sign-in tokens in the common JWT format. Error reports do not contain your Bravely Account identifier or your email address, and our server does not record your IP address with them. Our apps are built to keep the contents of your tickets out of error reports. Instead of a device identifier, each report carries a code that the app works out from a random identifier it keeps for its installation and from the date, so the code changes every day. We use the code to count how many devices ran into a problem on a given day and to limit how many reports one device can send. Bravely Help for iPhone, iPad and Mac does not yet ask which country your connection comes from, so its automatic error reports are on until you turn them off, wherever you are. You can turn automatic error reports on or off at any time under Help & Diagnostics in Settings. We delete each report after 30 days, and the hourly counts we make from reports after 7 days. We keep a summary of each kind of problem with no set end date: its category, type and description with details removed, the app versions it happened in, how many times it happened, on how many devices it happened each day, when it was first and last seen, and a recent example of the log entries that led up to it. Diagnostic reports A diagnostic report is a fuller report about one problem. The app sends one when you press Send Diagnostic Report. Unless you turn automatic diagnostic reports off under Help & Diagnostics, it also sends one when something fails in a way you might not notice, such as a sync that keeps failing or a remote session that ends unexpectedly, and at most once an hour for the same kind of problem. Versions of Bravely Help that send our newer diagnostic reports, described below, can also send one, except on the web, when the app stops responding for 5 seconds or more, or the next time you open it after it closed unexpectedly. Automatic diagnostic reports are on by default wherever you are. Diagnostic reports are sent only while you are signed in. A diagnostic report contains the app version, your operating system version, a few counts and settings from the app (for example, how many documents are open, or whether sync is on) and, where the app keeps them, its own recent log entries. In versions of Bravely Help that send the newer reports, a report can also contain: • A record of your recent activity in the app: the names its code gives to its screens and to events such as signing in, changing a setting, the network going offline or a key press the app ignored, with details limited to numbers, yes-or-no values and fixed words that the app's code defines, such as a count or which part of the app something started from. Any other word is left out, so the record is built to leave out names, what you typed, which keys you pressed, file names, addresses, identifiers and the contents of your tickets. The app keeps this record, up to its latest 200 entries, only in its memory while it runs, and it leaves your device only inside a diagnostic report. • The state of the app when the report was made. For example: the screen, dialog and tool you were using, what kind of control your typing would go to, what kind of item was selected and how many, and which kinds of window were open. It also shows the state of the network, whether you have an active plan or trial, how long the app had been running and, in apps that sync, the state of sync. In some apps, it shows whether the app has the system permissions it uses. In apps with system-wide keyboard shortcuts, it can show up to eight of them, with the keys each is set to and whether it is working, and how long ago the app last noticed any key being pressed. Like the record, it holds only numbers, yes-or-no values and fixed words, never titles, names or text. • Your display and time zone: the size in pixels and the scale of the display the app is on, and the difference between your time zone and UTC; on a computer, how many displays you have; on Windows and Linux, the version of the software framework the app runs on; and on Linux, which desktop you use and whether it runs on X11 or Wayland. • Up to 50 recent warnings and errors, each with a description with details removed and, where it has one, a short code, and how many warnings and errors the app had recorded. • How the app's previous session ended (normally, in a crash, or unexpectedly, for example because it was forced to quit), with its version, how long it ran and the main steps it recorded, such as starting up. To know this, the app keeps a list of those steps in a file on your device, which it starts again each time it opens. If you have turned off usage analytics in the app, its newer reports leave out the record of your activity and the previous session's list of steps. In their place they carry a note that the record was left out and a few counts: how many entries the app recorded, combined or dropped to stay within its limit, how many event names or details its filter refused or replaced, and how many times the signed-in account changed. The rest of the report, including the state of the app and the previous session's last step, is still sent, because it describes the problem rather than how you use the app. When a different account signs in, the app first discards everything it recorded for the newer reports until the previous account signed out (or, with no sign-out, until the switch), keeping only a count of how many times the account has changed since the app started. What it recorded while no one was signed in, such as the steps of signing in, can appear in the new account's reports. The app removes details such as email addresses, file paths, and keys or tokens from log entries before they go into a report, and our apps are built to keep the contents of your tickets out of a report. In the newer reports, the app also removes text in common quotation marks, network (IP) addresses, the names of document and media files it recognizes by their endings, and your user and computer names, though some details, such as a name it does not recognize, can still appear. Some apps have a switch that records more detail in their own log for 24 hours and then turns itself off. That log stays on your device, apart from the entries that go into a report. With each diagnostic report we record your Bravely Account identifier, the user agent of the app or browser that sent it, the country your connection came from and when it arrived. When you send a report yourself, the app shows you a short code, such as DIAG-7K2QM, to give to support so we can find it. A report's log file, which holds its log entries and, in the newer reports, the record of your activity, the recent warnings and errors and any steps from the previous session, is deleted automatically after 90 days. We keep the rest of the report with no set end date, so we can see patterns across reports: its short code if it has one, your account identifier, the app and its versions, why it was sent, the counts and settings, the user agent and country, when it arrived, and, in the newer reports, the state of the app, your display and time zone details, how many warnings and errors the app had recorded and, if it had recorded any, a short label for the most recent error (or, if there was none, the most recent warning), and, where the app records it, how the previous session ended and its last step. Deleting your Bravely Account deletes your diagnostic reports from our live systems. Our data warehouse keeps its copy of what we keep from each report, without the user agent and country, under your account identifier, as the Bravely Account privacy policy describes. To have a report deleted sooner, email privacy@bravely.dev. Where reports are kept Both kinds of report are stored in database and file storage that Cloudflare runs for us, and copied into a data warehouse that we run ourselves. Diagnostic reports, apart from their log files, are also copied each night into our encrypted backups, described under "Backups" below. When our team looks into a problem, they can attach a diagnostic report to an issue in our own issue tracker, whose data Google stores for us. The issue keeps the report's short code (or its number), the app and platform, the app and operating system versions, whether the report was sent by hand or automatically, when it arrived and, for a newer report, a one-line summary of what it shows, such as the screen in use and the most recent problem. It stores the sender only as "customer account", not their account identifier or email address (for a member of our team, it stores their name or email address and their account identifier), and it keeps all of this after the report itself is deleted. While the report and the sender's account exist, our team can see the sender's email address when they view the issue.

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: for team members, your Bravely Account identifier, email address, name and role, an installation identifier and a notification token for each iPhone, iPad or Mac you use; for people who write to a support address, your email address and the name your email program sends with it, and for people who text our support number, your phone number. • Your content: the email you send to a support address and the texts you send to our support number, their attachments and pictures, and the replies, internal notes and records our team keeps about it, described in the sections above. • Internet or other electronic network activity: usage events from the iPhone, iPad and Mac apps, error and diagnostic reports, update checks from the Mac app, records of activity in the inbox, and request details such as your network address. • Coarse geolocation: a country-level signal derived from your network connection, recorded with a diagnostic report and used by your Bravely Account for consent rules. 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, help.bravely.dev and the account and diagnostics services, including the database and file storage that hold tickets, messages and attachments. See cloudflare.com/privacypolicy. • Google LLC: Firebase Authentication, which backs Bravely Account sign-in (including Sign in with Google); Gmail, which hosts the support mailbox that Bravely Help reads mail from and sends replies through; and the issue tracker described under "Error Reports and Diagnostic Reports". See policies.google.com/privacy. • Apple Inc.: Sign in with Apple, when you choose that sign-in method; the Apple Push Notification service, which delivers notifications to the iPhone, iPad and Mac apps as described under "Notifications on iPhone, iPad and Mac"; and TestFlight, which distributes the iPhone and iPad app during early access. See apple.com/legal/privacy. • PostHog Inc.: product analytics, receiving the usage events described under "Usage Analytics" and our account service’s own records of sign-ins. See posthog.com/privacy. • Twilio Inc.: carries the text messages and calls to our support number. It receives your phone number, the texts and pictures you send to that number, our replies and their delivery status, and it handles the STOP, START and HELP keywords. See twilio.com/legal/privacy. • Resend Inc.: sends our transactional email, which for Bravely Help means sign-in codes and password resets for your Bravely Account. 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.