Privacy Policy

The short version

We collect the minimum to run your account and bill you: your GitHub identity and Stripe payment records. We never see, store, or proxy your AI agent credentials or tokens — you authenticate Claude, ChatGPT or Gemini directly inside your own Box, which we never inspect.

What we collect

• GitHub OAuth data — your GitHub user ID, username, email address, and avatar URL, provided by GitHub when you sign in. We use this to identify your account; we do not request write access to your repositories.
• Billing data — handled by Stripe. We store the Stripe customer/subscription ID and payment status; we never see or store your card number.
• Box metadata — plan, status, hostname, creation and expiry timestamps, and referral attribution. This is operational data needed to run the service, not the contents of your Box.
• Referral data — if you arrive via a ?ref= link, we store that code locally in your browser and attach it to your checkout so referral credit can be applied.

What we never collect

• Your AI agent tokens or API keys. Claude, ChatGPT, Gemini, or any other agent CLI login happens entirely inside your Box, over your own connection — it never touches rel4i's servers.
• The contents of your Box — your code, terminal sessions, or files. rel4i connect talks directly to your Box; we don't proxy or log that traffic.
• Your card number or full payment details — that's Stripe's job, not ours.

Where your data lives

Boxes run on Hetzner Online GmbH cloud infrastructure in EU data centers. Our own dashboard/API runs behind Cloudflare. Billing runs through Stripe. Authentication runs through GitHub OAuth. See the subprocessor list below.

Subprocessors

• GitHub (Microsoft) — OAuth sign-in.
• Stripe — payment processing, billing, tax.
• Hetzner Online GmbH — Box infrastructure (EU regions).
• Cloudflare — edge/DNS/CDN for rel4i.com and the API tunnel.

Cookies

We set a single session cookie (via better-auth) to keep you signed in. We don't use third-party advertising or tracking cookies.

How long we keep things

Box metadata is kept while your account exists. During the alpha, Boxes are ephemeral — when a Box expires or you cancel, the Box and its disk are permanently deleted; we do not currently snapshot or retain Box disks. Billing records are retained as long as legally required for tax purposes.

Your rights

You can request access to, export of, or deletion of your account data at any time by emailing hello@rel4i.com (see also /impressum). A self-serve export/delete flow ships before general availability.

Locking ourselves out — the honest beta status

Our goal is that rel4i technically cannot access your Box — that only you can. This is on the roadmap and not yet fully in place. Here is exactly where we are today, in the beta:

• What is already true: your Box is your own VM (not a shared container), you hold root, inbound ports are closed and SSH is off by default, and you log your agent subscription in yourself on the Box — rel4i never proxies or stores your Claude / Codex / Gemini tokens.
• What is NOT yet true: rel4i currently retains an access credential to your Box (used to operate and support it). So a beta Box is not yet one that only you can reach. We do not access it except to run the service or at your request.
• What is coming (v1.5): a real lockout — at handover we rotate away and delete our own credential, and your data lives on a volume encrypted with a key only you hold, so even a provider-level snapshot or rescue only ever sees ciphertext. Plus open, verifiable image builds so this is provable, not just promised.

Honest day-zero note: we build the base image, so trust in that image applies until the verifiable-build work lands.

Changes

We'll update this page as the system evolves and note the date at the top.