Privacy and data

This page explains what data AEO Enhancer uses, why it is needed, and how it is handled.

AEO Enhancer is designed to minimize risk by following these rules:

• Only use store data needed to generate accurate previews and execute approved tasks
• Never apply changes without approval
• Keep changes auditable and reversible

What data AEO Enhancer reads from Shopify

AEO Enhancer reads store data to create grounded previews and to execute tasks reliably.

Typical categories include:

• Store and shop metadata
  Store name, domain, locale, currency

• Catalog data
  Products, variants, collections, product types, tags

• Content surfaces
  Blogs and articles when generating blog drafts

• Metafields
  Used to store draft and approved outputs

This data is used to ensure content generation reflects real store context and does not invent details.

What data AEO Enhancer writes

AEO Enhancer writes data only when you execute an approved task.

Typical writes include:

• Draft outputs
  Draft articles or draft metafield content

• Approved outputs
  Approved metafields that your storefront can render safely

• Audit and task state
  Task status, preview versions, and timelines stored in the app database

AEO Enhancer does not need to overwrite your live theme templates or live product fields to work. Approved outputs can be rendered through theme blocks or approved metafields.

How external services are used

Some features may rely on external services to generate content or gather competitive intelligence.

Examples can include:

• Content generation for Optimize Result
• Search and ranking retests for query targets
• Competitor discovery and evidence gathering

When external services are used, the goal is to:

• Send only the minimum necessary context
• Avoid sending sensitive business data that is not needed for the task
• Keep requests deterministic and traceable through request metadata

If a feature is blocked by plan limits or rate limits, the app will return a structured error instead of silently falling back.

What is stored in the AEO Enhancer database

The app stores:

• Tasks and their statuses
• Preview versions and associated metadata
• Audit logs and timelines
• Query targets and retest history
• AI Visibility Score snapshots
• Competitor evidence records when that feature is enabled

Snapshots and evidence are append only so you can audit history.

How long data is retained

Retention depends on your plan and operational needs, but the design intent is:

• Keep enough history for auditability and trend analysis
• Avoid storing unnecessary raw payloads
• Keep logs focused on metadata that helps debug issues without leaking content

If you have specific retention requirements, handle them through your internal policy and support channel.

Approval first and data safety

Approval first provides privacy and safety benefits:

• You see what will be written before it is written
• You control when changes are applied
• You can roll back changes if needed
• You can trace every change to a task, a preview, and a timeline event

Merchant controls

You control:

• Who in your team can approve and execute tasks through Shopify admin roles
• Whether regulated industry mode is enabled
• Your brand voice settings for content generation
• Whether you render approved outputs on the storefront

Reporting issues

If you suspect unexpected data access or behavior, capture:

• The task id
• The timeline events shown in the task modal
• The error code and message
• Steps to reproduce

Then contact support through the app.

Related pages

• Policies then Permissions
• Core concepts then Approval first
• Workflows then Preview approve execute rollback
• Troubleshooting then Common errors