Privacy policy

1. Information we handle

• Campaign and product content: ASINs, product titles, displayed prices, estimated earnings per click (EPC), whether EPC is an estimated maximum, campaign budget availability, the selected Amazon store ID, and capture timestamps.
• Account authorization: a short-lived, signed capture token containing Tempo user, session, and workspace identifiers, the permitted store, and an expiration time. The extension receives this limited token after Tempo verifies account access. It does not receive your Tempo password, your full Tempo login tokens, or Amazon authentication cookies.
• Supported-page activity: the extension checks the current URL, campaign tab, and sort selection on supported pages. It responds to scrolling and page changes to identify visible campaign cards. It maintains capture counts, processing status, pause preferences, and error information. This is limited to the extension workflow; it does not collect a general browsing-history list, keystroke log, or mouse-movement log.
• Technical information: hosting providers may process request metadata, including IP addresses and browser or network information, to deliver requests, maintain security, and diagnose failures. The extension does not request GPS or precise device location.

The extension does not read personal messages, payment-card numbers, bank-account details, or personal medical records. Product listings may describe health-related products; those listings are campaign content, not a user's medical history.

2. How information is used

We use information to verify team access, capture supported campaign cards, avoid duplicate processing, retrieve product details, display products and campaign metrics in Discover, report progress, recover interrupted work, and protect the service from misuse. Capture is enabled for accepted Sponsored Products for Creators campaigns sorted by Estimated EPC. Users can pause capture through the floating panel.

We do not sell personal information or use a user's extension activity to serve personalized, retargeted, or interest-based advertising. Use and transfer of information received through the extension are limited to its stated purpose, security, legal obligations, and the applicable Chrome Web Store User Data Policy, including its Limited Use requirements.

3. Sharing and service providers

Uploaded products and campaign information are visible to authorized teammates in the configured shared Tempo feed. They are not a private collection belonging only to the person who captured them. Technical operators may access information when necessary for support, security, and service maintenance.

The extension workflow uses these providers:

• Cloudflare: receives authorized uploads and provides durable queueing, duplicate detection, and processing status.
• Supabase: supports Tempo account verification, workspace membership, and product campaign enrichment.
• EasyParser: receives product ASINs when product-detail enrichment is needed. It does not receive the extension's Tempo authorization token.
• Render: hosts the Tempo website and its server endpoints.
• Oracle-hosted services and ClickHouse: run enrichment processing and store the shared product feed.
• Amazon: provides the campaign pages you choose to visit and product resources used by the workflow. Your Amazon account remains subject to Amazon's own privacy practices.

Providers process information needed for their roles and may operate infrastructure in countries other than your own. Information may also be disclosed when required by law or necessary to investigate abuse or protect the service.

4. Storage and retention

• Discover products: Amazon captures remain visible for 30 days from the first capture in their active window. Recapturing a product updates its observations without extending that window.
• Failed jobs: failed enrichment jobs use the same 30-day capture window. They may be resolved earlier; they are not treated as successfully enriched products.
• Raw enrichment responses: database copies have a separate 14-day retention policy.
• Local pending uploads: captures are retained in the browser until the server acknowledges them. Expired captures are discarded when the queue is processed.
• Local duplicate-detection records: compact product fingerprints generally expire 30 days after their recorded observation and are removed during periodic cleanup. These are not full product responses or image files.
• Authorization: capture grants expire after five minutes and can renew while an authorized Tempo dashboard tab is open. Signing out stops local capture and requests session revocation.

Expired products leave the active feed before all underlying storage is physically removed. Routine queue records are eligible for cleanup after an additional 14 days, followed by scheduled cleanup. Database cleanup runs in the background. Unresolved paid-request recovery records, saved response files, security records, and provider logs may remain longer for reconciliation, troubleshooting, or legal obligations. The 30-day feed window is not a promise that every operational copy is erased at that exact moment.

5. Your controls and privacy requests

Use Pause capture to stop new captures and pending local uploads. Hiding the panel does not pause capture. Processing already accepted by the server may continue. Sign out of Tempo to end authorization, or uninstall the extension to stop its browser operation and remove its local extension storage. Neither action automatically deletes products already contributed to the shared feed.

For access, correction, deletion, or other privacy requests, contact your Tempo workspace administrator. Identify the relevant workspace and, where applicable, product ASINs. Do not send passwords, cookies, or authorization tokens. Requests may require verification, and shared records may also relate to other team members or necessary security and recovery records.

6. Security and policy updates

Production requests use HTTPS, and capture endpoints require limited authorization with server-side access checks. Local development may use HTTP on localhost. Authentication material stored in browser extension storage should be protected by securing your browser profile and device. No method of storage or transmission is entirely risk-free.

We will update this page when the extension's information practices change and revise the date above. Material changes that require additional notice or consent will be presented as applicable.