Security at CorrespondR

Last updated: 19 October 2026

CorrespondR is built for conversations between companies: with clients, suppliers, accountants and advisers. This page explains, in plain language, how we protect what you share, where it is stored, and who can see it. For how we use personal data, see our Privacy Policy.

Where your data is stored

• The service and its database run in Frankfurt, Germany, inside the EU (Vercel for hosting, Neon for the PostgreSQL database).
• Files and profile photos are stored with Cloudflare R2, in Europe (Cloudflare's Eastern Europe region).
• Your conversations, files and account details are therefore stored in the EU. Some service providers outside the EU handle specific tasks, such as sign-in and sending emails (see the list below).

Encryption

• In transit: every connection to CorrespondR (website, desktop app and phone apps) uses HTTPS (TLS). Unencrypted connections are not accepted.
• At rest: the database and file storage are encrypted at rest by our providers.
• Not end-to-end encrypted: messages are encrypted on the way and in storage, but not end to end. That is what lets your full history appear on every device you sign in on, lets you search it, and lets us act on reports of abuse. We say so plainly so you can decide what to share.

Who can see what

• Only the people in a conversation can read it. Someone who joins later never sees messages from before they joined.
• Projects and your company's internal space work the same way: only the people in a channel read it, and its @ admins decide who joins. A channel where people from other companies read along is marked "External".
• Files are private. They are only handed out to the conversation's participants, through download links that expire after a few minutes.
• There is no public directory. People can only reach you by knowing your email address, through conversations you share, or through your chat link if you switch one on. Your settings decide who may start a conversation with you, and you can block anyone.
• Your company's owners (on the Organization plan) manage who belongs to the company in CorrespondR, and see the copies of its OneDrive and SharePoint files sent to other companies. They cannot read your conversations.
• CorrespondR staff do not read your conversations. Access to the production systems is limited to CorrespondR's administrators. We only see message content when someone reports a message to us (the report includes it), or when the law requires it.

Signing in

• Sign-in is handled by Clerk. We never see or store your password. Passwords must be long and are checked against known data breaches.
• You can sign in with Google, Microsoft or Apple instead of a password.
• Deleting your account is confirmed with a one-time code sent to your email address.

Connected calendars, OneDrive and SharePoint

• Connecting is optional, and you can disconnect at any time (Settings → Meetings, Settings → Files), which deletes our access at once.
• The access Microsoft or Google gives us is stored encrypted with a key of our own, on top of the database's own encryption.
• We only ask for what each feature needs: to see when you are free and book meetings in your calendar; to list and read the files you pick to share; and, only if you choose a folder for a file request, to save the files sent for it there. We never change your other files, or who can open a file.
• A shared file stays in your company's Microsoft 365, and Microsoft decides who can open it. A copy is only sent when you choose one, and an organisation can switch off copies of its files to other companies.
• At companies where IT approves apps, IT approves CorrespondR once for everyone, and can withdraw that at any time.

How the apps are protected

• The website tells browsers never to show it inside another website (so nobody can trick a click on it), never to treat a file as something other than what it is, and never to ask for the camera, microphone or location.
• The desktop app shows only CorrespondR's own pages, in a locked-down window; every other link opens in your browser.
• The phone apps keep your sign-in in the phone's encrypted storage.

How we check security

• Before every release, CorrespondR runs over a thousand automated checks, among them who may see and do what.
• The software CorrespondR is built on is checked for known security problems, and updated promptly when one is found.
• We review the code for security, above all the rules for who can see what.

Protection against abuse

• Rate limits and a web application firewall protect the service from overload and automated attacks.
• Fair-use limits on new conversations and invitations stop spam, and new accounts start with lower limits.
• Anyone can block a person or report a message; reports are reviewed by our team.

Backups and reliability

• The database is backed up continuously by our provider, with point-in-time restore.
• Every change to CorrespondR is tested before release, and a release can be rolled back in moments.

Monitoring and incidents

• Errors are reported to us automatically (Sentry), without personal data such as IP addresses, and set up to leave out message content.
• If a security incident affects personal data, we act at once to contain it, notify the Norwegian Data Protection Authority (Datatilsynet) within 72 hours where the GDPR requires it, and tell affected customers without undue delay.

You are in control

• Download my data (Settings → Profile) gives you everything we hold about you, as one file.
• Download a conversation as a text file from the conversation itself.
• Delete your account at any time (Settings → Profile, or app.correspondr.com/delete-account).
• Message previews can be turned off, so notifications on a locked screen show no names or content.

Service providers (subprocessors)

These companies process data on our behalf, only to provide their part of the service:

Where a provider is outside the EEA, transfers rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses.

Data processing agreement

Businesses that use CorrespondR with their clients can ask us for a data processing agreement (DPA) under Article 28 of the GDPR. Email info@correspondr.com.

Reporting a security problem

If you think you have found a security problem in CorrespondR, please email info@correspondr.com with "Security" in the subject, and tell us how to see it. We reply to every report, and keep you posted while we fix it.

• Test only with your own accounts, and never read, change or delete other people's data.
• Do not overload the service, send spam, or try to trick our staff or our users.
• Give us a reasonable time to fix a problem before telling others.

If you follow these rules and act in good faith, we will not take legal action against you, and we will gladly thank you by name if you wish.

CorrespondR AS · Organisation number 931 147 765 · Turbinveien 40, 0195 Oslo, Norway