Privacy Policy
Last updated 17 November 2026
SnackWiz lets you share snack recipes and shop-bought food discoveries, follow other people, and buy and sell food through our marketplace. This policy explains what personal data we collect, why, who we share it with, how long we keep it, and the rights you have.
In short: we collect what we need to run SnackWiz and the marketplace. Your posts and profile are public. Your calorie goals and food diary are private to you and only kept if you choose to use them. We don't show ads, use third-party tracking or analytics tools, or sell your data. We remove location data from photos before they're stored. You can delete your account at any time in Settings.
1. Who we are
SnackWiz is run by Lee Edelmann, a sole trader trading as Codedbylee (CBL), of Suite RA01, 195-197 Wood Street, London, E17 3NU. We are the "controller" of the personal data described in this policy, which means we decide how and why it is used. Our registration number with the Information Commissioner's Office (ICO) is ZC284426.
For any privacy question, or to use your rights, contact help@codedbylee.com.
2. What we collect
When you create an account
- Email address
- Password, which our login provider stores only in hashed form, so nobody can read it
- Username and display name
- Confirmation that you are 16 or over and that you accepted our terms
- If you sign in with Google or Apple: the name and email address that account shares with us (Apple lets you hide your real email behind a relay address). We never see your Google or Apple password
- If a sign-in or sign-up fails: the type of error, a short error message, and your iOS and app version, so we can fix it. This holds no account, email address or device identifier
- Your favourite foods and dietary habits, if you choose to share them when you join. We use them to tailor what you see, and you can change them in your profile
Your profile and settings
- Bio, avatar colour, and profile photo if you add one
- Links to your Instagram, TikTok, YouTube or Pinterest, if you add them. We store only the usernames you type, and show them as buttons on your public profile
- Dietary tags and daily calorie target, if you set them
- A location area name (for example "Camden, London"), if you choose to set one
Calorie goals and food diary (optional)
If you choose to use the calorie calculator or food diary, we collect:
- For your goal: your sex, age, height, weight, how active you are and your goal (for example to lose weight), and the daily calories, protein, carbohydrate and fat we work out from them
- For your diary: each food you add, the day and meal, how many servings you had, its calories, protein, carbohydrate and fat, and the recipe, store find or product it came from
This is information about your health, so it is protected more strictly by law (see "Health information" below). It is private: only you can see it. We use it only to show you your goal and diary, never for advertising, to order your feed, or for anything else, and we never share or sell it.
Content and activity
- Recipes: titles, descriptions, photos, ingredients and nutrition values
- Store finds: titles, descriptions, photos, shop names, prices and calories
- Captions, comments, likes, saves, and who you follow
- If you turn on notifications: a code from your phone (Apple's push token) so we can send you a notification when someone messages you. It is saved on your profile and removed if you delete your account
- Private messages you send and receive. They are text only, visible only to you and the person you are writing to, and not used for advertising
- Which posts you view and share in the app, counted at most once a day for each post
- Videos you upload to import a recipe (used only to create the recipe, not stored by us afterwards)
- Videos of up to 5 seconds that you record in the app for a recipe, store find or listing, including the sound. We shorten and re-encode each one, check frames from it with an AI system, and store it with your post until you delete the post or your account
- Star ratings you give sellers (1 to 5). Only people who have bought from a seller can rate them. Others see only each seller's average and number of ratings, never who gave them
- Reports you make, people you block, and reports others make about your content
- Messages you send us, for example support requests, complaints and appeals
If you buy something
- Your full name, email address and phone number
- Your delivery address
- Your order: what you bought, the price, the seller, and its status and tracking details
- Which SnackWiz account placed the order, so you can track it and rate the seller afterwards
If you sell something
- Store name and description, trading address, business email and phone
- Food business registration number, VAT or company number, where you give them
- Your listings, orders, and your subscription plan and its status
- Details the law requires us to report to HM Revenue & Customs about sellers: your legal name, address, date of birth (individuals), National Insurance number or UTR, company and VAT numbers, and sales totals. Your tax reference and date of birth are encrypted, and none of this is shown to buyers
- Identity and bank details for payouts are collected by Stripe directly, under Stripe's own privacy policy. We only see whether your account can take payments and receive payouts.
Collected automatically
- Location: only when you tap to find nearby shops or fill in your area. We ask for approximate location, use it once for that search, and don't store your coordinates on our servers. You can turn location off at any time in your phone's settings.
- Photo metadata: photos taken on a phone can contain the place they were taken. We remove this location data from every photo before it is stored.
- Technical data: our servers record request logs (including IP address, time and the action requested) and short-lived rate-limit counters (your account ID or IP address) for security and to prevent abuse.
- On your device: SnackWiz stores your login session (in your phone's secure keychain), settings such as theme and currency, your AI-feature choice, and some cached content. Personal items are cleared when you sign out or delete your account.
We use no advertising, third-party analytics or tracking. We don't track you across other apps or websites, build advertising profiles, or sell or rent your data to anyone.
Payments
Payments are handled by Stripe. Your card details go directly to Stripe and never pass through or get stored on our systems. We receive only whether a payment succeeded and limited transaction details.
Health information
Your calorie goal answers (sex, age, height and weight) and your food diary are information about your health. Your dietary tags and favourite foods could also reveal something about your health or beliefs (for example being vegan or gluten-free). Under UK and EU data protection law, information that reveals your health or beliefs is "special category" data, so we only use it with your explicit consent. You give it when you save your goal, add food to your diary, or choose dietary tags, each time after being told what is kept and why.
- It is completely optional. You can use SnackWiz fully without it.
- It is private to you, used only to run the calculator and diary, and never used for advertising or shared with anyone, including sellers.
- You can withdraw your consent at any time: remove your goal in Food diary → Goals, delete diary entries, change your dietary tags in your profile, or delete your account. We then delete it (see section 8).
Please don't include sensitive details about yourself or others in public posts, comments or messages.
3. Why we use it, and our legal basis
Data protection law requires a lawful basis for each use of your data. Ours are:
- Running your account, showing your posts and profile, and providing the features you use: contract (providing the service you signed up for).
- Processing orders and payments, and sharing your delivery details with the seller: contract.
- Seller subscriptions and payouts: contract.
- Sending photos, videos and listing text to OpenAI for photo and video checks, recipe import and price suggestions: your consent, which you give in the app and can withdraw in Settings → AI features.
- Location when you ask to find shops: your consent, through your phone's location permission.
- Your calorie goal and food diary: your explicit consent (UK GDPR Articles 6(1)(a) and 9(2)(a)), which you can withdraw at any time as set out in "Health information" above.
- Seller ratings, and checking that only buyers can rate: legitimate interests (helping buyers choose trustworthy sellers) and legal obligation (consumer law requires us to take reasonable steps to prevent fake reviews).
- Showing the social media links you add on your profile: contract (providing the feature you chose to use).
- Ordering your For You feed using the posts you like, save, view and share and the people you follow: legitimate interests (showing you relevant content).
- Showing creators how their posts are doing (totals of views, people reached, saves and shares): legitimate interests (helping creators understand their audience).
- Moderation, handling reports, preventing abuse, fraud and spam, and keeping SnackWiz secure: legitimate interests (keeping users safe), and legal obligation where the Online Safety Act applies.
- Reporting seller information to HMRC, keeping tax and accounting records, and responding to food safety authorities, courts or the police: legal obligation.
- Keeping records needed to deal with complaints or legal claims, and keeping banned users off SnackWiz: legitimate interests.
- Service emails (order receipts, shipping updates, sign-up and password codes, important changes): contract or legitimate interests. We don't send marketing emails.
Where we rely on legitimate interests, we have balanced them against your rights. Where we rely on consent, withdrawing it doesn't affect anything done before.
4. What other people can see
SnackWiz is a social app, so some things are public to anyone using it: your username, display name, bio, profile photo, published recipes and store finds, comments, likes, who you follow, and your follower counts. Sellers' store names and listings are public, and buyers are shown a seller's trading address, business email and phone, as consumer law requires.
Creators can see totals for their own posts, such as views, people reached, saves and shares. They never see who viewed, saved or shared a post. Sellers and everyone else see a seller's average star rating and number of ratings, never who rated them. Social media usernames you add are shown on your public profile.
Kept private: your email address, password, saved posts, blocks, reports, AI and location choices, calorie goal, food diary and the ratings you have given, and your delivery address and phone number, which are shared only with a seller when you buy from them.
Please don't put anything in a post, bio or comment that you wouldn't want to be public. Once published, others may have seen or copied it even if you later delete it.
5. Who we share it with
We share data only as far as needed, with:
Service providers who work for us
- Supabase: database, login and photo storage
- Render: hosting our servers
- OpenAI: checking photos and video frames for prohibited content, turning uploaded videos into recipes and suggesting prices for store listings from their name and description, with your permission. OpenAI keeps API data for up to 30 days for abuse monitoring and doesn't use it to train its models.
- Google Maps Platform: finding nearby shops and suggesting addresses at checkout (our server sends the search, not your account details)
- Resend: sending emails such as sign-up codes, receipts and shipping updates
- Google and Apple: signing you in, if you choose Continue with Google or Continue with Apple
- RevenueCat: managing seller plans bought through Apple (receives your account ID and the plan purchase history, not your name or card details)
- IONOS: hosting our support email inbox, including reports sent to our moderators
- Food databases (Open Food Facts, USDA FoodData Central, FatSecret): food searches only, no account details. Open Food Facts searches go directly from your phone, so Open Food Facts receives your IP address.
Others
- Stripe: processes payments and seller payouts, and is responsible in its own right for its identity checks and fraud prevention.
- Apple: if you subscribe through the App Store, Apple handles that payment under its own privacy policy.
- Sellers: when you place an order, we share your name, delivery address, phone number and email with the seller so they can send it. The seller becomes responsible for that data and must use it only for your order.
- Buyers: when you sell, buyers see your store name and the details on your listings and order emails.
- Authorities: HMRC (seller reporting), food safety authorities and councils, the police, courts or regulators, where the law requires it or to protect someone's safety.
- Professional advisers and insurers, such as a solicitor or accountant, where needed.
- A buyer or successor of SnackWiz, if the business is sold, transferred or moved to a company we own, who will be bound by this policy.
6. Automated decisions
Every photo, and frames from every video, is checked automatically by an AI system before it is published, to detect prohibited content such as nudity or graphic violence. Flagged photos aren't published. Explicit words in text are masked automatically, and content reported by several people may be hidden automatically until we review it.
If you think an automated decision was wrong, email help@codedbylee.com and a person will review it. Your For You feed is also ordered automatically using the posts you like, save, view and share and the people you follow; this doesn't have legal or similarly significant effects on you.
7. International transfers
Some providers (including OpenAI, Stripe, Google, Resend, RevenueCat and Render) process data outside the UK, including in the United States. Where that happens, the transfer is protected by an adequacy decision (such as the UK-US Data Bridge), the UK International Data Transfer Agreement or Addendum, or equivalent safeguards. Contact us for details.
8. How long we keep it
- Account, profile, posts, comments, photos, videos and private messages: until you delete them or your account
- Calorie goal: until you remove it or delete your account
- Food diary entries: until you delete them or your account. The diary shows one day at a time, but past days are kept so your entries aren't lost
- Seller ratings: until you or the seller delete your accounts
- Videos uploaded for recipe import: deleted from our server as soon as the recipe is made
- Orders, payments and seller tax reporting records: 6 years after the end of the tax year they relate to, as UK tax law requires
- Reports, moderation decisions and appeals: 12 months after they are resolved, or longer if needed for a legal claim
- Details of banned accounts: as long as needed to keep them off SnackWiz
- Support emails: 2 years after the conversation ends
- Records of which posts you viewed or shared: 90 days. After that only daily totals for each post are kept, with nothing linking them to you
- Server request logs: up to 30 days. Rate-limit counters: deleted when they expire, within 24 hours
- Backups: deleted data can remain in encrypted backups for up to 30 days before it is overwritten
9. Your rights
Under UK data protection law (and EU law if you are in the EEA) you have the right to:
- Access: get a copy of the data we hold about you
- Rectification: correct anything inaccurate or incomplete
- Erasure: have your data deleted
- Restriction: limit how we use your data
- Portability: receive your data in a machine-readable format
- Object: object to processing based on our legitimate interests
- Withdraw consent: where we rely on it, at any time
- Human review of automated decisions that significantly affect you
To use any of these, contact help@codedbylee.com from the email address on your account. It's free, and we will reply within one month (we may extend this by two months for complex requests, and will tell you if so). We may need to confirm your identity first, and some rights have legal limits, for example where we must keep tax records.
Deleting your account
You can delete your account at any time from Settings → Delete account. This permanently erases your profile, posts, photos, videos, comments, private messages, likes, saves, follows, ratings you gave, calorie goal, food diary and records of posts you viewed or shared, and cancels subscriptions billed through SnackWiz. It can't be undone.
Records of completed orders and seller tax records are kept for the periods in section 8, as the law requires. If you would rather we did the deletion for you, email help@codedbylee.com from your account's email address and we will do it within 30 days.
Complaints
If you are unhappy with how we have handled your data, please tell us first at help@codedbylee.com with "Data protection complaint" in the subject. We will acknowledge your complaint within 30 days, look into it, keep you updated, and tell you the outcome without undue delay. You can also complain to the Information Commissioner's Office at ico.org.uk (0303 123 1113), or to your local data protection authority if you are in the EEA.
If you live in the United States
Some US state laws, such as Washington's My Health My Data Act and Nevada's consumer health data law, give extra protection to "consumer health data". For SnackWiz that means your calorie goal answers and food diary. We collect them only with your consent, from you, to provide the calculator and diary. We don't sell them, share them with third parties (other than the service providers in section 5 who store them for us), or use them for advertising. You can see them in the app, delete them, or withdraw your consent at any time as described above, or by contacting us. We don't knowingly sell personal information of any kind.
10. Children
SnackWiz is not for anyone under 16, and we don't knowingly collect data from children under 16. If we learn that a user is under 16, we will close their account and delete their data. If you believe a child has given us personal data, contact help@codedbylee.com.
11. Security
- All communication is encrypted in transit using HTTPS
- Login tokens are stored in your phone's secure keychain
- Database rules restrict each user to their own private data (including your food diary and the ratings you gave), and sensitive tables can only be reached by our server
- Passwords are hashed and never stored in readable form
- Location data is removed from photos before they are stored
- Sellers' tax references and dates of birth are encrypted before they are stored
- Our servers apply rate limits and abuse protection
No system is completely secure. If a breach is likely to put your rights at risk, we will report it to the ICO within 72 hours and tell you without undue delay where the law requires it.
12. Changes to this policy
We may update this policy. If a change is significant we will tell you in the app or by email before it takes effect. The date at the top always shows the current version.
Contact
Email help@codedbylee.com, call 0161 820 0696, or write to Lee Edelmann, trading as Codedbylee (CBL), Suite RA01, 195-197 Wood Street, London, E17 3NU.