Security and data use

Encryption

• On the way: everything between your device and Reposance is encrypted with TLS, and our site tells browsers to use only secure connections.
• At rest, with a key unique to you: your files, recordings, made images and documents, messages in spaces, your cloud computer's saved sign-ins, the keys to your connected apps and your own model keys. We use AES-256-GCM, and keys are managed by us.
• At rest, everything else: chat text and memory sit on encrypted servers, behind database rules that let each account reach only its own rows.
• Not end-to-end. Messages in spaces are encrypted on our servers, but Reposance can process them to help you, so they are not end-to-end encrypted.
• Deleting your account destroys your keys, so what was encrypted with them can't be read again, even in backups.

Passkeys and sign-in

• Passkey first. A passkey lives on your device and can't be phished or reused on a fake site. You can also sign in with Google, Apple or Microsoft, or with a one-time email code.
• Codes are short-lived: an email code lasts 10 minutes and allows 5 tries. We store codes and session tokens only in a scrambled (hashed) form.
• Sessions end: after 7 days without use, and after 30 days at most. You can see and end your sessions in Settings › Security.
• Step-up for what matters. Deleting your account, loosening what Reposance may do, and paying ask for your passkey again.

Asks before it acts

Reposance reads freely to help you, but what it does in the world goes through a gate that sits outside the AI model. The model can only propose; the gate decides, and when in doubt it says no.

• You see the exact step. An approval shows who it goes to, what it says, what it costs and where, and your yes is bound to exactly that. If anything changes, it asks again.
• Hold to confirm. You press and hold to approve, so a stray tap can't send anything. Paying also asks for your passkey.
• Per-app switches. For each connected app you choose Off, Asks first or On. Acting starts at Asks first, and loosening it asks for your passkey. Sending, paying, deleting and anything that can't be undone always ask.
• Small private changes, such as adding an event only you will see, may happen straight away. You're told, and you can undo.
• While you're away. A standing order you set up runs only the plan you approved, for at most 90 days, and spends nothing unless you set a cap. It never messages someone new, changes account or payment settings, deletes, or accepts new terms on its own. If a scheduled task reaches a step that needs you, you have 20 minutes to answer; no answer means nothing happens.
• Stop any time. Every task has Stop, and you can take over whenever you like.

Your cloud computer

For tasks on the web, Reposance uses a computer of its own in the cloud: a private browser for you, in the United States, that pauses when idle and keeps your sign-ins between tasks, encrypted with your key.

• It reads and searches freely. Anything else it types, every upload, and every step that books, sends, submits, saves, pays or deletes needs a one-time permission for exactly that step.
• Your secrets stay yours. It never types passwords, card numbers, expiry dates, security codes or one-time codes, and never touches a payment form's card fields. When it reaches one, you take over.
• No sign-ins, no accounts, no CAPTCHAs. It never signs in for you, never creates accounts and never solves CAPTCHAs. You do those yourself; it keeps the session, never the password.
• Paying is capped. A purchase you approve uses a card that works once, for one seller, for the amount you approved. Reposance never holds or moves your money.
• No quizzes or exams. It never opens, reads or acts on a live quiz, exam or proctoring page.
• It won't be used for abuse: mass messaging, large-scale scraping, account farming, attacks on passwords, card testing, fake engagement or harassment are refused, and there are daily limits on sign-ups, messages, payment attempts and form submits.
• Gated web access. Secure sites only, with private network addresses and known malware and phishing sites blocked.
• Pictures, not video. It keeps still pictures of a task for 30 days so you can see what it did, and records no video. It keeps no picture while a secret field is in use, while you're in control, or on a quiz page.

The Chrome extension

The extension lets Reposance do tasks in your own Chrome, for sites that block cloud browsers.

• Its own tab group. It acts only in tabs in the "Reposance" group. Chrome shows its own bar while it works, and the page shows a banner with Stop.
• The same limits: no typing into password, card or one-time-code fields, no screenshots while they're in use, no CAPTCHAs, and no quizzes or exams.
• Signed permission for every step that counts. It submits, sends, pays or deletes only with a one-time permission from our servers for exactly that step, and only a real press counts as your hold to approve.
• Off during exam hours. Nothing runs in that browser while an exam is on.
• Pairing keys stay in your browser. Unpair from the extension or from Settings at any time; removing the extension deletes everything it stored.

What the extension sends to Reposance is described in the Privacy policy.

Connected-app keys

• Encrypted with your key (AES-256-GCM), tied to your account so they can't be used for anyone else.
• Only what it needs. Each connection asks for the access its features use, listed scope by scope in the Privacy policy.
• Disconnecting deletes the stored keys; for Google we also revoke our access with Google. Your own model keys are never shown again after you save them.

Staff access

Nobody at Reposance can read the content of your account: not your mail, files, notes, chats or memory. There is no back door for staff, not even if you ask us to look. Support can see account details such as your plan and usage, never content. Every staff action is recorded.

Defences against prompt injection

A web page, email or file can contain hidden instructions meant to trick an AI. Reposance has several defences. They lower the risk a lot, but no defence is perfect.

• Content is data, not orders. Text from pages, mail and files is marked as untrusted, and Reposance is told never to follow it.
• A sealed reader. Mail and documents are first read by a separate model that has no tools and can only fill in a form.
• The gate decides, not the model. A recipient, payee or amount that came only from untrusted content is refused, and untrusted input together with access to your private data means it must ask you first.
• Data can't slip out. Each task can only reach the sites it needs, and sending your data to a new place asks first.

What we never do

• sell your data, or use it for ads;
• train or evaluate AI models on your data;
• let staff read your content;
• type your passwords, card numbers or one-time codes, or keep your passwords;
• solve CAPTCHAs or create accounts for you;
• open, read or act on a live quiz or exam;
• move money from your bank (bank connections are read-only);
• send, pay or delete without your yes.

Reporting a vulnerability

If you think you've found a security weakness, please tell us privately at support@reposance.com with "Security" in the subject. Include what you found, how to reproduce it, and what it could allow. To report abuse of Reposance, write to abuse@reposance.com.

• Please don't access, change or delete other people's data, and don't test in a way that could harm Reposance or its users.
• Give us a reasonable time to fix it before you tell anyone else.
• We'll confirm we got your report, keep you posted, and thank you publicly if you'd like.

If something goes wrong

If a breach puts your information at risk, we contain it, tell you what happened and what you can do, and report it to the privacy regulators as Canadian, Quebec and US law requires. If we ever have to pause tasks to keep you safe, we stop them first and explain afterwards.