Data Deletion & Account Disconnection

This page explains how Appath customers and authorized users can:

• Disconnect a sales channel or other integration.
• Revoke Appath's access to a connected account.
• Disconnect a supplier relationship.
• Request deletion of eligible data.
• Close an Appath account.
• Understand what information may be retained and why.

Disconnecting an integration, requesting data deletion, and closing an Appath account are separate actions.

Disconnecting an integration

Disconnecting stops Appath from making future authorized requests to the applicable sales channel, supplier, or service after the disconnection or revocation takes effect.

Disconnecting an integration does not automatically close the Appath account or immediately delete all information previously processed through that connection.

Requesting data deletion

A deletion request asks Appath to remove eligible information associated with an account, organization, integration, or specific data set.

Some information may be retained when required for legal, tax, accounting, security, fraud-prevention, dispute-resolution, or regulatory purposes.

Closing an Appath account

Closing an account ends access to the applicable Appath organization and Services. Account closure may initiate deletion of eligible information, but certain records may remain subject to required retention periods.

Customers may disconnect an authorized sales channel through Appath or through the applicable sales channel.

Disconnecting through Appath

When connection controls are available for the applicable integration:

1. Sign in to your Appath account.
2. Open the applicable sales-channel connection.
3. Select the option to disconnect or remove the connection.
4. Review the effects of disconnection.
5. Confirm the request.

After disconnection, Appath will stop initiating new authorized activity for that connection once the disconnection takes effect.

In-progress synchronization, listing, inventory, order, fulfillment, accounting, or reconciliation jobs may need to complete or be safely stopped before the connection is fully disabled.

If you cannot access the applicable connection controls, submit a request through our contact form and select Account disconnection or deletion as the request type.

Revoking access through the sales channel

Customers may also revoke Appath's access directly through the connected sales channel. The available steps and terminology are controlled by that sales channel and may change.

Revoking access at the sales channel generally prevents Appath from making additional authorized requests, but it does not automatically delete information already processed or stored by Appath.

Only the authorized Amazon selling partner can revoke Appath's Amazon OAuth authorization.

To revoke Appath's authorization in Amazon Seller Central:

1. Sign in to Amazon Seller Central.
2. Open Apps and Services.
3. Select Manage Your Apps.
4. Locate Appath.
5. Select Disable authorization.
6. Confirm the action.

After Amazon authorization is revoked:

• Appath can no longer make new SP-API requests for that authorization.
• Amazon synchronization and automation for the connection will stop.
• Associated credentials will be invalidated, revoked, or securely deleted from active use.
• Previously processed information remains subject to Appath's deletion and retention rules.
• The Amazon application may remain visible in Amazon even though its authorization is disabled.

Customers may also disconnect the Amazon connection through Appath when that control is available. For the strongest assurance that Amazon authorization has ended, the selling partner should also disable authorization through Amazon Seller Central.

For Walmart Marketplace, Shopify, eBay, and other supported integrations, customers may:

• Disconnect the applicable connection through Appath.
• Revoke Appath's access through the sales channel's account or application settings.
• Submit a disconnection request through Appath's contact form.

Because each service controls its own authorization system, the available settings and exact steps may differ.

After revocation, Appath will stop making new authorized requests once the revocation takes effect. Data previously processed through Appath remains subject to the applicable retention and deletion requirements described on this page and in the Privacy Policy.

A retailer or supplier may request that an Appath supplier relationship be disconnected.

A supplier disconnection may:

• Stop future catalog or inventory synchronization.
• Stop new order routing to that supplier.
• Change affected inventory availability.
• Trigger listing or inventory exceptions.
• Require completion, cancellation, or reconciliation of active orders.
• Preserve historical accounting, order, and audit records where required.

Disconnecting a supplier relationship does not automatically delete product, order, accounting, or fulfillment records that must be retained for business, legal, tax, security, or dispute-resolution purposes.

Requests may be submitted through our contact form. Select Account disconnection or deletion and identify the supplier or retailer relationship involved.

To request deletion of eligible information, submit the request through our contact form and select Account disconnection or deletion as the request type.

Include enough information for Appath to identify and verify the request, such as:

• Your name.
• Business or organization name.
• The email address associated with the Appath account.
• The applicable Appath organization or account.
• The connected sales channel or supplier, if relevant.
• Whether the request concerns an integration, selected records, or the entire account.
• A brief description of the requested action.

Appath may verify the identity and authority of the requester before disconnecting an integration, closing an account, exporting data, or deleting information.

Verification may include:

• Confirming access to the email address associated with the account.
• Requiring the requester to sign in.
• Confirming the requester's organization and role.
• Requesting approval from an account owner or administrator.
• Confirming ownership of the connected sales-channel account.
• Requesting additional information reasonably necessary to prevent unauthorized deletion.

Appath may decline, delay, or narrow a request when the requester cannot be verified or does not have authority to act for the applicable account or organization.

Depending on the request and applicable obligations, eligible information may include:

• Appath account profile information.
• User preferences.
• Integration credentials.
• Imported catalog information.
• Channel-listing records.
• Inventory records.
• Supplier connection information.
• Order-recipient information.
• AI Product Optimizer source files.
• Generated listing content.
• AI Assistant conversation data.
• Uploaded files.
• Support communications.
• Other Customer Data associated with the request.

Deletion may involve permanent deletion, irreversible anonymization, or removal of the link between the information and the applicable account or individual.

Appath processes Amazon Information only for features authorized by the applicable Amazon seller.

Amazon customer PII

Amazon customer PII may include:

• Recipient name.
• Shipping address.
• Telephone number.
• Buyer email address.
• Delivery instructions containing personal information.

Unless longer retention is legally required for a specific permitted purpose, Appath deletes Amazon customer PII no later than 30 days after order delivery.

Where reliable delivery information is unavailable, Appath may use an earlier or shipment-based deletion schedule.

Amazon customer PII is not retained for advertising, independent marketing, customer profiling, data resale, shared AI-model training, or cross-seller competitive intelligence.

Amazon non-PII

Amazon non-PII is retained for no longer than 18 months unless longer retention is required by applicable law or expressly permitted by Amazon.

Amazon deletion notices

Information subject to a valid Amazon deletion notice will be securely deleted within the applicable required period unless retention is legally required for tax, regulatory, or other permitted legal purposes.

Amazon authorization credentials

When an Amazon connection is disconnected or authorization is revoked, Appath invalidates, revokes, or securely deletes the applicable credentials from active use in accordance with operational and legal requirements.

Appath may retain limited information when reasonably necessary to:

• Comply with tax, accounting, invoicing, or financial-reporting obligations.
• Comply with a legal, regulatory, or court requirement.
• Establish, exercise, or defend legal claims.
• Resolve disputes.
• Enforce agreements.
• Detect, investigate, or prevent fraud and abuse.
• Investigate security incidents.
• Maintain required audit and security logs.
• Document consent, authorization, account actions, or deletion requests.
• Complete active orders, returns, chargebacks, or financial reconciliation.
• Protect Appath, its customers, suppliers, and other parties.

When information must be retained:

• Retention is limited to the required information.
• Access is restricted.
• The information remains protected.
• The information is not used for unrelated purposes.
• It is deleted when the applicable retention obligation ends.

Security and audit records may be retained after account disconnection or deletion when required to:

• Investigate unauthorized access.
• Protect system integrity.
• Demonstrate compliance.
• Detect fraud or abuse.
• Maintain operational accountability.
• Meet legal or contractual requirements.

Appath excludes Amazon customer PII from ordinary logs unless inclusion is specifically required by law.

Security and audit records relating to Amazon Information are retained for at least 12 months where required.

Deleted information may remain temporarily in encrypted backups until those backups expire under Appath's documented backup schedule.

Backups are:

• Encrypted.
• Access-restricted.
• Maintained for security and disaster recovery.
• Not used for ordinary business activity after a valid deletion request.
• Removed according to the applicable backup-retention schedule.

If a backup must be restored for disaster recovery, Appath will reapply applicable deletion records or otherwise prevent previously deleted information from returning to ordinary active use.

Appath processes verified requests within the time required by applicable law, contract, sales-channel requirements, and the nature of the request.

Timing may depend on:

• Identity and authority verification.
• The scope and complexity of the request.
• Active orders or unresolved transactions.
• Legal, tax, accounting, or security requirements.
• The systems and integrations involved.
• Backup-expiration schedules.

Appath may contact the requester through the information provided in the contact form when clarification or verification is required.

Disconnecting or deleting information may affect Appath functionality, including:

• Listing management.
• Catalog synchronization.
• Inventory updates.
• Order retrieval.
• Supplier order routing.
• Fulfillment and tracking.
• Pricing workflows.
• FBA-related workflows.
• Financial reconciliation.
• Order accounting.
• AI-assisted recommendations.
• Historical reporting.
• Exception monitoring.

Appath is not responsible for changes that remain within a sales channel, supplier system, carrier system, or other independent third-party service after Appath access is revoked.

Customers should export any information they are legally permitted and operationally required to retain before requesting deletion or closing an account.

An authorized account owner may request closure of an Appath account through our contact form. Select Account disconnection or deletion and specify that the request concerns account closure.

Before closing an account, Appath may require:

• Identity and ownership verification.
• Resolution of outstanding balances.
• Completion or resolution of active orders.
• Disconnection of integrations.
• Export of requested data.
• Confirmation that the requester understands the effects of closure.

Following closure:

• User access will be disabled.
• Connected integrations will be disconnected or scheduled for disconnection.
• Eligible information will be deleted or anonymized.
• Required records will be retained only for applicable legal, financial, security, or contractual purposes.
• Encrypted backup copies will expire under Appath's backup schedule.

An individual whose personal information is processed through an Appath customer should generally submit the request to that customer, because the customer controls its buyer, employee, supplier, and sales-channel relationships.

Appath will assist customers with verified requests as required by applicable law and contract.

Individuals may also submit a request through our contact form. Appath may direct the request to the applicable customer or request information needed to identify the relevant account and verify the request.

Questions, disconnection requests, deletion requests, account-closure requests, and privacy inquiries may be submitted through our contact form. Choose the request type that most closely matches your inquiry:

• Privacy or data request.
• Account disconnection or deletion.
• Security concern.
• Support.
• General inquiry.

Appath may request information necessary to verify the requester's identity, authority, account, or organization before processing the request.