This Cookie Policy explains what CargoScope LLC (“SalesScope”, “we”, “us”) stores in your browser when you visit salesscope.io or use the SalesScope app, and why. It also explains the tracking pixel and links in the emails our customers send through SalesScope, because people often ask about them.
1. Cookies and trackers we don’t use
We use no advertising cookies, no analytics cookies, no social media pixels, and no third-party scripts or trackers, on the website or in the app. We don’t follow you across other websites, and we don’t build profiles of you for advertising. Everything we do keep in your browser is strictly necessary for a service you asked for, so there is nothing to opt into or out of.
2. What the app keeps in your browser
The SalesScope app uses your browser’s local storage and IndexedDB rather than cookies. Only SalesScope can read them.
| What | Where | Why | How long |
|---|---|---|---|
| Sign-in session | Local storage | Keeps you signed in, so the app knows who you are on every page | Until you sign out |
| Reminders shared between tabs | Local storage | Makes a reminder ring once, not in every open tab | Until you sign out |
| Contact sheet cache | IndexedDB | Opens large sheets instantly while fresh data loads | Until you sign out |
| Preferences | Local storage | Remembers choices such as light or dark theme, desktop notifications, and where you were on a page | Until you clear your browser’s storage |
Signing out removes your session and the cached contact data from the browser. Simple preferences, such as your theme, stay until you clear your browser’s storage.
The public pages of salesscope.io set no cookies of their own. If you are already signed in to the app, the home page may read the session the app stored so that it can take you straight to the app.
3. Security cookies Cloudflare may set
Cloudflare serves our website and app and protects them from attacks. When it needs to tell people from bots, it may set strictly necessary security cookies, such as __cf_bm (used for bot detection, and expires after 30 minutes of inactivity) or cf_clearance (records that your browser passed a security check, so you aren’t asked again). Cloudflare uses them only for security, and we don’t use them at all. Cloudflare’s cookie documentation describes them in full.
4. Stripe’s payment pages
When an admin buys a plan or manages billing, the payment pages are on Stripe’s own website, not ours. Stripe sets its own cookies there, for example to prevent fraud, under Stripe’s Cookie Policy. SalesScope does not control or read them.
5. Tracking in emails sent through SalesScope
Campaign and sequence emails that our customers send through SalesScope may contain:
- A tracking pixel: a tiny invisible image. When your mail app loads images, it fetches the pixel from SalesScope, which records that the email was opened, when, and the user-agent string of your mail app.
- Wrapped links: links that pass through SalesScope and then go straight on to the address the sender wrote, recording that the link was clicked.
- An unsubscribe link, plus unsubscribe headers your mail app can use, so you can opt out in one step.
SalesScope sets no cookies with any of these. The events they record belong to the sender, who controls that data and can switch open and click tracking off. You can block tracking pixels by turning off automatic image loading in your mail app. Our Privacy Policy explains how this data is handled and how to stop a sender’s emails.
6. Your choices
You can clear or block cookies and site storage in your browser’s settings at any time. If you block storage for salesscope.io, the app can’t keep you signed in. Signing out removes your session and the cached contact data.
7. Changes to this cookie policy
If we ever add cookies or similar technologies that are not strictly necessary, such as analytics, we will update this policy first and ask for your consent where the law requires it. The effective date at the top of this page shows when the policy last changed. Questions: privacy@salesscope.io.