Policies, Security & Data

Written By Sam from Jinnify

Last updated 19 days ago

Policies, Security & Data

Summary: What Amazon-related data Jinnify uses, how access works, how to think about AI content responsibility, and how deletion and legal documents relate to the product.

What Amazon data Jinnify accesses

When you authorize Seller Central, Jinnify receives the access needed for connected workflows. Depending on permissions and product scope, that can include:

  • Seller account and connection status

  • Listings and catalog information

  • Product and offer context needed for optimization and publish

  • Operational and analytics context used by dashboard and skills (orders, fees, and related metrics where enabled)

  • Marketplace metadata required to target the correct store

Exact fields depend on the Amazon authorization, your marketplaces, and which product features are enabled for your account.

Why those permissions matter

Jinnify uses them to:

  • Keep each workflow tied to the correct seller and marketplace

  • Show your catalog and analytics

  • Prepare listing content and submit approved changes

  • Power in-app chat and optional external agents (BYOA) with store-scoped tokens

  • Troubleshoot mismatches between intended and accepted Amazon results

Without authorization, live catalog, publish, bulk optimize, and Automate metrics cannot work fully. You can still explore the sandbox and draft some copy offline from a production connection.

How access is protected (high level)

Jinnify is built as a modern web app with:

  • Authenticated user sessions (for example Google / email via the app auth stack)

  • HTTPS

  • Backend APIs that scope data to your account and stores

  • Encrypted handling of sensitive Amazon connection material

  • Optional Personal Access Tokens for BYOA (shown once; stored hashed; revocable; optionally store-scoped and recommend-only)

Never paste raw refresh tokens, PATs, or passwords into public tickets or chats. Revoke a token immediately if it leaks (Settings → Developer access → API Tokens).

Security details evolve; the live Privacy Policy and Terms are authoritative.

Privacy Policy and Terms of Service

Use the canonical documents linked from jinnify.ai and the app footer/legal entry points for:

Review them before connecting production seller data if your organization requires legal sign-off.

API tokens and external agents

If you use Bring Your Own Agent:

  • Tokens act like passwords

  • Prefer Recommend (proposals only) and store-scoped tokens

  • You are responsible for how external runtimes store JINNIFY_API_TOKEN

  • Revoke tokens you no longer use

See Bring Your Own Agent.

Responsible use of AI-generated listing content

AI can draft titles, bullets, descriptions, and keywords. Before anything reaches Amazon:

  • Check factual accuracy (materials, dimensions, certifications)

  • Remove unsupported health, safety, environmental, or performance claims

  • Match brand voice and category rules

  • Stay within Amazon title length (about 75 characters) and content policies

  • Review variation and required attributes

You remain responsible for what is submitted to Amazon, whether you clicked publish in Create, approved Inbox items, or used an Auto-approve token.

What Jinnify does vs what Amazon controls

Jinnify

Amazon

Connects approved seller accounts

Final catalog and offer state

Generates and prepares listing content

Validation, normalization, acceptance

Submits approved updates via APIs

Propagation timing and suppressions

Shows inbox, drafts, and activity

Marketplace and category rules

Jinnify does not guarantee that every submission appears exactly as sent or on a fixed timeline.

Subscription cancel vs account or data deletion

Action

Effect

Cancel subscription

Stops future billing (usually after period end). Account and data can remain.

Remove a store

Disconnects that Amazon connection and removes its synced data from Jinnify for that store.

Delete account / broader data deletion

Separate request. Use any in-app path if offered; otherwise contact support with the account email and what you want removed.

Support may verify ownership before processing deletion.

Data retention (summary)

Operational logs and account history may be retained for security, debugging, reliability, support, and legal reasons, subject to current policy and law. For a precise answer about a data category, contact support and name the category.

Security issues

Report suspected unauthorized access, exposed credentials, account compromise, or vulnerabilities through the security path in Contact & Escalation. Avoid sending secrets in plain email unless a secure channel is arranged.

When to contact support

  • Account or connected-data deletion

  • Permission or authorization clarification after self-serve steps fail

  • Suspected unauthorized access

  • Billing identity or ownership changes

Related articles