Fit4Retail OS privacy notice

Updated 3 November 2026.

About this service

Fit4Retail OS is a private operational integration for the operator's own eBay seller account. This notice describes its hosted callback service. Seller linking and the local order reader are under development.

Contact

For privacy questions or requests about this service, contact hamzaabualzait@gmail.com.

Information handled and purposes

The callback handles temporary OAuth authorization codes, random sign-in state identifiers and timestamps to return a sign-in response securely to an authenticated local connection tool. It also receives marketplace account-deletion notifications, which can contain eBay user identifiers, usernames and EIAS identifiers. Notifications are queued for verification and privacy processing. Receipt acknowledgement does not confirm that a notification is genuine or that deletion has been completed.

This callback does not request an eBay password or collect seller client secrets, access tokens or refresh tokens. Broader permissions may appear in the selected eBay consent configuration; consent permissions alone do not cause this service to modify listings, stock, messages or orders.

Hosting and access

Cloudflare Workers and D1 host this callback and its pending records. Cloudflare also processes network and security metadata to deliver the service. Access to receipt retrieval and authorization-code handoff requires the separately configured queue credential. This application code sets no tracking cookies, loads no external page resources and sends no eBay data to AI or advertising services.

Retention and deletion

Sign-in state expires within ten minutes. A returned authorization code expires within at most four minutes and is removed when handed off once to the authenticated local tool. Expired rows are removed during OAuth handling and by scheduled cleanup when its trigger is configured. Logical expiry does not itself erase a stored row.

Deletion-notification receipts remain pending until verified and handled, then are removed by authenticated acknowledgement. The local signature-verification and automated-erasure processor is still under development; notification receipt must not be treated as proof of completed erasure. Provider backup/recovery copies may remain within the configured recovery window. Restore procedures must address prior deletion requests before data is reused.

Current limits and requests

The local business-data reader is not enabled by this callback. This notice will be reviewed before additional collection or processing is enabled. Contact the address above to ask about personal data held by this service or to request access, correction or deletion. Requests and any applicable retention requirements need operator review.