Privacy Policy
Effective and last updated: July 25, 2026
1. Scope and who we are
This Privacy Policy applies to the Dashrix websites, dashboard, APIs, tracking script, emails, integrations, and related services (collectively, the “Service”). “Dashrix,” “we,” “us,” and “our” refer to Just Jump Solutions, the operator of Dashrix.
For account, billing, marketing-site, invitation, and support information, Just Jump Solutions generally determines why and how the information is processed and acts as the controller or business. For analytics and integration data that a Dashrix customer directs us to process for its workspace, the customer generally acts as the controller or business and Just Jump Solutions acts as its processor or service provider. The customer is responsible for providing notices and obtaining any consent required on its own websites and services.
2. Information we collect
| Category | Examples | Primary purposes |
|---|---|---|
| Account and identity | Name, email address, Firebase user identifier, authentication provider, email-verification state, workspace roles and memberships. | Authenticate users, provide accounts, secure workspaces, support users, and enforce permissions and subscriptions. |
| Invitations and communications | Invitee email, inviter, workspace, role, invitation status and expiry, delivery status, provider message ID, and support correspondence. | Send and administer invitations, prevent abuse, troubleshoot delivery, and maintain security records. |
| Workspace and product configuration | Product names, public URLs and domains, favicons, time zones, tracking keys, mappings, integration settings, and display preferences. | Configure the Service and associate analytics, revenue, and calls with the correct workspace and product. |
| Customer-site analytics | Page URL and path, page title, referrer, UTM parameters, click text and selectors, outbound links, generated visitor/session/page-load identifiers, browser and device metadata, language, time zone, viewport, video engagement, and form metadata such as form type, provider, field categories and counts, and submission-status signals. | Provide traffic, engagement, form, video, attribution, and conversion analytics; diagnose reliability and prevent duplicate events. |
| Approximate location and network data | User agent; country, region, city, postal area, coordinates and time zone supplied by Cloudflare; IP address used in transit to generate a rotating pseudonymous visitor hash and for security. Dashrix does not store the raw IP address in its analytics event record. | Geographic analytics, security, abuse prevention, event integrity, and service operations. |
| Google account and Calendar data | Connected Google account email, encrypted OAuth refresh token, calendar identifiers and names, event identifiers, iCal UID where available, event title, limited description snippet, start/end time, status, link, organizer/attendee or conference signals where used for matching, mappings, and synchronization status. | Connect requested calendars, match booked calls to products, import and deduplicate call records, attribute calls, and maintain synchronization. |
| Stripe data | Connected account identifiers and names, encrypted restricted credentials or OAuth credentials, product and price catalog details, payment and refund amounts, currency, status, timestamps, description, and customer email when Stripe supplies it. | Import and display revenue, map Stripe prices to products, calculate summaries, and attribute payments. |
| Operational and security data | Request timestamps, authentication and OAuth state, errors, delivery results, synchronization timestamps, audit context, Cloudflare logs, and diagnostic information. | Operate, secure, debug, monitor, and improve the Service and comply with law. |
| Billing data | Plan, subscription and trial state. If paid billing is enabled, the payment processor—not Dashrix—collects full card details. | Administer trials, subscriptions, limits, invoices, and fraud prevention. |
Customer-site storage and form privacy
The Dashrix tracking script does not set browser cookies. It uses first-party localStorage for a generated visitor identifier and sessionStorage for session and referral state. Those identifiers remain until the browser or site clears the applicable storage. Dashrix does not use them to track a person across unrelated Dashrix customer domains.
Dashrix analytics is designed not to collect values typed into forms. It can collect structural metadata—such as a form’s inferred type, provider, field categories and counts, visibility, start, submission attempt, and success/failure signals. Customers must not configure selectors, names, URLs, callbacks, or other metadata to send passwords, payment-card data, health data, government identifiers, form answers, or other sensitive content to Dashrix.
3. Google user data
Dashrix accesses Google user data only after a user chooses to connect Google and grants the requested permissions. We use Google sign-in data to authenticate the user. We use Google Calendar data to list eligible calendars, import and match booked-call events, maintain synchronization, and show call analytics in the workspace selected by the user.
A workspace owner may email an external sales representative a request to contribute Google Calendar data. The representative does not create a Dashrix account or receive workspace access. Before Google authorization, Dashrix shows the requesting workspace, the invited email in masked form, the read-only access requested, and the invitation expiry. If accepted, Dashrix stores the invitation email, verified Google identity email, encrypted refresh credential, consent/audit timestamps, connection status, seat assignment, and imported call data for the receiving workspace.
We do not use Google user data for advertising, sell it, permit humans to read it except with the user’s affirmative support request or when necessary for security or legal compliance, or use it to train generalized artificial-intelligence or machine-learning models. We disclose Google user data only to service providers acting on our behalf, when directed by the user or workspace, as part of a lawful business transfer subject to this policy, or when legally required.
Dashrix’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
You can disconnect Google Calendar inside Dashrix and revoke Dashrix access from your Google Account connections. Disconnecting removes stored Dashrix connection credentials. Mapping configuration and previously imported call records may remain so a workspace can preserve attribution or reconnect without rebuilding its setup, until the workspace owner submits an authenticated deletion request, subject to legal and backup requirements.
4. How we use information
- Provide, personalize, maintain, and secure the Service.
- Authenticate users and administer trials, subscriptions, invitations, workspaces, and permissions.
- Process customer instructions for analytics, Google Calendar, Stripe, and supported integrations.
- Send transactional messages, respond to support requests, and provide service notices.
- Detect abuse, prevent fraud, debug failures, enforce terms, and protect users and the Service.
- Measure and improve Service performance using data appropriate for that purpose.
- Comply with law, valid legal process, and enforceable governmental requests.
Where the GDPR or similar law applies, our legal bases may include performing a contract, taking requested pre-contract steps, complying with law, consent, and legitimate interests such as securing and improving a business analytics service. Customers determine the appropriate legal basis for personal data they direct Dashrix to process.
5. How we disclose information
We may disclose relevant information to vendors that process it for us under contract, including:
- Google Cloud and Firebase for authentication, Firestore data storage, and Google API connectivity.
- Cloudflare for hosting, content delivery, networking, security, and request metadata.
- Resend for transactional email delivery and delivery diagnostics.
- Stripe when a customer connects Stripe or when Stripe processes Dashrix subscription billing.
- Professional advisers, auditors, insurers, and authorities when reasonably necessary and legally permitted.
Workspace owners and authorized members can view information according to their roles. An external calendar contributor’s data is provided to the workspace they intentionally connect to, without giving the contributor access to the Dashrix dashboard.
We do not sell personal information. We do not share personal information for cross-context behavioral advertising, and we have not done so in the preceding 12 months. We do not knowingly use sensitive personal information to infer characteristics about a person.
6. Retention and deletion
We retain information only for as long as reasonably necessary for the purposes described here, to follow customer instructions, maintain security and auditability, resolve disputes, and comply with law. Retention currently follows these criteria:
- Account, workspace, product, analytics, imported revenue, and imported call data generally remain while the applicable account is active or until an authenticated deletion request is completed. Disconnecting an integration deletes the connection credentials and associated data described by the applicable in-product control; previously imported Google Calendar call records may remain until separately deleted.
- Google and Stripe credentials are retained while the integration remains connected and are deleted when the connection is disconnected. Credentials are encrypted before storage.
- Workspace invitation links expire after seven days. Acceptance links are stored as hashes; invitation and delivery status may be retained for security, audit, and support.
- Operational logs, caches, backups, and vendor records follow security, recovery, and provider lifecycle requirements and may persist for a limited period after deletion from active systems.
- We may retain information when required by law or necessary to establish, exercise, or defend legal claims.
Where we process information for a Dashrix customer, deletion requests may need to be directed to that customer. We will assist the customer as required by applicable law and our agreement.
7. Security
We use safeguards designed for the nature of the information, including TLS in transit, access controls, authenticated workspace permissions, hashed invitation tokens, encrypted Google and Stripe credentials, secret management, and service-provider security controls. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
8. International processing
Dashrix and its providers may process information in the United States and other countries where they operate. Those countries may have different data-protection laws. Where required, we and our customers are responsible for using an approved transfer mechanism and implementing appropriate safeguards.
9. Your privacy rights
Depending on where you live and subject to applicable exceptions, you may have the right to request access, correction, deletion, restriction, portability, or objection; withdraw consent; opt out of sale or targeted-advertising sharing; and appeal or complain to a regulator. We will not discriminate against you for exercising an applicable privacy right.
Submit a request to [email protected]. Describe the account, workspace, website, or integration involved. We may verify your identity and authority before fulfilling a request. If Dashrix processes the information solely for a customer, we may refer the request to that customer.
Because we do not sell personal information or share it for cross-context behavioral advertising, Dashrix does not currently provide a “Do Not Sell or Share” opt-out. We will honor legally required browser-based preference signals if our practices change so that such a choice becomes applicable.
10. Children
Dashrix is a business service and is not directed to children under 13. We do not knowingly collect personal information from children under 13. Customers must not use Dashrix to intentionally collect children’s personal information without first establishing all notices, consents, and safeguards required by law.
11. Changes to this policy
We may update this policy as the Service, vendors, or legal requirements change. We will post the revised policy with a new effective date. If a change materially expands how we use personal information—including Google user data—we will provide additional notice and obtain consent where required before applying the new use.
12. Contact
Just Jump Solutions — Dashrix
Email: [email protected]
Website: https://dashrix.io/