1. Who we are
foodnear.me ("we," "us") operates AI-native restaurant discovery infrastructure, including public websites, APIs, and MCP endpoints. Contact: api@foodnear.me.
2. Information we collect
Depending on how you interact with the service, we may collect:
- Lead and waitlist data: restaurant name, city, email, and source tag when you submit an ADO audit or contact form.
- Technical logs: IP address, user agent, request paths, timestamps, and error diagnostics for security and rate limiting.
- API/MCP usage metadata: query parameters (e.g. location, search terms), rate-limit counters, and aggregated usage patterns.
- Restaurant partner data: business details, menus, and verification records provided by participating restaurants.
We do not intentionally collect sensitive categories (health diagnoses, government IDs) through public beta forms. Do not submit them.
3. How we use information
- Provide, secure, and improve discovery, API, and MCP services.
- Respond to audit requests, support inquiries, and onboarding.
- Enforce rate limits, prevent abuse, and maintain system integrity.
- Measure product usage and plan capacity (aggregated where possible).
- Comply with legal obligations and enforce our Terms of Service.
4. Legal bases (where applicable)
For users in regions with data-protection laws (e.g. GDPR, UK GDPR), we rely on: (a) consent for marketing communications where required; (b) legitimate interests in operating and securing the platform; and (c) contractual necessity when providing services to restaurant partners.
5. Sharing and processors
We may share data with service providers that help us operate, including:
- Hosting and deployment (e.g. Vercel)
- Database and authentication (e.g. Supabase)
- Email delivery (e.g. Resend), when configured for lead notifications
We do not sell personal information. We may disclose information if required by law, to protect rights and safety, or in connection with a merger or acquisition with appropriate safeguards.
6. Retention
Lead records are retained while relevant to onboarding and communication, unless you request deletion or a shorter period is required by law. Server logs are retained for a limited period for security and debugging, then rotated or aggregated.
7. Security
We use industry-standard measures including encrypted transport (HTTPS), access controls, and separation of public vs. service credentials. No method of transmission or storage is 100% secure.
8. Your choices and rights
Depending on your location, you may have rights to access, correct, delete, or restrict processing of your personal data, or to object to certain processing. To exercise these rights, email api@foodnear.mewith "Privacy request" in the subject line.
9. AI agents and public discovery files
We publish machine-readable discovery assets (e.g. llms.txt, OpenAPI, MCP manifests) intended for AI systems. These describe public capabilities and documentation links — not private user data. Agent queries to our API may be logged as described above.
10. Children
The service is not directed to children under 13 (or 16 where applicable). We do not knowingly collect data from children.
11. International transfers
Data may be processed in the United States and other countries where our providers operate. We use appropriate safeguards where required for cross-border transfers.
12. Changes
We will post updates on this page with a revised date. Material changes may also be communicated via email to registered leads where appropriate.
This Privacy Policy is a beta-stage template. Consult qualified privacy counsel before treating it as complete for regulated markets.