To work for you, Reputcon holds sensitive things: the keys that connect your accounts, your Google Business Profile, your private customer feedback, and the intelligence we build from it. In the wrong hands, that data could damage the very reputation you trust us to protect.
AES-256 is not a Reputcon invention. It is the encryption standard that governments, national security and intelligence agencies, and the armed forces rely on to protect classified information, approved for material at the very highest levels of secrecy. We chose it because, when it comes to your reputation, nothing less is acceptable.
Your business data lives in a Postgres database with row-level security switched on, which means access is enforced by the database itself rather than by the application asking nicely. A query for another client’s rows returns nothing, not because the interface hides it but because the database refuses.
The keys you connect, meaning your Google API key and your own AI key if you supply one, are encrypted with AES-256 before they are stored, and the encryption key never leaves the server. They are written from the server and never sent back to a browser, so they cannot be read out of the page you are looking at.
The agency account that supports you is a separate role with its own two-factor requirement, and every destructive action it can take is recorded server-side rather than in the browser that performed it. An audit trail written by the thing being audited is not an audit trail.