Arnaud
e71c978e52
Adds a (marketing) route group -- Home, Features, About, Privacy, Terms, Contact -- reusing the app's design system/i18n/deploy pipeline rather than a separate site. Root page.tsx now branches on session instead of always redirecting to /recipes: logged-in visitors still land in the app unchanged, logged-out visitors see the vitrine home page. The actual integration point: proxy.ts's PUBLIC_PATHS previously sent every anonymous "/" request straight to /login before page.tsx's redirect ever ran. Added the new marketing routes to PUBLIC_PATHS, plus a separate exact-match list for "/" itself -- it can't go in the startsWith-matched array, since every path starts with "/" and that would make the whole app public. Also adds app/sitemap.ts and app/robots.ts (neither existed before), disallowing the authenticated app and the unlisted /r/ and /s/ share routes from crawling while allowing /u/ public profiles. Pricing page deliberately not included -- waiting on Stripe Checkout (STRIPE_PLAN.md) so its CTA goes somewhere real. Privacy/Terms are structural drafts flagged inline as not lawyer-reviewed, per STRIPE_PLAN.md's own tax-advice caveat -- same spirit here. Verified with a full production build (pnpm build) -- compiles clean, all 7 new routes render, since there's no DB in this sandbox to run the dev server against for a real click-through. v0.48.0
48 lines
2.4 KiB
TypeScript
48 lines
2.4 KiB
TypeScript
import type { Metadata } from "next";
|
|
import { AlertTriangle } from "lucide-react";
|
|
|
|
export const metadata: Metadata = {
|
|
title: "Privacy Policy — Epicure",
|
|
description: "How Epicure collects, uses, and protects your data.",
|
|
};
|
|
|
|
export default function PrivacyPage() {
|
|
return (
|
|
<div className="container mx-auto px-4 py-16 max-w-2xl space-y-6">
|
|
<div className="rounded-lg border border-yellow-500/40 bg-yellow-500/10 p-4 flex gap-3 text-sm">
|
|
<AlertTriangle className="h-4 w-4 text-yellow-600 shrink-0 mt-0.5" />
|
|
<p>
|
|
<strong>Draft — not yet reviewed by counsel.</strong> This page is a
|
|
placeholder structure, not a finished, legally-binding policy. Replace
|
|
before accepting real signups/payments (see <code>STRIPE_PLAN.md</code> §10).
|
|
</p>
|
|
</div>
|
|
|
|
<h1 className="text-3xl font-bold tracking-tight">Privacy Policy</h1>
|
|
|
|
<div className="space-y-6 text-sm text-muted-foreground leading-relaxed">
|
|
<section className="space-y-2">
|
|
<h2 className="font-semibold text-foreground">Data we collect</h2>
|
|
<p>Account information (email, name), recipes and content you create, usage data (AI calls, storage), and payment information (processed by Stripe — we never store card details ourselves).</p>
|
|
</section>
|
|
<section className="space-y-2">
|
|
<h2 className="font-semibold text-foreground">How we use it</h2>
|
|
<p>To provide the service (store your recipes, run AI features you request, process subscriptions), and nothing beyond that — no data is sold to third parties.</p>
|
|
</section>
|
|
<section className="space-y-2">
|
|
<h2 className="font-semibold text-foreground">Third parties</h2>
|
|
<p>AI providers (OpenAI/Anthropic/OpenRouter/Ollama, depending on your configuration), Stripe for payments, and your own configured integrations (webhooks, API keys) that you explicitly set up.</p>
|
|
</section>
|
|
<section className="space-y-2">
|
|
<h2 className="font-semibold text-foreground">Your rights</h2>
|
|
<p>Access, export, correct, or delete your data at any time from Settings, or by contacting us (see Contact page). EU/EEA users have rights under GDPR.</p>
|
|
</section>
|
|
<section className="space-y-2">
|
|
<h2 className="font-semibold text-foreground">Contact</h2>
|
|
<p>Questions about this policy — see the Contact page.</p>
|
|
</section>
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|