Privacy Policy

Effective date: November 1, 2026 · Versão em português

This Privacy Policy describes how Slink Digital ("we", "us", "our") collects, uses, stores and protects information in connection with SlinkDash, our e-commerce profit analytics dashboard, available at app.slinkdash.com and described at slinkdash.com (together, the "Service").

SlinkDash helps store operators understand the real profitability of their e-commerce stores by consolidating sales, advertising spend, product costs and fees into a single dashboard. It is a business tool: each account works inside a workspace holding that account holder's own stores and data. A workspace owner can invite other people, and anyone who joins by invitation sees that workspace's data according to the role they were given.

1. Information we collect

Account information

• Email address: used to authenticate you, identify your account and send the messages described below. Authentication is handled by Clerk, and we do not store passwords.
• Name: provided at sign-up and used to identify you in the dashboard and in the messages we send.
• Language preference: stored so the dashboard and our emails reach you in the language you picked.

Data from services you connect

When you choose to connect a third-party service, SlinkDash accesses only the data needed to compute and display your profitability:

• Shopify: orders, order totals, line items, products and payout/fee information for the stores you connect.
• Meta Ads: ad account names and identifiers, campaign spend and performance metrics.
• Google Ads: ad account (customer) names and identifiers, campaign cost and performance metrics. See Section 3 for the full Google-specific disclosure.
• Supplier / fulfillment platforms: product cost data for orders placed in your connected stores.

Notifications

• If you turn on push notifications, we store your device subscription (the technical address your browser provides and the keys used to encrypt the message), which is required to deliver them. Turning notifications off removes that subscription.

Technical information

• Basic logs (such as request timestamps and status) needed to operate, secure and debug the Service. We do not use analytics trackers or advertising cookies. The only cookies used are those strictly necessary for authentication.

2. How we use information

We use the information described above exclusively to:

• Display your sales, costs, advertising spend and computed profit back to you in the dashboard;
• Send you notifications you have enabled (for example, sale alerts and daily profit summaries), along with necessary emails about your account, such as your welcome message and the alert that an integration needs reconnecting;
• Operate, secure and improve the Service.

We do not sell your data, rent it, share it with third parties for marketing, use it to advertise to you or anyone else, or use it to train machine-learning or artificial-intelligence models.

3. Google user data

If you connect a Google Ads account, SlinkDash uses Google's official OAuth 2.0 sign-in and requests access under the Google Ads API scope (https://www.googleapis.com/auth/adwords).

Account health asks for Gmail read access (https://www.googleapis.com/auth/gmail.readonly) to alert you about Google Ads suspensions, payments, verifications and interruptions. It uses the Google Ads scope to list the accounts you choose to monitor and to check, read-only, each account's status, the hours with impressions in the last 7 days and advertiser identity verification. Google's permission allows reading the entire mailbox; SlinkDash restricts processing to identified Google Ads notices. Gmail is not required to use the dashboard: when you connect a store's spend, it is requested only if you turn on Account health. We use the Gmail address to associate the authorization with the correct account.

What we access

• The list of Google Ads accounts you can access (names and customer IDs), so you can choose which account to link;
• Campaign-level cost and performance metrics (such as daily spend) for the account you link.
• If you connect Account health: sender, authentication headers, subject and snippet of the Google messages that mention Google Ads or Google's payments, to identify relevant notices. A message body is requested only when the subject indicates a notice.
• If you connect Account health: account status, time zone, the latest hour with impressions in the last 7 days and the advertiser identity verification status of each monitored account.

How we use it

• Your advertising cost data is used solely to display your ad spend in your dashboard and to compute your profit figures. Access is read-only: SlinkDash never creates, edits or deletes campaigns, budgets or any other Google Ads resource.
• Monitoring data is used to record incidents and send the alerts you enable. From Gmail notices we store the subject, date, message identifier and incident type; we do not store message bodies. From the Google Ads check we store the latest answer for each monitored account; we do not store campaigns, amounts or impression counts. Incidents are accessible to owners of your workspace.

How we store and protect it

• OAuth tokens and synced cost data are stored in our database hosted on Cloudflare's infrastructure, encrypted in transit (TLS) and at rest;
• Data is processed by the Cloudflare infrastructure described in Section 4 and, when you enable notifications, your devices' push services. Google user data is not sold, used for advertising, transferred to third parties for independent purposes, or used to train AI/ML models;
• No humans read this data except with your explicit consent (for example, a support request), or where necessary for security, to comply with applicable law, or as part of aggregated, anonymized internal operations.

How to revoke access

• Disconnect the integration inside SlinkDash at any time; and/or
• In Account health, Disconnect monitoring stops new reads and deletes that connection's credentials, monitored accounts and incidents from the active database. It does not revoke Google's authorization for your stores' other spend integrations. If the same authorization also feeds a store's spend, it stays valid at Google for that purpose, and SlinkDash does not read Gmail with it. To revoke the app's access at Google, use the link below; doing so may also interrupt those other integrations;
• Revoke SlinkDash's access from your Google Account at myaccount.google.com/permissions;
• You may also email us (below) to request deletion of all stored Google user data. We honor such requests within 30 days.

4. Data sharing

We do not sell your data or share it with third parties for marketing. We rely on a small set of infrastructure providers, which process data only to run the Service on our behalf:

• Cloudflare: hosting, database, file storage and queue processing. This is where the Service runs and where your data is stored;
• Clerk: sign-up and authentication. Clerk verifies your email address and maintains your signed-in session;
• Resend: delivery of your account emails, such as the welcome message and the reconnect alert. It receives the destination address and the message content.

Beyond these, we may disclose information if required by law, regulation or valid legal process, and then only to the extent required.

5. Data retention and deletion

• Connected-service data is retained while the integration remains connected, so the dashboard can show historical profitability;
• When you disconnect an integration, we stop syncing new data from it, and stored credentials for it are deleted;
• You can delete your account from the dashboard itself, under Settings and then Danger Zone. The account is deactivated for 30 days, and once that period ends the data is permanently erased from our systems. Within that window you can sign in and restore the account. If you are the workspace owner, the deletion covers the whole workspace, including the other members' data;
• If you prefer, you can also request deletion by emailing contact@slinkdash.com. We complete those requests within 30 days. The Data Deletion page covers both routes in detail.

6. Security

• All traffic to and from the Service is encrypted with TLS (HTTPS);
• Data at rest is stored on Cloudflare infrastructure with encryption at rest;
• API credentials and OAuth tokens are stored as encrypted secrets, never in client-side code;
• Reaching the dashboard requires an authenticated session, and each account can only reach the data of the workspace it belongs to.

7. Children's privacy

The Service is a business tool and is not directed to children under 18. We do not knowingly collect information from children.

8. Changes to this policy

We may update this Privacy Policy from time to time. The current version will always be available at slinkdash.com/en/privacy, with its effective date shown at the top. Material changes will be communicated to active users.

9. Contact

For any questions about this policy or your data, contact:
Slink Digital
Email: contact@slinkdash.com