01Who is responsible
AMANOUS PTY LTD (ABN 54 696 304 391), trading as AmaNous, is an Australian company based in New South Wales. We decide how personal information is used to operate the AmaNous app, amanous.ai and its feature-request board.
For privacy questions, requests or complaints, email [email protected]. This policy covers visitors and users, including people in the European Economic Area and United Kingdom.
02Your reading material
Speech is generated on your device. We do not need to upload your whole library to a speech-generation server.
The app stores imported text, document titles, source addresses, reading progress and related library data on your device. The current first-use flow requires sign-in; local speech generation and listening work on the device after setup.
When you import a web address, your device requests that page from its host. That host receives the request and ordinary connection information, including your IP address. Content opened through a website view may also interact with that website’s services.
Device backups, transfers and exported files can create additional copies under your operating system or storage provider’s settings. “On device” does not mean those copies can never leave the device.
We design routine product analytics to use identifiers and measurements instead of article bodies. Information you put in feedback or support emails leaves your device when sent. Error messages and stack traces may also contain document details, paths, web addresses or other personal information. We therefore cannot promise that reading content can never appear in a diagnostic report.
03Information we collect
We receive information directly from you, from the app and browser you use, and from sign-in or service providers involved in the actions below.
| Activity | Information | Purpose |
|---|---|---|
| App sign-in | Email address, account identifier, verification code, device identifier and app version. Apple sign-in can supply an identity token, account details and a name where provided. Our authentication service stores account/provider identifiers, an email where supplied, hashed refresh credentials and their rotation, expiry and revocation records. | Verify access, maintain sign-in and prevent misuse. |
| Product analytics | Account or pseudonymous identifiers, hashed email and email domain, device and app details, feature interactions, import categories, listening measurements, settings and acquisition source. | Understand use, evaluate changes and improve reliability; see the analytics and diagnostics section below for collection timing and Settings controls. |
| Crash reporting | Error messages, stack traces, timestamps, device/build context and diagnostic identifiers. Some reports may be linked to your account after analytics consent. | Find crashes, hangs and failures. |
| Feedback & support | Your message, rating, contact details if supplied, and technical details included with the report or email. | Respond to you and investigate the issue. |
| News signup | Email address; first name, optional last name and device preference if you complete the details step; subscription preferences. | Send requested AmaNous news and relevant updates. |
| Request board | Email, account/display name, requests, comments, votes, moderation history, sign-in/session records and email-delivery records. | Run, moderate and secure the board; notify you about your requests. |
| Website & connection | IP address, browser/device details, requested URLs, referrals, campaign and click identifiers, cookie/local-storage identifiers and security/rate-limit data. | Deliver and protect the site; measure use after analytics consent. |
IP addresses can be used to infer an approximate location, including country, region, city or approximate coordinates. This is different from precise GPS access. Identifiers and hashed emails can still be personal information; they are not necessarily anonymous.
When writing feedback, support messages or public posts, please do not include passwords, confidential documents or sensitive personal information. Describe the technical problem without including private reading material or sensitive details.
04Analytics & crash diagnostics
App analytics
The app uses PostHog for product analytics. The current first-use screen offers only “I Agree to Share Analytics”, with no decline or skip button before entering the reader. You can withdraw later through the app’s analytics setting in Settings. Turning it off opts out of ordinary PostHog product capture and clears the associated analytics identity.
Submitted in-app feedback can include your message and rating in PostHog. Our feedback-notification service can forward that message, its diagnostic context and an analytics identifier through Loops to the developer’s inbox. Sending a separate support email creates another copy. App analytics may use your account identifier, an email hash and email domain. On the website, a completed signup can instead identify you to PostHog by email and include your first name and device choice, if website analytics is enabled.
Diagnostics that run separately
The current app implementation starts Sentry crash reporting before analytics consent. Turning off app analytics clears its account association but does not stop Sentry’s automatic crash capture. Android also has a separate crash-recovery path that can send a stored stack trace to PostHog on the next launch regardless of analytics consent.
After a saved Android crash, startup can also enable app-lifecycle and other PostHog usage capture before the agreement step. A saved opt-out can affect whether events are sent. The app also uses PostHog for remote feature configuration; turning off ordinary analytics does not necessarily stop those configuration requests or their identifiers.
These reports can include technical context and exception messages. Disabling analytics is therefore not a complete crash-reporting opt-out in the current beta implementation.
05The website & email
Website PostHog analytics starts after you accept the analytics banner. It can record page views, clicks and interactions, browser/device information, referring and current addresses, campaign identifiers and IP-derived location. Automatic interaction capture can include visible element text. We have not enabled session replay in our current PostHog project settings.
The website stores your analytics choice in browser local storage. If you accept, it also stores an experiment assignment and the analytics SDK can store identifiers. These local-storage choices have no automatic expiry in the current site code.
To change a saved website choice, use the Analytics choices link in the website footer and select Decline to stop future website analytics. This does not automatically delete information already received by us or our providers. You can also clear AmaNous’s site data in your browser; that removes local preferences and may sign you out.
Cloudflare delivers the site and provides security and, on the board, Turnstile abuse protection. Cloudflare also loads a separate website-performance beacon that can collect page and referring addresses, browser details and performance measurements. That measurement is not controlled by your PostHog analytics choice. The site also loads typefaces from Google Fonts. These requests reveal ordinary connection information to the providers.
When you use Subscribe on the website’s waitlist form, your email is sent to Loops at that first step. It can remain subscribed even if you do not complete the later name and device questions. The form describes launch emails. You can unsubscribe using the message link or ask us by email.
The app’s update-email preference is separate from analytics consent. The current app shows that preference selected by default and lets you change it in Settings. The Android sign-in service initially adds new contacts to beta and app-update lists; a subsequent preference update can change app-update membership. An iOS contact-sync service can also transfer available email and name information from PostHog to Loops and set subscription flags to subscribed during repeated synchronisation. A server timestamp for either operation does not itself prove that you gave marketing consent.
The app preference, email unsubscribe and contact-sync paths are not yet reliably reconciled. If you have opted out and still receive updates, contact [email protected] so we can investigate and honour your request. Requested sign-in codes and necessary service replies are separate from marketing.
We also use listening milestones to trigger some feedback or review invitations. Loops is currently configured to record email opens and link clicks. This email tracking is separate from your website analytics choice.
06The feature-request board
Browsing public requests does not require a board account. Posting, voting and commenting require an email sign-in code. The board stores these records in Cloudflare D1 and uses Loops to deliver codes and request-status messages. Its separate news checkbox is not selected by default.
Unapproved requests are visible to their author and our moderation team. Once approved, the request’s title, body, category, status, vote count, author display name, team notes and published comments are public. The display name is derived from the part of your email before the @ symbol, so it may reveal your identity even though the email address itself is not shown publicly.
Moderators can access email addresses and private submissions for administration and support. Security controls include sign-in codes, session cookies, Cloudflare Turnstile and hashed rate-limit identifiers. The board’s manually defined analytics events omit request/comment text and email addresses.
Public posts can be copied or indexed by other people and search engines. Email us if you want help removing an account or contribution. We cannot guarantee removal of copies held independently by others.
07Who receives information
We use service providers for the purposes described in this policy:
- Cloudflare: site and authentication infrastructure, authentication and request-board databases, security, abuse protection and website-performance measurement.
- PostHog: product and website analytics, remote feature configuration, submitted in-app feedback and some error diagnostics.
- Sentry: app crash and error monitoring.
- Loops: contact records, sign-in and service emails, subscriptions, updates and developer feedback-notification emails.
- Apple: Apple sign-in when chosen, and app distribution; Google also distributes the Android app.
- Google Fonts: delivery of the website’s typefaces.
Cloudflare also processes Turnstile security signals for its own bot-detection improvements, as described in its Turnstile Privacy Addendum. Its role for that purpose is separate from processing on our behalf.
Our team accesses information as needed for support, moderation and operation. Relevant feedback text and diagnostic summaries can be copied into internal work records to investigate issues, including local or hosted work databases and private tracking documents. Those copies are separate from the original analytics or crash events. We may also disclose information where legally required, to protect people or the services, to professional advisers under appropriate confidentiality duties, or in a business transfer subject to applicable protections.
We do not sell personal information or provide it to other companies for their independent marketing. Sharing with the providers above is part of delivering and improving AmaNous.
AmaNous operates from Australia. We use PostHog’s US Cloud and Sentry’s United States data-storage region. Loops’ published subprocessor list identifies processing in the United States. Hosting, security, support and other operations can also involve other countries. Those primary storage regions do not describe every provider’s international infrastructure or support access.
08Why we process information
We use information to provide sign-in and requested services, operate and moderate the board, answer support requests, understand use, maintain reliability, prevent abuse, send the service and update emails described above, and comply with law.
For people in the EEA and UK, each use of personal information needs an applicable legal basis. We have not yet completed that assessment for all the processing described here, including required beta analytics and crash diagnostics that run separately from the analytics setting. The required agreement screen does not, by itself, establish freely given consent.
Where a form or service requires information, we explain that at collection. Without an email or another supported sign-in method, you may be unable to complete sign-in. The current app gates first use on the analytics agreement step; a later Settings opt-out does not itself establish freely given consent at onboarding.
09How long we keep information
Different records have different lifetimes. An expired credential is not the same as a deleted database record.
| Record | Current handling |
|---|---|
| Local library | Stored on your device until removed or reset; backups and exports have their own lifetimes. |
| App authentication records | Sign-in codes are usable for up to 10 minutes. A successfully used code is removed; unused expired records are not automatically purged by the current implementation. Refresh credentials have a 180-day validity period, which is not a deletion deadline for their stored hashes or account records. The replay guard removes expired entries during subsequent token processing. Account records and stored credential hashes do not have a scheduled automatic deletion period. |
| Board sign-in code | Usable for up to 10 minutes. Expiry alone does not purge the stored record. |
| Board session | Usable for up to 30 days. Signing out removes the active session; expiry alone does not purge all older records. |
| Board content & account records | Persist in D1; there is no scheduled automatic purge or self-service account-deletion route in the current implementation. |
| PostHog events | Our current Pay-as-you-go plan provides a seven-year event window. This includes feedback or diagnostic information sent as events. The window is not a deadline for deleting all underlying data, profiles or copies held elsewhere. |
| Sentry error events | Our current Developer plan gives newly ingested error events a 30-day retention period. Older events keep the period assigned under the plan in effect when they were received. Issue summaries, audit records and other data types can have different lifetimes. |
| Internal feedback & diagnostic work records | Feedback text and diagnostic summaries can persist after source events expire. The work-record storage paths reviewed for this policy do not automatically delete these copies. |
| Email contacts & support correspondence | A fixed company deletion period for these records has not been confirmed. Feedback notifications, separately sent support emails and attachments can each create copies. Unsubscribing from marketing is separate from deleting contact, sign-in, support or suppression records. |
We have not confirmed a fixed deletion timetable covering every category and copy above. Retention decisions must account for the service purpose, rights requests, security, disputes and specific legal record-keeping duties. A marketing unsubscribe is a request to stop marketing, separate from deleting other records. A limited suppression record may still be necessary to honour that choice.
10Your choices & rights
- App analytics: change the analytics setting in Settings, subject to the separate diagnostic behaviour explained above.
- Website analytics: decline the banner or revisit a saved choice using Analytics choices.
- Email updates: use the unsubscribe link, the app’s email preference or contact us. Sign-in and other necessary service messages are separate.
- Local reading data: remove content or use Reset App Data. This does not delete data already sent to providers or remove backups and exports.
- Information we hold: email us to request access, correction or deletion, or to raise a concern.
Depending on the law that applies, you may also have rights to restrict or object to processing, obtain a portable copy, withdraw consent and complain to a supervisory authority. Some rights have legal exceptions. Where the GDPR or UK GDPR applies, your right to object to direct marketing is absolute.
Send requests to [email protected]. Identify the service and email or account involved, but do not send passwords or sign-in codes. For access, correction or deletion, we may ask for proportionate verification and will respond within the time required by applicable law. For a marketing unsubscribe, we will not require account login, extra personal information or a fee beyond ordinary transmission costs. We do not have a self-service server-side deletion flow in the current app or board implementation.
Where the GDPR or UK GDPR applies, you have the right to complain directly to your EEA supervisory authority or the UK Information Commissioner; you do not have to complete our internal process first. Where Australian privacy law applies, you can also complain to the OAIC, following its applicable complaint process. These rights do not remove other available remedies.
11Children & families
AmaNous is a general-audience text-to-speech reader with no general minimum age. A store content rating does not determine whether a child can consent to analytics, marketing or other data processing. Age and parental-authorisation requirements differ by country and by processing activity.
If you are a parent or guardian with a concern about a child’s information, contact [email protected] so we can investigate and handle an appropriate request.
12Security & policy changes
Our services use HTTPS for network requests and authenticated controls for private board administration. No service or storage method can guarantee complete security. Please protect your device, email account and verification codes.
Each version shows its effective date. We will provide additional notice of material changes where required. If a new purpose requires consent, we will obtain it before relying on it.
For questions or a copy of this policy in another accessible format, email [email protected]. See also our Terms of service.