Privacy

Data we process

We may process account identifiers, email address, subscription status, quota usage, backtest setup, saved history, bot configuration, device tokens for push notifications, product interactions, device and app information, crash diagnostics, and technical logs needed to operate the service.

How we use data

We use this data to authenticate accounts, enforce quotas, sync history, run backtests, send requested signal notifications, understand feature usage, diagnose crashes, improve reliability, and prevent abuse. We do not use this data to track you across other companies' apps or websites.

Anonymous App Clip use

The App Clip works without an account. When you run its sample backtest, the selected EMA and RSI settings, locale, product interaction, and a random App Clip client identifier are sent to Backtest servers. We use them only to run the request, enforce guest quotas, prevent abuse, and diagnose service failures—not for cross-app tracking. Request and result logs plus anonymous quota records are kept only as needed for service operations and security. Email support with the approximate request time and run details to request access or deletion.

Analytics and diagnostics

We may measure product interactions, device and app information, crash reports, and performance diagnostics to understand feature usage and improve reliability. We do not use this information to track you across other companies’ apps or websites.

Research and Paper Session data

When you are signed in and cloud sync is available, we store account-linked Research Workspace titles, hypotheses, tags, strategy snapshots or fingerprints, compact run metrics and execution context, plus observation-only Paper Session settings and events. Browser-only Research data stays on your device until signed-in cloud sync is available. Paper Sessions cannot place broker orders. Deleting your account deletes these account-linked records; limited security or service logs may remain only as operationally or legally required.

Optional shared research links

A signed-in creator may opt in to an unlisted, revocable, expiring summary link or reproducible link. Backtest stores the minimum result snapshot needed to display either link and, for a reproducible link, normalized strategy rules and test assumptions. The public payload excludes prompts, capital, account data, raw trades, and candles. Public attribution uses random event identifiers and a digest of the link token, without a reporter or recipient account. A report contains its reason and optional details for moderation; blocking a result stores only a one-way digest of its token on that device. A link can be revoked and expires, although limited moderation and security records may be retained when operationally necessary. This sharing feature is not used for cross-app tracking, does not place live orders, and does not provide creator payouts. Recipients call a fixed API path with the bearer token in the request header. The server matches its one-way digest to the share and never stores the raw token. Attribution records store neither the token nor its digest and expire with the share. At the application layer, a report’s reason and optional details expire exactly 25 hours after the report is received. Firestore TTL then queues the record for physical deletion, which may finish later.

Public Community methods

Community is a public, searchable list, separate from unlisted share links. When you choose to publish, your public alias, title, summary, tags, normalized rules, market, timeframe, test assumptions and historical simulation evidence become visible. The one-click flow generates the alias and text; older app versions may submit text for moderation. Generated posts include a server rerun with standardized starting capital of 10,000, requested and actual data coverage, and provider information. This is not your original capital or verified live profit. Email, login identifiers, prompts, raw trades and candles are not published.

Publication ownership, saved methods, free Thanks reactions and creator blocks are privately linked to your account. Community creator blocks sync between signed-in devices; they differ from device-only blocking of unlisted links. Public counts include saves, Thanks, copy starts and completed reruns, not participants’ identities. Reports and copy attribution can be sent without sign-in and use event identifiers; reports include a reason and optional text. Avoid including personal information in that text.

Archived posts and posts whose source is revoked or expires disappear from public access; this does not erase the retained publication record or copies already imported by others. Account deletion removes account-linked Community records; limited deletion tombstones, moderation and security records may remain as operationally necessary. Attribution expires with its source share. Report reasons and optional details expire at the application layer 25 hours after receipt; Firestore physical deletion may finish later. Community does not place live orders, execute live copy trading or provide donations or creator payouts. Thanks is not a payment.

Third-party services

The service can use Google Cloud, Firebase, Cloudflare, Apple services, Binance public market data, yfinance market data, and OpenAI or Gemini when AI features are enabled.

Retention and control

Backtest setups and account usage are kept while the account is active or as needed for service operations. Users can contact support to request deletion of account-linked data.

Subscription terms

Subscriptions are purchased in the iOS app and governed by Apple's standard terms. Apple confirms the final localized price and renewal terms before purchase.

Trading risk

Backtests are historical simulations and do not guarantee future performance. Backtest does not place real trades and does not provide investment advice.

Your choices and contact

You can delete your account in the app or email support to request access to or deletion of account-linked data. [email protected]