Skip to content
Early access is open →
Repic
LoginJoin early access
Trust & responsible AI

The rules we set before we needed them.

Repic is built on someone's voice, likeness and brand. That only works if the boundaries are clear – so here they are, in full, with nothing hidden behind an accordion.

Draft principles – under legal review before launch. Voice-cloning consent law varies by region.
01Consent

Every voice clone starts with a recorded yes.

Before Repic learns a voice, you record a short consent statement in that same voice. No statement, no clone. And the rule underneath it is absolute: you can only clone your own voice. Even with their permission, you cannot clone someone else's on Repic.

Recording0:07

“I consent to Repic creating an AI voice from my own voice.”

Consent recorded & stored with the clone
Where the voice key lives
Your browserno key, ever
Repic serverskey stays here

The cloning key is generated and used server-side only. It is never sent to your device, so it can't be copied from there.

02Verification & anti-misuse

Hard to misuse, by design.

Consent gating is enforced, not suggested. No celebrity or third-party cloning. And the cloning key never leaves our servers – it isn't sent to your browser, so it can't be lifted from there. Suspected misuse jumps the queue at contact.

03Ownership & deletion

Your voice and twins are yours to remove.

You own your voice model and every twin version. Delete a twin version in the product and its voice model goes with it – no support ticket, no waiting. Close your account and everything follows, surviving only briefly in backups.

Twin versions
Voice v3Active
Voice v2
Delete

Deleting a version removes its voice model too. Nothing lingers on the active clone.

04The assistant's permission model

Nothing that matters happens without your yes.

The assistant explains its intent first. Anything that changes or deletes your brand waits behind an Allow / Disallow card. “Just do it” phrasing can't skip the gate, and Disallow means nothing changes – verified.

RRepic AssistantNeeds approval
I'm about toRegenerate your palette – warmer
What changes4 palette colors shift warmerLogo kept, exactly as you asked
AllowDisallow

It states its intent in plain words before doing anything.

Changes and deletions are gated; reads and navigation run instantly.

Your exclusions – “keep the logo”, “not salesy” – are respected and forwarded.

See the full permission model →
What we store
Your Brand PersonaThe 25 fields you describe
Runs & historyEvery generation, saved
Uploaded assetsLogos, photos, voice audio
Export anytimeDelete anytime
05Data handling

We store what runs the studio – nothing you can't take back.

Your persona fields, your runs, and your uploaded assets – held so the studio can do its job. We don't sell your data or train models for other customers on it. Export or delete any of it whenever you like. Full detail in the privacy policy.

06Disclosure

When it's AI, we say so.

We label AI-generated audio and likeness content where disclosure is required, and we support you in doing the same. As EU and regional rules land, this section moves first.

AI-generated

Generated audio and likeness carry a clear label wherever disclosure applies.

These are ours to keep – and answerable.

We wrote these before we needed them, and the same two people who built the permission gate answer when you write in. If we ever fall short of what's on this page, tell us – it reaches us directly.

Raise a concern →
Responsible by default

Build on a studio that asks first.