How we protect your access

Connecting Meta, Google or your CRM to Relator means giving it authorized access to your accounts. This article explains how that access is requested, stored and used, and how each client's data is kept separate.

You never give us your password

Connections use each platform's official login. You sign in on the Meta, Google, HubSpot or RD Station screen, see what is being requested and authorize it. The platform gives Relator an access key, not your password. You can revoke that key at any time on the platform itself.

How access is stored

• Encrypted before it is saved: the access key is encrypted with AES-256-GCM. If anyone changes a single byte, reading it fails.
• Kept out of the address bar: the key goes straight from the platform to Relator's server; it does not appear in links or in the interface.
• Signed, time-limited authorization: the authorization request Relator sends is signed and valid for 30 minutes. A forged or late response is rejected, and the same authorization code is not accepted twice.
• Protected traffic: all communication uses TLS.
• Controlled internal access: access to production systems requires single sign-on with two-factor authentication, and access to sensitive data is audited.

Each client's data is kept separate

Every query is filtered by organization and by client, including questions asked to RelatorAI. In practice:

• An agency never sees another agency's data.
• Inside the agency, each client has its own space, with its own connections, dashboards and reports.
• A client invited to the portal only sees what is theirs (see Client portal).

What you can do

1. 1
   Step 1

   Give each person the right role

   In an agency, Owner and Admin manage connections, members and billing; Member works on clients. Review roles in Account › Members (see Roles and permissions).

2. 2
   Step 2

   Remove people who left the team

   When someone leaves, remove them in Members and cancel invites that will not be used.

3. 3
   Step 3

   Disconnect what you no longer use

   In Sources, use Disconnect on accounts that no longer need to sync. Sync stops right away.

   Illustrative screen

   Korra/Connections

   Ask RelatorAIPT

   IntegrationsYour connected sources and synchronization status.

   • 

     Meta AdsLast sync 12 min ago

     ActiveDisconnect

     1
   • 

     HubSpotLast sync 1 h ago

     ActiveDisconnect

   1. 1Disconnect stops syncing that account.

4. 4
   Step 4

   Turn on the connection revoked alert

   In Notification preferences, keep Connection revoked on: it notifies you when credentials or permissions are no longer valid, for example after someone changes the password on the platform.

5. 5
   Step 5

   Protect your own account

   Use a strong, unique password for Relator and for your ad accounts. See Account security.