Help center

Security and data

Your data is stored in Canada (Montreal), each workspace is isolated at the database level, ad platform access is read-only, and secrets such as CRM credentials and API keys are encrypted or stored as hashes.

Control your data

  1. Limit who sees what
    Give people the Viewer role unless they need to change budgets or links. See Workspaces, roles and team members.
  2. Stop data from arriving
    Remove the script from Google Ads or Microsoft Ads, or press Disconnect for LinkedIn or a CRM on Connect platforms. Disconnecting deletes the stored access token right away.
  3. Rotate the workspace key
    On Connect platforms, press Replace key. Scripts using the old key stop until you paste the new ones.
  4. Revoke links and keys
    Turn off the client report link in Settings, and revoke Link Console API keys in Integrations.
  5. Delete your workspace
    Contact us from your account's email address and ask to delete your workspace. We delete the workspace, its campaigns, spend history, links, tokens and members within 30 days and confirm by email.

Questions

Where is my data stored?

In Canada, in the Montreal region (AWS ca-central-1).

Who can see my workspace?

Only its members. Each workspace is isolated in the database with row-level security, and we do not sell your data.

Do you get access to my ad accounts?

No. The Google Ads and Microsoft Ads scripts run inside your own accounts and send campaign names, IDs, spend, conversions and daily budgets, plus live ad URLs for the Link Console audit. They change a daily budget only when someone in your workspace queues the change. LinkedIn is connected with read-only reporting access that you can revoke.

How are credentials and keys stored?

LinkedIn tokens are kept server side and never shown in the browser. CRM credentials are encrypted before they are stored. Link Console API keys are stored only as a one-way hash, and webhooks are signed.

What do you record when someone clicks a short link?

The time, country, referring website's domain and device type. We do not store IP addresses or identify the person, and bots and link previews are not counted.

What about cookies?

Sign-in cookies are always on. Analytics cookies load only after you press Accept on the cookie banner, and you can change your choice at any time with Cookie choices at the bottom of the main pages.

Which service providers do you use?

Supabase (database and sign-in), Netlify (hosting), Mailgun (email), Stripe (payments; card details go to Stripe and never reach us) and HubSpot (PlanConversion's customer records).

Do you support single sign-on?

Single sign-on (SAML) is on the roadmap. Contact us if you need it.

Where is the full privacy notice?

At /privacy.

Good to know

Related articles