How we keep your data safe

Sign-in and sessions

• You sign in through Google using Firebase Authentication, and the email must be verified. RepClose has no passwords of its own.
• After sign-in our server checks Google's proof and issues a session cookie. The cookie can't be read by scripts on the page, is sent only over HTTPS to repclose.com, and expires after 5 days.
• The server checks whether a session has been revoked, but cached checks can delay enforcement for up to 60 seconds.

Each seller's data stays separate

• Seller data (runs, account plans, notes, chats, templates and saved outputs) carries its owner's ID. Lists are filtered by that ID, and a single item is checked before it is shown.
• Messages submitted through public forms are stored in a separate admin inbox, visible only to RepClose administrators.
• If you ask for something that belongs to another seller, RepClose answers "not found", the same as for something that doesn't exist.
• For how opt-outs affect people data and workspace content, see Privacy.

Sharing

• A share link shows only the sections you pick. People, notes and conversations are never part of it, and private notes appear only if you explicitly include them.
• Each link carries a long random token that can't be guessed. You can revoke a link, and it then stops working immediately. Shared pages tell search engines not to index them and are not cached.
• An account can have at most 20 active links.

What leaves RepClose

To do the work, RepClose sends data to the services listed in the privacy page: the AI model that reads sources and writes plans, research and people-data vendors, our email sender, and Google, which stores our data. We send each only what its task needs. Error reports have cookies, headers, form contents and query strings removed first, and usage counts carry an internal ID and counts, not names, emails or companies.

All calls to the AI model go through one piece of our code that records what each call costs and refuses to start a call that would go over its budget.

Limits that protect the service

• A daily spending limit per seller, a daily limit on questions to Claude, and a cap on file size (2 MB for lists).
• Public forms (opt-out and contact) briefly check a salted hash of each visitor's network address in process memory to limit requests. The hash and counters are cleared daily; raw network addresses are not retained.
• If our database is out of capacity, RepClose says so and asks you to try again later.

Keys and access

The keys that connect RepClose to its services live in our hosting provider's settings, not in our code. The website, the worker that runs research, and the daily clean-up job run as separate services. We don't hold any seller's CRM login.

Keeping and deleting data

Research results and ratings are deleted 365 days after they were made. Workspace account plans and their copied people and evidence, plus other workspace content, stay until you delete them or ask us to. The privacy page has the details.

What we don't have yet

We would rather you knew than assumed.

• No security certifications or audits, such as SOC 2 or ISO 27001.
• No independent penetration test.
• No single sign-on beyond Google, and no log of who accessed your account that you can read.
• No button to delete your account or export everything; ask us and we'll do it.

If your company needs a security review before using RepClose, write to us. We'll answer what we can, with what the product does today.

Reporting a security problem

If you think you've found a weakness, contact us via hello@repclose.com. Please tell us what you found and how to reproduce it, and give us a reasonable time to fix it before you share it. Don't access other people's data beyond what's needed to show the problem.