Cookie Policy
Last updated:
UniPulse uses a single cookie and some browser storage to keep you signed in and remember your settings. We do not use advertising cookies, analytics cookies or tracking pixels on unipulse.tech or app.unipulse.tech.
2. Browser storage
The UniPulse app stores the following in your browser's local storage. It never leaves your device except where noted.
| Key | Purpose |
|---|---|
| omnisocial-auth | Your sign-in session: your basic profile and the access and refresh tokens the app sends to our servers. |
| omnisocial-ui | Interface preferences: theme, language, layout. |
| omnisocial-workspace | Which workspace you last used. |
| Other UniPulse keys (recently opened items — which can include the names of records you opened — pinned items, inbox draft notes, notification state) | Remember interface state between visits. |
Signing out removes your session; some interface data (such as recently opened items and draft notes) stays in the browser until you clear its storage, which you can do at any time in your browser settings.
3. Third-party resources
| Provider | When | What it means for you |
|---|---|---|
| Google Fonts | Every page | Your browser downloads our fonts from Google, which receives your IP address and browser details. |
| Google Sign-In, Microsoft Sign-In | Only when you choose to sign in with them | The provider handles the sign-in under its own privacy policy and may set its own cookies. |
| Stripe | Only on checkout pages | Stripe loads its payment form and may set cookies for fraud prevention under its own privacy policy. |
| Meta, TikTok, Google (authorization pages) | Only when you connect an account | You are sent to the platform's own authorization page, which uses its own cookies. |
4. UniPulse-hosted storefronts
Stores that UniPulse customers run on UniPulse storefronts (store addresses under unipulse.tech, or the store's own domain) store an anonymous visitor identifier (sf_fp) and the shopping cart (sf-cart) in local storage, and send page views — page path, referrer, browser user agent and campaign (UTM) parameters — to the store owner's analytics in UniPulse. The store owner is responsible for that store's cookie notice.
5. The UniPulse tracking SDK on customers' websites
UniPulse customers can install our tracking SDK on their own websites to measure which social campaigns lead to sales and to send conversion events to their own Meta, Google or TikTok advertising accounts. It is not installed on unipulse.tech. On a customer's site it may set:
| Name | Purpose | Duration |
|---|---|---|
| _fbp | Meta browser identifier used for the customer's conversion measurement | 395 days |
| _fbc | Meta click identifier from an ad click (fbclid) | 90 days |
| _up_consent | Remembers the visitor's tracking consent choice | 365 days |
Email addresses, phone numbers and names sent through the SDK are hashed (SHA-256) in the visitor's browser before they leave it. The website owner decides whether to require consent before tracking and is responsible for its own cookie notice and consent. Visitors with questions should contact that website.
6. Changes and contact
If we ever add analytics or advertising cookies to our own sites, we will update this page and ask for your consent first where the law requires it. Questions: privacy@unipulse.tech.