1. Information collected
SellerOS may collect information provided directly by users, generated through account activity, or received from connected services. The final policy should identify required and optional fields and the lawful basis for each use.
2. Account and business data
Account information may include names, email addresses, company details, user roles and preferences. Business data may include products, costs, inventory, suppliers, evidence documents and reporting configurations.
3. Marketplace and API data
When integrations are enabled, SellerOS may process authorized marketplace data such as orders, fees, refunds, fulfillment events and related financial records. Access should remain limited to approved scopes and documented operational purposes.
4. Payment data handled by Stripe
Future subscription payments are intended to be processed by Stripe. SellerOS should not directly store complete payment-card details. The final policy must describe the information exchanged with Stripe once billing is implemented.
5. Cookies and local storage
SellerOS may use essential cookies and browser storage for authentication, security, preferences and service operation. The public website currently uses local storage to remember Light, Dark or System theme selection.
6. Security
SellerOS intends to apply appropriate technical and organizational safeguards to protect information. No system can guarantee absolute security, and the final policy should reflect the controls present in the production environment.
7. Data retention
Information should be retained only as long as needed for service delivery, legitimate operational requirements, legal obligations and dispute resolution. Final retention periods remain to be approved.
8. User rights
Depending on applicable law, users may have rights to access, correct, export, restrict or delete personal information and to object to certain processing. Applicable procedures and response timelines require legal review.
9. Third-party services
SellerOS may rely on infrastructure, analytics, marketplace, support and payment providers. The final policy should list relevant processors and explain international transfers where applicable.
10. Contact
Privacy contact details and the responsible legal entity will be added after client and legal approval. Until then, this section is a placeholder and should not be treated as a final notice.