Draft · counsel review required · not effective
Privacy notice
- Working version
- draft-0.2
- Audience
- Customers, applicants, sellers, drivers, and site visitors
Describes the information FOODERCE expects to collect and the controls that must be approved before real-person data is processed.
This source draft is not a published database agreement. It cannot be accepted, relied upon, or used to activate an account or transaction.
Proposed section 1
Scope and roles
This draft covers FOODERCE marketplace accounts, applications, orders, deliveries, seller tools, support, fraud review, and public discovery records. Counsel must identify FOODERCE's legal role for each data flow and each enabled jurisdiction.
Proposed section 2
Information collected
FOODERCE may need account, contact, application, credential, kitchen, catalogue, order, payment-reference, delivery, device, support, and security-event information. The production notice must identify required versus optional fields and avoid collecting data that is not needed.
- Identity, business, tax, and payment-onboarding information
- Private credential, preparation-site, vehicle, and screening evidence
- Order, delivery, communication, review, fraud, and audit records
- Approximate or precise location only when a feature requires it
Proposed section 3
How information is used
Proposed purposes include operating accounts, reviewing eligibility, displaying approved public listings, fulfilling orders, preventing fraud, supporting users, meeting tax or legal obligations, and improving the service. Data collected solely for a statutory verification purpose must not be repurposed incompatibly.
Proposed section 4
Sharing and processors
The final notice must name or categorize payment, hosting, storage, mapping, notification, screening, analytics, and support processors; explain seller/driver/customer disclosures; and distinguish public profile data from private evidence.
Proposed section 5
Retention, deletion, and legal holds
No universal retention period is approved. The final schedule must reconcile account deletion with payment, tax, safety, dispute, fraud, and immutable audit obligations, including exceptions and appeal paths.
Proposed section 6
Security and choices
FOODERCE intends to use private storage, least-privilege access, audit trails, encryption in transit, and bounded signed access. The final notice must explain access, correction, deletion, appeal, marketing, location, and jurisdiction-specific privacy rights.
Proposed section 7
Contact and changes
A real privacy contact, mailing address, effective date, change-notice process, and state-specific supplements must be supplied before publication.