Your marketplace data, handled with restraint.
Connecting your seller accounts is a decision you should be able to make with clear eyes. Here is exactly what DPAILE stores, what access it asks for, and where our posture stands - no overclaiming.
Data handling
What we store, how long, and who can reach it.
API scope
Read and write permissions, explained plainly.
Encryption
Protected in transit and at rest.
Compliance
Current status only, no aspirational badges.
Marketplace account and listing data handling
DPAILE stores the data it needs to optimize and monitor your listings, and no more. That primarily means listing content - titles, keywords, images, attributes - along with the performance and account-health signals a marketplace exposes to you as a seller.
- What is stored: listing content, product attributes, pricing and inventory figures, buy-box and ranking signals, and seller performance metrics.
- What is not sought: we do not need or collect end-buyer payment details, and we avoid pulling personal data beyond what a listing or order record inherently contains.
- Why it is stored: optimization and monitoring require a baseline to compare against, so changes and losses can be detected over time.
Marketplace API connection scope
When you connect a marketplace, DPAILE requests the narrowest set of permissions that lets it do its job. Where a marketplace separates read and write access, we ask for each only where a feature genuinely needs it.
- Read access is used to sync listings, read performance metrics, and monitor buy-box and ranking signals.
- Write access is used only to apply the optimizations you approve - updated titles, keywords, and listing fields.
- Revocable at any time: a connection can be disconnected from your marketplace's own settings, which immediately ends DPAILE's access.
Encryption in transit and at rest
Data moving between your browser, DPAILE, and the marketplaces is encrypted in transit using current transport-layer standards. Stored data is encrypted at rest. Credentials and connection tokens are handled as secrets and are never exposed in the product interface.
Compliance posture, stated honestly
We describe only where we actually stand. DPAILE follows the security practices outlined on this page today. We do not claim certifications we have not completed, and this page is the reference for our current status.
As our compliance program matures, this page is where any formal attestations will be listed - accurately, and only once they are real.
Access and retention
Access to stored data is limited to what is required to operate and support the product. Retention is tied to the life of your account: while you are active, we keep the baseline needed for monitoring and comparison; when you disconnect a marketplace or close your account, the associated data is removed within a defined window.
If you have a specific data question - what is held, or a removal request - reach us through the contact page and we will answer directly.
Least access, clear retention, no overclaiming.
Start a free trial and connect a single marketplace first. You control the scope, and you can disconnect at any time from the marketplace's own settings.