Privacy Policy

This policy explains what BlazeApps, which operates Marji (“we”), collects, why, and the choices you have. It covers marji.co and the Marji application. It is written to be read, not to hide behind. If anything is unclear, email hello@marji.co.

What we collect

• Account data — your name, email, and password hash when you sign up.
• Restaurant data — the menus, recipes, supplier invoices, and prices you upload so Marji can calculate margins. This is yours; we never sell it or share it with other restaurants or your vendors.
• Billing data — handled by Stripe. We store your Stripe customer and subscription IDs, never your full card number.
• Marketing data — if you use our free tools (like the margin calculator) we store the email you give us and the numbers you included in the requested report, so we can send that report. Marketing follow-ups require a separate subscription.
• Usage & device data — only with your consent, browser analytics and performance measurements from Vercel, advertising measurement from Meta and Google, and limited browser error diagnostics from Sentry. Browser replay is disabled. Optional browser telemetry excludes account, sign-in, diner-menu, embed and claim pages. Campaign attribution is collected only after consent: the public page you first arrived on, the website that sent you (its domain only, never a search phrase or full address), and any campaign label in the link. When you sign up we keep your cookie choice and, if you allowed it, that same first-visit information with your account; if you declined, we keep only the fact that you declined. If you withdraw consent while signed in, that stored first-visit information is replaced by the withdrawal.
• Optional onboarding answers — when you set up your restaurant you may say how you heard about Marji and what you want to do first, by choosing from fixed lists. You can skip both. The answers stay with Marji, are not sent to analytics providers, and are deleted with your account.
• Menu-scan diagnostics — to fix scans that fail or are never imported, we keep short technical records for each scan: the kind of step (opened, import blocked, import finished, failed), how many dishes were involved, and a fixed error category. They never contain dish names, prices, file names or error text, and are deleted with the scan or your account.

Free calculator inputs stay in your browser unless you request an email report or choose to import a recipe. A requested calculator report does not subscribe you to marketing emails. You can explicitly save one unfinished recipe in this browser and return without an account; later changes require another save. A complete recipe draft kept for account review is stored separately. Both copies use this browser profile for a seven-day usable window after saving. Expired drafts are removed when next accessed; you can discard a draft sooner. Other people using the same browser profile may be able to see it. Importing requires sign-in and your explicit review, creates a dish hidden from your public menu, and stores recipe and source details in your account and audit history.

Cookies & consent

Strictly necessary cookies — your sign-in session and your cookie choice itself — are always on; the product doesn't work without them. Optional browser analytics, advertising and error diagnostics load only after you click “Allow” on our cookie banner. You can change your mind anytime via the “Cookie settings” link in the footer. Declining prevents optional browser initialization. Withdrawal blocks subsequent optional events and clears local advertising and attribution cookies; it does not erase records already received by providers. Server diagnostics and abuse-prevention controls run separately to operate the service. Diagnostic events discard free-form messages, request payloads and identifying URL parameters; shared abuse limits use pseudonymous keys with expiry. Provider retention is managed separately from browser consent.

How we use it

• To provide the product: parse invoices, cost recipes, track margins.
• To send transactional email (verification, alerts, receipts).
• To send marketing email you can unsubscribe from in one click, via the link in every message.
• To measure and improve our marketing, when you've consented.
• To keep the service secure and prevent abuse.

Who we share it with

Only the processors that run the service, each under contract: Neon (database), Vercel (hosting, file storage, optional analytics/performance), Stripe (billing), OpenAI, Anthropic, and AWS (AI document reading and recommendations), Resend (email), Sentry (limited diagnostics), Upstash (shared abuse limits when configured), and — only with your consent — Meta and Google (advertising measurement). We do not sell personal data.

AI processing

Marji uses AI to read the invoices and menus you upload and to draft recommendations. That processing runs on the AI providers listed above (OpenAI, Anthropic, AWS), which handle your data solely to provide the service. We do not use your data to train AI models.

Retention

We keep account and restaurant data for as long as your account is active. Delete your account and the associated data is removed (some records may persist briefly in backups and where law requires). Lead emails are kept until you unsubscribe or ask us to delete them.

Your rights

Depending on where you live (including under GDPR and CCPA), you can request access to, correction of, or deletion of your personal data, and object to certain processing. Email hello@marji.co and we'll respond within 30 days.

Security

Data is encrypted in transit. Access is scoped per restaurant and gated by authentication. Security and your data explains who can see what, where it is stored and how export and deletion work. Report a vulnerability to hello@marji.co.

Changes

If we make material changes we'll update the date above and, for significant changes, notify account holders by email.