Last updated 3 October 2026

Privacy Policy

What Repath collects, why, where it is kept, who else handles it, and how long it stays.

01

Who we are

Repath (tryrepath.com) provides progressive delivery for AI applications: canary rollouts, quality evaluation and automatic rollback for prompts and models. Questions about this policy go to hello@tryrepath.com.

02

What we collect

  • Account: your name, email address and a bcrypt hash of your password. We never store your password itself.
  • Requests you send through Repath: metadata — model, provider, token counts, latency, status, estimated cost, time — and, unless you turn capture off, the prompt and the response.
  • Evaluations: the scores and written reasons our judge gives each sampled response.
  • Provider keys you save: encrypted at rest and used only to call those providers for you.
  • Billing: your plan, subscription and payment identifiers, amounts and status. Card, UPI and bank details go to Razorpay and never reach us.
  • Technical logs: request paths, errors and timings needed to run and secure the service.
  • Product analytics: which pages of tryrepath.com and the dashboard you visit, what you click, the page that referred you, your approximate location from your IP address, and recordings of sessions in the dashboard. Recordings mask every form field, API key, prompt, response and request body before they leave your browser, so none of those are ever recorded.
03

How we use it

To run the service: route and proxy your requests, judge response quality, decide whether a rollout advances or rolls back, show you the request log, bill your plan, send transactional email (password resets, receipts, alerts you configure) and keep the service secure.

Product analytics show us where the site and the dashboard are confusing or broken, so we can fix them.

We do not sell your data, use it for advertising, or use it to train models.

04

Where it is stored

On Amazon Web Services in the Mumbai region (ap-south-1): a PostgreSQL database encrypted at rest, and application servers with encrypted disks. Traffic is encrypted in transit with TLS. Database backups are kept for seven days.

05

How long it is kept

  • Prompts and responses: 7 days on the Trial, Indie and Starter plans, 90 days on Pro and Enterprise, then deleted automatically. The window is fixed when a request is recorded.
  • You can switch prompt and response capture off in Settings at any time.
  • Request metadata and evaluations: while your account exists.
  • Product analytics: events up to one year; session recordings 30 days.
  • Your account and everything in it: deleted within 30 days of your request. Backups containing it expire within a further seven days.
06

Who else handles it

We use these sub-processors, each only for the purpose shown:

  • Amazon Web Services — hosting, database and transactional email (SES).
  • Vercel — the AI Gateway our judge uses; sampled prompts and responses pass through it to be scored.
  • Razorpay — subscriptions and payments.
  • PostHog (United States) — product analytics and session recordings, as described above.
  • The model providers you configure — your requests are forwarded to them, using your own keys and accounts, under their terms.

If your data must never leave your own network, Repath can be deployed inside it.

07

Cookies

One cookie keeps you signed in; it is HttpOnly and sent only over HTTPS. Your light or dark theme choice is remembered in your browser's local storage. PostHog sets a first-party cookie to recognise return visits for product analytics. There are no advertising cookies, and nothing is shared with ad networks.

08

Your rights

You can ask us for a copy of your data, to correct it, or to delete it, by emailing hello@tryrepath.com from your account's address. We answer within 30 days.

09

Changes

When this policy changes we update the date above, and for material changes we email account owners before they take effect.