Clear rules for
responsible research.

Retention & analytics

During the Ohio beta, account records remain until you delete the account. Account deletion removes saved plots, field logs, field outcomes, mobile tokens, and pairing records; active subscriptions must be canceled first. If you participated in the signed Ohio field pilot, the session records and receipts you submitted are part of a tamper-evident evidence chain that published results depend on, so deleting those records is completed by a RelicPlot coordinator: your account row, saved content, and mobile pairing are erased, and the retained pilot record is rebound to an anonymous subject that no longer identifies you. The pseudonymous participant id and the payload inside your signed receipt remain, because rewriting them would break the anchored chain. Expired pairing codes and diagnostic reports are automatically cleaned up, and diagnostic reports are retained for no more than 30 days. Mobile sync tokens expire after 90 days and are never stored in plaintext.

RelicPlot does not run advertising analytics in the beta. The only operational diagnostic record is a bounded, hashed error fingerprint with a support reference, app surface, and app version. It does not include precise locations, notes, photos, field history, raw stack traces, or account identity. We will publish any analytics provider and consent choices before enabling paid traffic or product analytics.

Privacy notice

RelicPlot is currently an Ohio beta. Signed-in web saved plots are stored in the private account workspace; mobile field logs and outcomes remain encrypted on the device until native account sync is connected. We do not sell your research locations, finds, or personal information.

The beta uses only the information needed to provide sign-in, saved plots, field logs, support, and abuse prevention. Precise location is used for an active field feature only when you grant permission; it is not a public signal or a substitute for consent. The beta does not run advertising analytics.

Before paid launch, this notice will be updated with the final service providers, retention periods, deletion/export process, analytics choices, and security controls.

Terms of use

RelicPlot provides research prioritization, not legal advice, permission to enter land, or a guarantee of finds. You are responsible for confirming the current rule, land manager, parcel, season, weather, and local conditions before detecting.

Do not trespass, disturb protected resources, dig where prohibited, or rely on a map color as authorization. If a source is stale, conflicting, or unclear, stop and verify with the responsible authority.

Catalog records may be corrected, withdrawn, or reclassified as source evidence changes. Automated candidates are not reviewed leads.

Billing, cancellation & refunds

The current Ohio beta is free and does not create a subscription. The $5/month figure shown in earlier product concepts is a pricing hypothesis, not an active offer.

When paid membership is enabled, checkout will show the final price, renewal timing, taxes where applicable, cancellation path, and refund terms before payment. Cancellation will stop future renewals.

For a billing question or refund request, contact hello@relicplot.com. Do not send payment-card numbers or passwords by email.

Your data choices

Signed-in users can export or delete account data from the account page; you can also request access, correction, export, or deletion through hello@relicplot.com. We verify account ownership before fulfilling a request and explain any information that must be retained for security, legal, or accounting reasons. Active subscriptions must be canceled before account deletion. When an account holds signed field-pilot evidence, the account page records your deletion request and gives you a reference id; RelicPlot support completes that erasure and confirms the reference, and the retained pilot record is anonymized rather than deleted as described under Retention.

Mobile local data can be deleted from the app’s account tab. Synced field logs preserve the same private-by-default principle as the beta. Sharing, public publishing, and team access will be separate actions with clear confirmation.