WalkthroughMT5 PackWhy RNMEPricing
Sign inAdd RNME to your AI

DRAFT — REQUIRES HUMAN LEGAL REVIEW

Privacy policy (draft)

> Current authority: `plan 8.md` (Phase 66+). Where Plan 8 conflicts with earlier plans, Plan 8 wins. Plans 1–7 are historical evidence.

DRAFT — ordinary Terms / Privacy / Refund / Risk pages with electronic acceptance at checkout (Plan 8). Outside-counsel sign-off is non-blocking archived process, not a launch gate.

_Last updated: 2026-08-05 (draft; Plan 8 paid Pack loop + Build Pass / Live model)_

Summary

We collect account, billing, build job metadata, Pack artifacts, and optional post-delivery monitoring telemetry necessary to operate the service. We do not collect broker passwords or fund your AI provider inference at launch.

Company cloud systems do not store broker trading passwords. MT5 account login stays with you and your broker.

Data we collect

| Category | Examples | Purpose |

|----------|----------|---------|

| Account | Email, auth identifiers | Sign-in, billing |

| Build jobs | Build Summary hash, job status, diagnostics | Pack delivery |

| Pack artifacts | Source, compiled binary, manifest hashes | Secure download, My Tools |

| Backtests | Parsed metrics, settings, report hashes | Build Report / evidence |

| Device (optional) | OS, Connector version, pairing token hash | Live monitoring only |

| Monitoring | Heartbeats, trade event metadata (redacted) | Optional Live continuity |

| Billing | Stripe customer / Build Pass / Live subscription IDs | Entitlements |

Data we do not collect

  • Broker trading passwords (not stored in company cloud)
  • Full payment card numbers (handled by Stripe)
  • Unrestricted user source code by default in logs

Minimum telemetry payload (R29)

Default cloud telemetry is redacted. The minimum operational set is documented in engineering code (`@tb/shared` monitoring privacy + `docs/SECURITY_MODEL.md`):

Excluded by default: account number, user filesystem paths, strategy source, free-form log dumps, broker credentials, device secrets.

Opt-in where product settings allow: broker label, symbol, and performance aggregates.

Flood / size abuse controls apply to telemetry ingest (`apps/web/lib/security/telemetry-flood.ts`).

Trading execution

We do not run trades on your behalf or host a per-user trading terminal. Paid Pack builds use an isolated managed compile/test environment on RNME-controlled Windows workers. Optional Live monitoring uses the RNME Connector on your Windows machine after a ready Pack exists (and Connector certification).

Managed build plane (Plan 8)

For Build Pass customers, MQL5 source you approve is submitted through our build protocol, compiled and checked in isolated cloud Windows workers, and returned as an MT5 Pack. Workers are wiped between jobs. We do not use broker credentials or live account data in cloud builds. Ordinary Terms / Privacy / Refund / Risk with electronic acceptance apply — MetaQuotes/counsel programs are not launch gates.

Optional local agent (RNME Connector)

The Windows Connector is optional and post-delivery. It runs on your machine for Live monitoring, Weekly Review, and installed-version evidence — not required to receive a Pack. Only metadata and optional redacted telemetry sync to our servers. The Connector binds to loopback for local control and does not store broker passwords.

Retention

  • Free / Build Pass: no Live monitoring retention (0 days of Live telemetry)
  • Live: up to 90 days of redacted monitoring telemetry while subscribed
  • Account and billing records retained while the account is active and as required by law after deletion requests

Your choices

  • Disconnect optional Live Connector / revoke device links used for Live
  • Export diagnostics (redacted)
  • Request account deletion (subject to legal retention)
  • Opt out of optional telemetry in Account settings

Processors

We may use hosting (e.g. Railway), database/auth (e.g. Supabase), payments (Stripe), email, and analytics under contractual safeguards. Exact processor list may update; current contacts below.

Contact

Privacy: legal@rnme.app · Support: support@rnme.app

---

Public page: `/privacy`

Draft — keep accurate; outside-counsel sign-off is non-blocking under Plan 8.

TermsRefundRiskSecurity