Privacy Policy — App Inquirer

If you sign up on appinquirer.com, we keep your email address so we can send you the launch email and then the weekly newsletter. If you ask us to list your app, we keep your name, your email address, your app’s name and link, and the name of your studio or company if you give it, so an editor can review it; your email address is never shown on the site. Both forms keep a salted hash of your network address for the day, never the address itself, to cap sign-ups. We also contact app makers whose business contact details are public, to invite them to be listed. Anyone can ask us to stop, and then we never contact them again. We do not sell any of this.

The sign-up form for readers asks only for your email address. We use it to send you the launch email when App Inquirer opens, and after that the weekly newsletter. To stop them, or to have your address removed, email privacy@appinquirer.com.

The form for app makers asks for your name, your email address, your app’s name and a link to it. It also asks, optionally, for the name of the studio or company you publish under, and has an optional box to ask us to consider your app for a story. Sending it asks us to list your app when App Inquirer launches. We store what you send, and an editor reviews each request. If we list your app, we write the listing ourselves, in our own words. We use your name and email address to reply to you about your request and your listing. Your email address is never shown on the site. We also keep a record of you and your apps with the outreach records described under "Reaching Out to App Makers", so we know you have asked to be listed and do not contact you about it as if you had not.

To stop the forms being flooded, each form accepts a limited number of sign-ups a day from the same network address. To count them, we store a hash of your network address, made with a secret value and the day’s date, so it changes every day and cannot be turned back into the address. We store that hash with your sign-up. We never store the network address itself.

Each listing on App Inquirer has buttons that take you to the app’s store page or website. We count clicks on those buttons, per app per day, so we know which listings readers find useful. The counts are totals: they do not record who clicked. App Inquirer does not track you across other websites.

To invite app makers to be listed at launch or featured in a story, we gather the public business contact details of app makers from public sources: the directories and communities where they post their apps, and the contact details they publish on their own websites or store listings. For each app maker, we keep: • Their name, and the contact email address or contact page they published. • Their apps. • Where we found them. • Our notes about them, and the messages we have exchanged. We use these details only to invite app makers to be listed or featured, and to keep track of those conversations. Each email is written and sent by a person, one at a time. Anyone can ask us to stop, by replying to one of our emails or by emailing privacy@appinquirer.com. When you do, we keep a "do not contact" record, so that we never contact you again. We never sell any of this.

Mail sent to App Inquirer’s addresses, such as team@appinquirer.com, jeff.schiesser@appinquirer.com and our team members’ own addresses, reaches our shared team inbox and our support tool, so our team can read and answer it. The support tool has its own privacy policy, which describes what it keeps. Privacy questions can go to privacy@appinquirer.com, which reaches the same people as privacy@bravely.dev.

Our editors sign in to App Inquirer with a Bravely Account, which is covered by its own policy at bravely.dev/privacy/bravely-account. Readers and app makers do not need an account to use appinquirer.com.

• Sign-ups for the launch email, and requests to be listed, are kept until you ask us to remove them. • Outreach records are kept until the app maker asks us to remove them. A "do not contact" record is kept for good, so that we never contact that person again. • The salted hash of a network address is kept with the sign-up it belongs to. The day’s count of sign-ups from that hash, which is stored with the hash, expires when the day ends and is cleared out after that. • Click counts are kept as totals per app per day, with nothing about who clicked. To have your details removed, email privacy@appinquirer.com from the address involved and tell us what to remove. If you ask us never to contact you again, we keep only what we need for the "do not contact" record.

App Inquirer’s sign-ups and outreach are 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. If you believe a child has signed up, email privacy@appinquirer.com and we will delete the record.

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 (including limiting sign-ups), inviting app makers whose business contact details are public to be listed or featured, keeping a record of those conversations and of who has asked not to be contacted, and improving App Inquirer. We balance these against your rights and do not use them to justify intrusive tracking. You can object at any time by emailing privacy@appinquirer.com. • 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: the email address you give us; for app makers, your name; for app makers we contact, your name and the contact email or contact page you published; for our editors, their Bravely Account identifier. • Professional or commercial information: for app makers, your apps, their names and links, and whether you asked to be considered for a story; for app makers we contact, where we found your details and our notes and messages with you. • Internet or other electronic network activity: a salted hash of your network address that changes each day, kept with a sign-up to limit sign-ups, and counts of clicks on each app’s buttons, per app per day, which are not linked to anyone. • Your content: the email you send to App Inquirer’s addresses and our replies, described in the sections above. 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" 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 appinquirer.com, including the database that holds sign-ups, the records described under "Reaching Out to App Makers" and the daily click counts. See cloudflare.com/privacypolicy. • Google LLC: the email service that receives and sends mail for App Inquirer’s addresses, and Firebase Authentication, which backs the Bravely Account sign-in our editors use. See policies.google.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.