DataMarketer

Marketing data security for connected accounts

Marketing data security starts with limiting what a connection can do. DataMarketer reads authorized account data, keeps campaign changes with your team and applies encryption and access controls to service data. Review the handling practices below before connecting advertising, analytics, commerce or CRM accounts.

Read-only access protects campaign control

DataMarketer uses read-only OAuth connections to read the data you authorize for analysis. It never changes campaigns, budgets, bids, tags or consent settings in connected platforms. Findings include evidence and fix steps for your team to review. You decide whether a recommendation is appropriate and apply changes in the source platform.

Encryption in transit uses TLS to protect information moving between your browser, the service and supported connections. Stored data is encrypted at rest. These controls protect account and analysis data alongside restricted access. Review the permissions shown when connecting a source and connect only accounts that are relevant to your work.

  • Authorize each source using its connection flow.
  • Keep access scoped to accounts you own or are authorized to manage.
  • Review evidence before changing a campaign or measurement setting.
  • Treat exports as customer data and control who receives them.

The data driven marketing workflow explains how connected data supports monitoring, attribution and decisions without transferring campaign control to DataMarketer.

Roles and SSO support team access

Scale includes 20 seats with roles and permissions so account owners can manage workspace access. SSO using SAML is included on the yearly Scale plan. Use these controls to align access with each person's responsibilities, especially when an agency manages client workspaces or colleagues have different reporting and administration needs.

Starter includes 1 seat and Growth includes 5. Choose access based on the data a colleague needs to do their work, and review access when responsibilities change. Avoid sharing account credentials. Yearly Scale includes security review documents for teams evaluating account controls and purchasing requirements.

For client reporting workflows, see marketing agency reporting tools. Confirm your authorization for each client connection before adding data to a workspace.

Data history follows your plan

Data history is 6 months on Starter, 24 months on Growth and 36 months on Scale. These windows describe analysis history within a subscription. Account data is retained while the account is active. Free one-time audit results are retained for 30 days. Yearly Scale includes custom data retention for specific requirements.

Canceling a subscription stops renewal while preserving access through the paid period. After that period, account and connected data are deleted unless a limited record must be retained for legal obligations, billing disputes or security needs. Deletion is also available on request. Necessary retained records are restricted to their remaining purpose and deleted when that purpose ends.

Email [email protected] to identify the account and requested deletion scope. Deleting data can remove report history and affect access. Compare history windows on the marketing analytics platform page before choosing a subscription.

Data category
Free one-time audit results
Retention
30 days
Data category
Active account data
Retention
While the account is active
Data category
Starter analysis history
Retention
6 months
Data category
Growth analysis history
Retention
24 months
Data category
Scale analysis history
Retention
36 months
Data category
Yearly Scale custom retention
Retention
Defined through the custom retention arrangement

GDPR and CCPA data handling

DataMarketer handles personal information under applicable GDPR and CCPA requirements, including access and deletion requests. Customer data remains yours. Personal information is not sold or shared for cross-context behavioral advertising. Processing for connected customer data follows your service instructions, and a data processing agreement is available on request at [email protected].

The service uses account information to provide access, connected data to produce requested analysis and service records to maintain security and billing. Customers remain responsible for their collection notices, lawful permissions and visitor consent. Auditing a consent setup does not replace a legal assessment of that setup or override visitors' choices.

Use the marketing data analysis answers to understand consent mode, source coverage and the limits of analysis. Provide only information needed for a support or rights request, and do not email passwords or connection tokens.

Service providers have defined processing roles

Subprocessors support service delivery within defined categories. Hosting providers store and process service data, email delivery providers send account communications, and payment processing providers handle subscription payments. These providers receive information needed for their role under appropriate contractual obligations. Request processing details or a data processing agreement before connecting data that requires additional review.

  • Hosting supports storage, computing and service operation.
  • Email delivery supports verification, account notices and service communications.
  • Payment processing supports charges, billing status and invoices.

Send your review questions to [email protected], including your account email and the processing concern. Yearly Scale includes security review documents. Review the information relevant to your own connected sources, exports and internal data handling before completing approval within your organization.

Report a security concern responsibly

Send suspected security issues to [email protected] with the affected page or feature, steps to reproduce and the possible impact. Use an account or site you are authorized to test. Keep testing limited to what is necessary to demonstrate the issue and avoid accessing another customer's data or disrupting the service.

Do not include live passwords, tokens or personal records in the initial message. Describe sensitive evidence without exposing it, and ask support how to provide further details if necessary. Reporting a concern does not authorize testing accounts or systems you do not control.

Questions about marketing data security

Can DataMarketer change my campaigns?

No. Connections use read-only OAuth access. DataMarketer reads permitted account data to monitor tracking, compare attribution and explain performance changes. It never changes campaigns, bids or budgets. Your team reviews each finding and applies any changes directly in the relevant platform, keeping responsibility for campaign decisions with your account owners.

Is data encrypted in transit and at rest?

Yes. DataMarketer uses TLS to encrypt data in transit and encryption at rest for stored data. These controls work alongside read-only connections and access permissions. No security control eliminates every risk, so protect your account credentials and review which colleagues and connected accounts need access to your workspace.

Which plan includes SSO and custom retention?

SSO using SAML and custom data retention are included on the yearly Scale plan, together with invoicing and security review documents. Scale also includes roles and permissions for its 20 seats. Create your account, then email [email protected] with your access requirements or the documents your review team needs.

Can I request deletion after cancellation?

Yes. Email [email protected] with your account email and the scope of the request. Subscription cancellation preserves access through the paid period. After it ends, account and connected data are deleted, subject to necessary legal retention. You can request earlier deletion and should consider how it affects access to reports and history.

How do I obtain a data processing agreement?

Request a data processing agreement by emailing [email protected] with your account email and the context of your review. Explain which connected data and workspaces are involved. The agreement addresses processing responsibilities for customer data. Yearly Scale also includes security review documents for teams completing a purchasing or access review.

Review access before connecting data

Start with a ga4 audit of a site you own or are authorized to test, then review account permissions and retention requirements before connecting sources. Use the findings to discuss measurement with your team and select the level of monitoring, access control and history your work requires.

Run the free one-time audit to inspect public tracking before connecting account data.

No card required. Read-only, your data stays yours.