How it works for you

Through the app itself, never through a password. When a job needs your calendar, your inbox, your Facebook page or your books, it asks you to connect that app to your repryntt account. Connecting opens the app’s own sign-in page in a window we cannot read. You sign in there, the app issues its token to Nango, our integration provider, and what reaches your AI is a connection — never a password.

Connecting an app never asks for its password. The card that asks about an app has three buttons: connect it, do it yourself, or not this one. Your AI never sees a password.

You can cut off any app at any time. Revoke its access in that app’s own account settings (Google, Microsoft, Meta or Intuit). From then on your AI cannot use it, and only you can connect it again.

Anything leaving your company. An email, a post, a text, a purchase. It stops at an approval card that shows you the whole thing — not a summary of it — lets you rewrite the subject and the body, and sends exactly what you leave. Changing it does not send the old version.

Every kind asks every time, by default. The one exception is small residual actions, which can earn their way out after ten approvals in a row that you did not have to edit. An edit, a rejection or an opt-out puts that count back to zero. You can set every kind to ask every time in Settings → Approvals.

An app it has not got. A job that reaches a wall puts a card in your chat with one sentence about what connecting grants, and waits. It does not fail and it does not quietly work around it.

Spending. Nothing may spend your money by default. A purchase stops at a card showing what and how much, and it stays stopped until you say yes.

These run before anything is drafted, not after, and an approval cannot override them:

Never anyone who has opted out. One ledger, and it fails closed: if it cannot be read, nothing is sent.

Never twice inside seven days, and never more than three times if they never answer.

Never more than five first emails in a day. Five named people it has actually read about beats fifty it has not — and a cap you can clear in an afternoon is what makes the approval card real work rather than a rubber stamp.

Never a law firm, and never businesses in an excluded trade. That is not an opt-out; it is a whole category we do not write to.

On your own computer, when you run it there. The download runs on the computer you install it on. Your memory and your logins stay there, not in someone else’s cloud.

Apps you connect to your account are the exception. Their tokens are held by Nango, our integration provider — not on your computer and not in our database — and each one is scoped to the permissions that app’s own consent screen listed.

In our cloud, when you run it there. That work is kept in your repryntt account.

It thinks on your included hours, wherever it runs. The plan’s 20 hours run on our AI service — one pool for your computer and our cloud, with no key to get. From your computer, the text of each request passes through our service to the model; we log the usage, never the content.

Or on your own AI, on your computer. Give it your own AI key, a model running on that computer, or a coding subscription you are signed in to there, and it thinks with that instead. Those calls do not pass through us, and the hours stay untouched.

Either way, one call at a time. When it calls a model, the text of that one call goes to the provider and nothing else goes with it. None of it is uploaded for training unless you turn on receipt sharing in Settings, which is off by default.

The work, while it happens. Under the message that asked for it: each step as a plain sentence, the hostnames it read, and whether a step failed. The contents of what it read and wrote are not on that strip — you get where it went and how much came back.

Every decision you made. An approval records which version of the draft you read, what you changed, and whether the act actually went out afterwards — so “approved” and “sent” are two different facts on the record rather than one assumption.

A step that was refused is a step, not a silence. When a wall stops something, that step is on the strip marked as having failed rather than being dropped from it.

One app — revoke its access in that app’s own account settings. Settings → Connect your apps connects or reconnects one.

One company — deleting it removes the company and its whole activity history. Anything on your own accounts — your deployed site, your GitHub, your Stripe — is untouched, because it was always yours.

Stop a job now — the stop control on a running shift halts it and stops the spend with it.