NiblGo Privacy Policy
Last updated: 18 October 2026 · Effective: 18 October 2026
NiblGo is a photo-first app for sharing meals with friends. This policy explains what we collect, why, who we share it with, and what you can make us do about it.
We are Bryce and Cameron, 4500 E. 33rd St., Sioux Falls, South Dakota 57110, USA, and we are the data controller for the information described here.
Questions, requests, or complaints: privacy@niblgo.com.
1. The short version
- We collect what you give us — your account details and what you post — plus a small amount about how you use the app.
- We show no ads, we use no third-party analytics or tracking SDKs, and we never sell your data. There is no advertising identifier, no third-party tracker, and no cross-app or cross-site tracking of any kind in NiblGo. We do keep our own simple record of how the app is used (section 2), only to understand and improve NiblGo; it stays with us and is deleted with your account.
- Your meal photos are stored in a public bucket: anyone with the direct link can view an image, whether or not they use NiblGo. Do not post pictures you would not want seen outside the app.
- If a post is shared out of the app, anyone with that link can see the post on niblgo.com without an account (section 5).
- You can delete your account from inside the app, and it really deletes.
- Section 7 covers your legal rights, including in the EU/UK and California.
2. What we collect
You give us
| What | When | Why |
|---|---|---|
| Email address | Sign-up | To create and secure your account, confirm it, and reach you about it |
| Password | Sign-up | Stored only as a salted hash by our authentication provider; we never see it |
| Handle, display name | Sign-up | Your public identity in the app |
| Profile photo or emoji, bio | Optional, any time | Shown on your profile |
| Meal photos | Each post | The core of the service |
| Your written blurb | Each post | Displayed with your post, exactly as you wrote it |
| Meal type, and optionally hashtags (from our fixed list), what it cost to make ($ to $$$) and a restaurant | Each post | Organising, browsing and searching meals |
| An invite code (a friend's handle) | Optional, at sign-up | So we know who invited you (section 2, "How you use the app") |
| Comments, likes, reposts, shares, saved posts | As you use them | To make the features work |
| Direct messages, including any photos you attach | When you message someone | To deliver them |
| Follows and blocks | As you use them | To build your feed and enforce your blocks |
| Reports about content or people | When you report | Safety and moderation (section 6) |
| Feedback and bug reports | When you send them | To fix and improve the app |
Collected automatically
| What | Notes |
|---|---|
| Your time zone | Set at sign-up so mealtime reminders arrive at sensible local times |
| Your posting streak | Derived from your own posting dates |
| How you use the app | When you open the app, which posts by other people appeared on your screen, which recipes on other people's posts you opened, recipe cards you made, invites you shared, and the invite code you entered at sign-up. Linked to your account and used only to understand and improve NiblGo (for example, how many people come back after a week). We look at it in reporting software on our own computers, as account ids, dates and counts, never with your name, email or what you wrote. Never used for ads or shared with anyone else |
| App version and platform | Attached only to feedback and bug reports you choose to send. Not collected otherwise |
| Server logs | Our hosting provider records standard request logs, including IP address, for security and reliability |
Stored only on your device, never sent to us
- Your mealtime reminder preferences and times
- Your recently searched profiles
- Your login session
These are removed when you delete the app.
We do not collect
Location data (the "where you ate" feature is disabled), contacts, health data, advertising identifiers, biometrics, or payment details. NiblGo has no ads, no in-app purchases, and no third-party analytics.
3. AI recipe formatting and nutrition
Two features send text off our servers, both only when you ask for them.
Recipe cards. When you tap the button to turn a blurb into a recipe card, the text of that blurb is sent to Anthropic (Anthropic PBC, USA) for formatting into structured ingredients and steps.
Nutrition estimates. When you tap to estimate nutrition, your ingredient list is sent to Anthropic to convert quantities into weights ("2 cloves of garlic" into grams), and the resulting plain food names — "garlic", "butter" — are sent to the USDA FoodData Central database to look up the actual nutrient figures. The nutrient numbers come from USDA, not from the AI, because a model asked for calories will produce a confident number that is not necessarily true.
- Only that text is sent. Your photo, name, handle, email and user ID are not sent to either.
- Anthropic processes it to return the recipe and, under its commercial terms, does not use API inputs to train its models.
- If you never tap either button, nothing is ever sent.
- USDA FoodData Central is a public database run by the US Department of Agriculture. We send it a food name; it sends back nutrient figures. It receives nothing about you.
- Recipe cards are generated by software and can be wrong. Check them, especially for cooking times, temperatures and allergens. See the Terms.
Anthropic's privacy policy: https://www.anthropic.com/legal/privacy
4. Who else we share with
We share only with the providers that make the app run. We do not sell your data, and we do not share it for advertising.
| Provider | What they handle | Where |
|---|---|---|
| Supabase | Accounts, database, photo storage, server functions | United States |
| Anthropic | Blurb text and ingredient lists, only when you ask for a recipe card or a nutrition estimate (section 3) | USA |
| USDA FoodData Central | Plain food names only, when you ask for a nutrition estimate | USA |
| Resend | Your email address and the email itself, to send account emails (confirming your account, resetting your password) | USA |
| Cloudflare | Hosts niblgo.com, including the pages behind shared post links; sees standard request data such as IP address | USA |
| Expo / Apple / Google | App distribution and delivery | USA |
We will also disclose information where we are legally required to — a valid court order, for example — or where it is necessary to investigate a safety issue or protect someone from harm.
International transfers. If you are in the EU, UK or Switzerland, your data may be processed in the United States. Where that happens we rely on Standard Contractual Clauses with the provider concerned.
5. Who can see what
- Visible to anyone signed in: your handle, display name, profile photo, bio, posts (with their hashtags and price), recipe cards, comments, likes, follower and following counts, streak, and the time zone your account is set to.
- Visible to anyone with a shared link: when you or someone else shares one of your posts out of the app, the link opens a page on niblgo.com that anyone with the link can see, no account needed. It shows your display name, handle and profile photo, the meal photo, your caption, the meal type, when you posted it, its price and hashtags, and the recipe card's title and cook time. It does not show the full recipe, comments, likes or anything else on your profile. Only that one post is shown, and only to people who have its link. A link shared from the app also carries the sharer's handle, so the page can suggest it as an invite code.
- Private to you: your email, saved posts, blocked accounts, your reports, and your feedback.
- Between you and the recipient: direct messages. No other user can read a conversation you are in — that is enforced by database rules, not merely by the app, so it holds even against a modified client.
- Your choice: you can make your follower and following lists private in Settings. The counts stay visible; the names do not.
What we can see. Being straight about this: as the people who run NiblGo we hold administrative access to the database, and that access is not limited by the rules above — it can reach any record, including message content and email addresses. We use it to operate the service, investigate reports and abuse, fix faults, and comply with the law. We do not read private messages in the ordinary course of running the app. Any service works this way; we would rather say so than let the section above imply otherwise.
Photos are a real exception and worth reading twice. Meal photos and profile photos are stored in a public storage bucket. The link is long and not guessable, and nothing in the app shows it to people who should not see the post, but anyone who obtains the URL can open the image without an account. Treat a meal or profile photo you upload as potentially public. Photos sent in messages are different: they are kept private, and only the people in that chat can open them, through links that expire after a short time.
6. Reports, moderation and safety
When you report a post, comment or message, we store the report along with a copy of the reported content. That copy is kept even if the author later deletes the original — otherwise deleting the evidence would defeat the report.
Reports survive the reporter's or the author's account deletion, no longer linked to the deleted account, so that a record of a safety issue is not lost when someone leaves. Feedback and bug reports you sent are kept too, but no longer linked to you or your handle once your account is deleted. This is our legitimate interest in running a safe service.
We aim to review reports within 24 hours.
7. Your rights
Whoever and wherever you are, you can:
- See your data. Email privacy@niblgo.com and we will send you a machine-readable copy. There is no self-serve export button in the app; we handle requests by hand. We will confirm you own the account before sending anything.
- Correct it. Edit your profile in the app, or ask us.
- Delete it. Settings → Account → Delete account. This removes your profile, posts, recipes, photos, comments, messages, follows and likes. Reports and feedback are retained as described in section 6.
- Take it elsewhere. The copy we send is JSON.
- Object or restrict. Tell us and we will consider it.
- Withdraw consent. Where we rely on consent, you can withdraw it at any time; it does not affect what we did beforehand.
If you are in the EU or UK, our legal bases are: performance of a contract (running the service you signed up for), legitimate interests (safety, moderation, preventing abuse), consent (mealtime notifications), and legal obligation. You may complain to your national data protection authority — in Ireland the DPC, in the UK the ICO.
If you are in California, you may request disclosure of the categories and specific pieces of personal information we hold, request deletion, and request correction. We do not sell or share personal information as those terms are defined by the CCPA/CPRA, and we do not use or disclose sensitive personal information beyond providing the service. We will not discriminate against you for exercising these rights.
We answer within 30 days (GDPR) or 45 days (CCPA), and will tell you if we need longer.
8. How long we keep things
| Data | Kept |
|---|---|
| Account, posts, photos, messages | Until you delete them or delete your account |
| How you use the app (app opens, posts you saw, recipes opened, invites) | Until you delete your account |
| Reports and reported-content copies | While relevant to safety: the copy of the reported content is kept for 2 years after the report is closed, so repeat behaviour is visible, and then deleted. The record that a report was made, and its outcome, stays |
| Feedback and bug reports | While relevant to the problem reported (no longer linked to you once your account is deleted) |
| Server logs | As retained by our hosting provider |
| Backups | Deleted content disappears as our provider's backups rotate |
9. Security
Passwords are hashed by our authentication provider — we never store or see them. All traffic uses HTTPS. Access to your data is enforced by database-level row security rules, so one account cannot read another's private data even if the app itself were modified. Our AI provider key is held server-side and never ships inside the app.
No system is perfectly secure. If we discover a breach affecting your personal data, we will notify you and the relevant authorities as required by South Dakota law and by any other law that applies to you — for users in the EU or UK that means the supervisory authority within 72 hours where the breach is likely to present a risk to you.
10. Children
NiblGo is not for children under 13, and we do not knowingly collect their data. In the EU/EEA the minimum age is 16, or the lower age your country sets (13–16). If you believe a child has given us personal data, contact privacy@niblgo.com and we will delete it.
11. Changes
We will post any change here and update the date at the top. If a change materially affects your rights, we will tell you in the app or by email before it takes effect.
12. Contact
Bryce and Cameron
4500 E. 33rd St.
Sioux Falls, South Dakota 57110, USA
Privacy requests, and anything about this policy: privacy@niblgo.com
Support, and anything else: support@niblgo.com
Either address reaches us. Privacy requests are answered from the first.