evoke app privacy notice: test version

This notice covers the test version of the evoke app, for people invited to try it, including through Apple's TestFlight. evoke is made by Novum Group LLC, Sacramento, California. A full privacy policy replaces this notice before evoke is available to everyone. The website evokekitchen.com has its own notice.

Effective 24 October 2026. Version: test 2.

What evoke collects

Your email address, to sign you in. Cloudflare holds it to send your sign-in code, and evoke keeps a list of invited addresses. evoke's own database stores only a one-way code made from it, never the address.
Your recipes: everything you add or write, every version, and where it came from.
Posts you share to evoke: the caption of a public post you share, the creator's name and the post's link. On a Facebook page, the author's own first comment too.
Your cooks: what you made, when, what you changed, and notes you make about a cook.
What you say and type: the text of what evoke hears while hands-free is on (never the audio), your questions to evoke and its answers, your searches, and feedback you send.
Photographs of your cooking that you add. A photo of a recipe you add is read once to make the recipe, and isn't kept.
Meal plans and shopping lists: what you plan for each day, your lists and what's on them, and notes you add to them.
Names you give evoke: what evoke should call you, and first names or nicknames of people at your table with the stars they gave a dish, if you add them.
Your choices: whether evoke's AI and hands-free are on, and which version of the tester note you accepted, and when.
Technical details: your browser or phone type, kept with the app's log of each cook (what it did, such as sound starting and stopping) and with feedback you send; your screen size when you send feedback; counts of what happens in the app with no words in them (a cook started, a command understood, how long something took, what it cost); and records of sign-ins, kept for security.

evoke does not store your IP address, shows no advertising, and uses no outside analytics or tracking.

How it's used

To run evoke for you: add and show recipes, guide your cooks, answer your questions and keep your history.
To fix what breaks and make evoke better. The person who runs evoke can see evoke's records to help you and to fix faults.
To keep evoke secure.

Your information is not sold, not shared for advertising, and not used to track you across other apps or websites.

Where it goes

evoke uses three services to do its work.

Anthropic's AI, Claude, reads recipes you add from a link, photo or text, splits steps, answers your questions while you cook, plans meals, searches for recipes and suggests changes after a cook. If hands-free can't tell what you said, Anthropic works that out too. Each time, evoke sends only what that job needs. Anthropic doesn't train on it and deletes it within 30 days, unless it's flagged for misuse.
Deepgram turns what the microphone hears into text while hands-free is on, and reads the steps aloud. It keeps the audio only while it works on it and doesn't use it to train its models.
Cloudflare runs evoke's servers and database, sends your sign-in code and draws the recipe pictures. It handles basic request data, such as your IP address, to deliver and protect the service.

Cloudflare and Anthropic are bound by data-protection terms to use your information only to provide their service to evoke. Deepgram has agreed not to keep or train on requests evoke sends it, and a written agreement is being put in place.

Also:

Recipe websites: when you add or open a recipe from a link, evoke's server fetches that page. The site sees a request from evoke, not from you.
Posts you share: when you share a public post to evoke, your phone reads that one post, without signing in to anything, and takes its caption (on a Facebook page, also the author's own first comment). evoke's servers never visit the social site itself. The caption goes to Anthropic to make your recipe, and the caption itself isn't kept. From a Pinterest pin, evoke follows the pin's link to the recipe's own website, reads that site like any recipe link, and keeps the pin's link as where you found it. evoke saves the recipe to your kitchen, marked New, for you to check before you cook. It keeps evoke's own version, with the creator's name and a link to the post, and no photo, video or audio. A screenshot you share is read once and not kept.
Apple: Apple runs TestFlight. Feedback, screenshots and crash reports you send through TestFlight go to Apple and then to evoke, under Apple's own privacy policy. Microphone buttons in text boxes use your phone's own speech recognition (Apple's, on an iPhone).

Your choices

evoke's AI is part of how evoke works, so you're asked to agree to it when you first open the app. You can turn it off any time in Account. With it off, every recipe you've saved still works: cooking, sizes, timers, Collections, and hands-free's simple commands. Adding recipes, questions while you cook and meal planning stop until you turn it back on.
Hands-free is your choice. You're asked the first time you turn it on. Say Not now and you cook by tapping, and nothing goes to Deepgram. You can change it any time in Account.
To stop everything, delete your account in Account. It's all removed within the hour. Anything already sent to Anthropic is deleted by Anthropic within 30 days, unless flagged for misuse.

How long it's kept

What you say and type (the text of what hands-free heard, questions and answers, searches, feedback), and the app's log of each cook: 90 days, then deleted.
A note you deliberately make about a cook: kept with that cook. Delete the cook and the note goes with it.
Your recipes, cooks, photographs, meal plans, shopping lists and names: for as long as you have an account. A recipe you delete is fully removed after 30 days; your plans and lists still show the name of a dish you'd planned or shopped for.
A recipe site's own wording, shown while evoke makes its version: deleted when evoke's version is saved, or after 30 days if it can't be made.
Sentences evoke spoke to you: 90 days after you last heard them.
Security records: 12 months.
Counts with no words in them, and cost records: kept, with no link to you once your account is deleted.
Pictures evoke draws for recipes are shared between accounts and stay.
Backup copies, kept to recover from faults, may still hold deleted data for up to 30 days.

Your rights

Delete: Account → Delete my account. Everything above is removed within the hour, except shared pictures, security records, and the word-free counts and cost records. Backup copies are overwritten within 30 days.
See, correct or get a copy: most of it is on your screens and can be edited there. For anything else, write to info@evokekitchen.com. You'll get an answer within 30 days.
Withdraw your choices: the two switches in Account.
Using these rights never changes how evoke treats you.

California

evoke doesn't track you across other websites or apps, and no one else collects that kind of information through evoke. Browser "Do Not Track" signals therefore change nothing.
evoke does not sell or share personal information as California law defines those words.

Children

evoke is not for children under 13, and the test version is for invited adults. If a child's information has reached evoke, write to info@evokekitchen.com and it will be deleted.

Security

Sign-in uses a one-time code sent to your email, and everything travels encrypted.
Each person can see only their own recipes, cooks, plans and lists, and that is tested whenever evoke changes.
No system is perfectly secure. If something went wrong that affected your information, you would be told.

Where it's processed

evoke is run from the United States. Its services may process information in the United States and other countries.

Changes

If this notice changes in a way that matters, evoke tells you in the app before the change applies, and testers are asked to accept the tester note again.

Contact

info@evokekitchen.com · Novum Group LLC, Sacramento, California