Privacy

This notice applies to people who request or receive beta access, use the application, submit feedback or contact the operator. The product also stores copies of public issuer and regulator documents; those documents may contain professional names and roles already published in the underlying filing.

• Account and application information: email address, email-verification state, name, organisation, professional role, optional intended use, account status and application role.
• Saved research preferences: canonical issuer IDs in an account-backed watchlist, plus reporting and filter choices stored in first-party browser cookies and peer selections stored in local storage. The account watchlist is available across devices; the other preferences remain browser-specific.
• Beta usage events: an internal account ID, one of a fixed set of product behaviors, the UTC event date and a server timestamp. Events are deduplicated to one record per account, behavior and day.
• Service and security information: technical request data processed by hosting and authentication services, such as IP address, device/browser details, timestamps and the requested route. The application does not deliberately add those fields to product analytics.
• Feedback and support information: the message a tester chooses to submit, redacted route context and an opaque internal user identifier. Feedback screenshots and session replay are disabled for the initial beta.
• Administrative records: an append-only record of account decisions, the acting administrator and any reason entered for that decision.

Information is collected from account, profile and feedback forms, automatically when the service is used, and from public disclosure documents. We use it to assess and administer beta access, authenticate users, provide saved features, deliver account messages, secure and troubleshoot the service, understand aggregate usage and improve data quality. Name, organisation and professional role are required to submit a beta application; intended use is optional.

When you report a figure, we store your internal account identifier, the affected field, your explanation, any public source URL you choose to supply, and a snapshot of the original approved source rows. The report also includes the figure shown in Evidence, the six reporting controls, display currency, application release and dataset publication reference when available. We record whether custom equivalent prices were present, without storing those prices. You can review the attached context before submitting. Custom prices, search terms and export contents are not attached.

Reports are available to you and authorised administrators, separately from behavioural analytics. Administrative status changes and response notes form a case history. Reports do not automatically change published data; corrections go through source QA.

We use Sentry for errors and feedback and Vercel Web Analytics for aggregate pageviews. Query strings, hashes and dynamic company, project and source identifiers are removed before pageview data is sent. Sentry receives a generated internal user identifier and safe, redacted route context when available. A separate first-party table records only fixed, daily-deduplicated beta behaviors so activation and return rates can be evaluated across approved accounts. We count active UTC days, not sessions or exact action totals. Administrators and marked test accounts are excluded. Earlier attempt-based events remain separate from the current completed-action definitions.

Our telemetry controls are designed not to send passwords, session tokens, cookies, email addresses, names, organisations, document contents or equivalent-price settings. First-party usage events contain no URL, query, entity, source, free text, arbitrary properties or browser fingerprint. Feedback screenshots, Session Replay and Vercel custom analytics events are disabled. No advertising trackers are configured, and personal information is not sold or rented.

Vercel's anonymous visitor hash resets daily, so its pageviews cannot reliably be joined to approved accounts or used for cross-day retention. Its custom events are aggregate and plan-dependent; we do not use them for the account-backed beta-learning measures. See Vercel's analytics privacy documentation and custom-events documentation.

We use Clerk for authentication, Neon for the application database, Vercel for hosting, file storage and aggregate analytics, Sentry for error monitoring and tester feedback, and Resend for account-activation email. These providers process information on the operator's behalf to deliver their services.

Some providers and their subprocessors operate outside Australia, including in the United States, so account, email-delivery, diagnostic and service information may be processed there. We use provider contracts, configuration and access controls to manage that processing.

Clerk uses cookies required to keep a user signed in and protect the account. Reserve Resource uses first-party cookies to remember data presentation choices and local storage for the browser's peer set. These are product preferences, not advertising profiles. Vercel Web Analytics is configured as cookie-free analytics. Clearing site data resets browser-only preferences and may sign the user out.

We retain information only while needed to run and evaluate the beta, maintain security and audit records, resolve disputes and meet legal obligations. When it is no longer needed, we delete or de-identify it where reasonably practicable, subject to backup, security and legal requirements. Account-linked beta usage events are removed after 180 days. Twelve months after a data case closes, we remove reporter identifiers, report text, supporting URLs and personal history notes. Original public evidence and case status history remain for the correction audit trail. The routine runs after verified backups; protected backup copies expire under their separate retention schedule.

Access to the application and account data is restricted by account status and role. Telemetry is minimised and route details are redacted. Database backups are held in a separate private store. No online service can guarantee absolute security; suspected incidents are investigated and handled under applicable law.

The research product archives copies of issuer filings and regulator announcements that were already publicly released. The application exposes source links to authorised beta users, but the underlying filing and an archived object URL may also be publicly accessible. Do not submit confidential or private documents for ingestion.

If you email us, our email service processes the message and any attachments so it can be delivered to the monitored operator inbox. We use that correspondence to respond and to operate or protect the service.

You may ask to access or correct personal information, request deletion where applicable, withdraw from the beta, or raise a privacy complaint by emailing hello@reserveresource.xyz. We will acknowledge and investigate privacy complaints and explain the outcome. Depending on where you live, you may also have the right to complain to a privacy regulator.

We may update this notice as the beta or its providers change. This page shows the current version date; material changes will be communicated to active testers where appropriate.