The plain-language version

Privacy policy

Effective October 6, 2026

Tasti is a social tasting journal. This policy explains the information Tasti may handle when you use the app and this website, why it is used, and the choices available to you.

Information you provide

When you use the Tasti app, you may provide your name, email address, account and profile information, photos or videos, tasting and recipe content, notes, ratings or reactions, food and pairing selections, dates, comments, saves, and social connections. You may also add a user-entered Place, City, and Region to a tasting. Tasti stores those fields with the linked tasting: a named venue can identify a precise place, while City and Region are coarse location. The current app does not request GPS location, use Core Location, or collect coordinates; it stores only the location text you choose to enter. Content you choose to share may be visible to other people according to the audience and privacy settings available in the app.

Information used to operate Tasti

Tasti may process identifiers from an authentication provider, product interactions and other usage records, limited performance measurements, basic device or request information, and records needed to keep the service secure and reliable. To deliver notifications, Tasti stores an APNs device token linked to your account. Tasti also stores the people you follow and related relationships in its in-app social graph to provide social features and personalize recommendations. Optional address-book matching is described below. The app may access photos or videos only when you choose to select, import, or upload them.

Phone verification

When you enter your mobile number and tap “Send verification code” or “Resend code,” Tasti uses that number to deliver your requested verification text and authenticate your account. Supabase manages account authentication and Telnyx delivers verification codes. These service providers may process your number, the verification message, delivery records, and messaging preferences to deliver requested codes and protect the service. Your authentication phone number is not displayed on your public Tasti profile.

Tasti does not sell or share mobile information, SMS opt-in data, or consent with third parties for promotional or marketing purposes. These categories are excluded from other data-sharing descriptions in this policy. Service providers may process this information only as needed to provide authentication, messaging, and related service protection. See SMS verification terms for message frequency, support, and opting out.

Optional contact discovery and invitations

If you choose Sync your contacts and grant contact access, Tasti reads the contacts available under that permission. Names, local contact identifiers, and number labels stay on your device. Tasti sends normalized phone numbers to its Supabase service to find eligible people whose phone discovery setting is on. During new-account profile setup, “Let people find me by phone” starts on and can be turned off before continuing. Existing accounts keep their current setting. You can change this choice later in Contact settings. Discovery does not display your phone number and is separate from syncing. Matching does not follow anyone or unlock their posts.

The matching database does not store submitted contact phone numbers. It records your profile, lookup time, and number count to limit lookups. Older counters are removed on a later lookup, rather than automatically expiring after 24 hours. Contact results are temporary and clear when you leave the screen, the app backgrounds, or the account changes. Stop syncing clears local sync consent and results; it does not change your discoverability choice. You can search Tasti names and usernames without syncing.

Inviting a contact opens your system Messages composer for the recipient you choose, with editable text and a cancel option. If Messages is unavailable, the system share sheet receives invitation text without that recipient’s number or name. The Feed invitation button opens the share sheet directly. Tasti does not send invitations automatically or confirm delivery.

How information is used

• Provide your tasting journal, feed, search, rankings, saves, and social features.
• Apply your privacy choices and protect private content.
• Maintain, troubleshoot, and secure the service.
• Respond to support requests and comply with legal obligations.

iOS app product analytics

If you choose to allow it, the iOS app uses product analytics to understand which app pages and features are used and to improve reliability and product flows. This uses a separate choice and event contract from optional website analytics described below. The app may record page or feature use, active screen duration, recipe-search metadata (such as character count, result count, outcome, surface, and duration), and actions such as opening or saving a recipe, starting a recipe log, and successfully publishing a tasting.

PostHog processes these product-analytics events for Tasti. They are content-free, pseudonymous user-level telemetry, not anonymous or aggregate data. Normalized recipe searches and raw recipe-search text are not sent to PostHog. User-created content—including notes, tags or descriptors, photos, rating values, and friend identity—is not sent in these product-analytics events. Recipe and dish identifiers used in events are opaque catalog identifiers. When enabled for a signed-in profile, app analytics are linked to an opaque Tasti profile or account identifier so we can understand activity across sessions. Fixture or no-auth use, such as app testing without an account, is a no-op; Tasti does not create anonymous or install-level app analytics captures.

The app does not use IDFA, cross-app tracking, advertising profiles, or third-party advertising for these analytics, and Tasti does not sell personal information.

Tasti's PostHog project is in the United States. Its project setting discards IP addresses, and app events also disable location enrichment. Turning off analytics stops later submissions and cancels queued events that have not been sent; an event already being delivered may finish.

Recipe search history and taste predictions

The current app’s Search tab matches recipes and people in Tasti without sending your search text to an AI provider. Search, search history, and taste predictions are normal Tasti features and work independently of your optional product-analytics choice. The current app has no switch to disable search history or taste predictions; you can still clear stored search history.

Tasti stores normalized recipe searches in its first-party Supabase database. These are deliberate searches you submit by pressing Search or selecting a displayed recipe result—not each character you type or searches for people. You can clear stored searches in Privacy Settings. Tasti uses this history to understand what recipes people are looking for. It does not change current Feed suggestions, search results, or taste predictions. A private operator report may show thresholded demand; in private beta a named concept may appear after one distinct searcher to the one authorized operator, while public mode requires at least twenty distinct searchers. The report does not automatically import, generate, or rewrite recipes.

Stored search history remains in Tasti’s first-party database and is not sent to PostHog or used by Tasti for generative-model training. Product analytics may separately include search metadata such as query character count, result count, duration, surface, and outcome, but never the search terms or recipe names.

Feed search in older app versions

Older app versions may include a separate AI-powered Feed search. The current app no longer offers that feature. When it is enabled in an older version, a submitted query that Tasti cannot interpret with its built-in recipe filters sends that request’s text to Cloudflare Workers AI to interpret ingredients, cuisine, and other search criteria. Tasti then matches and orders recipes using its stored metadata; Cloudflare does not choose the recipes. We do not attach your identity, account credentials, personal history, or candidate recipes to the interpretation request. The words you enter may themselves contain personal information, so avoid including information you do not want processed for search.

In older versions that include this feature, the AI-powered Feed search setting in Privacy Settings controls request processing separately from optional analytics and saved search history. Existing saved AI-search choices are retained when you update the app. If you still use an older version on another device, use that version’s setting to change its AI-search permission, or contact us for help. Turning it off blocks later AI interpretation requests from this device, but cannot recall query text from a request already sent. Feed searches that Tasti can interpret with its built-in recipe filters remain available in those older versions. Cancelling or replacing a Feed search discards its response in the app, but may not undo a search already processed and recorded by the server. Cloudflare describes its handling of model requests in its Workers AI data usage documentation.

Food preferences and tasting predictions

You may save dietary or religious food restrictions, cuisines, cooking proficiency, recipe interests, and discovery style. These private choices shape the recipes shown in “We think you'd like.” A food restriction may be sensitive; Tasti does not use it to establish your religion. The choices do not change search results or your predicted tasting score.

When you have enough scored recipes, Tasti may estimate how you might score another recipe using your own tasting history and recipe features; imports, saves, and lists provide weaker interest signals. A prediction is labeled separately from a score you actually gave. Search history is not an input to that prediction. The fitted model is first-party; Tasti does not send your private tasting history to a generative AI provider to calculate that score.

Recipe imports and original sources

When you import a recipe from a website or supported video post, Tasti may fetch its public title, description or caption, creator information, source URL, and image. Tasti may send the recipe’s title, written source text, and recipe details to Groq AI to identify its name, ingredients, and recipe attributes. Tasti does not append your private tastings, photos, scores, account ID or social connections to that request. The source text may itself contain personal information about the creator. Only share public recipe links; please do not submit private or signed links. Supported Instagram and TikTok imports can use written source information and a cover observed on your device, with recovery in the app when needed. Some sources are unavailable or have incomplete captions and may require a recipe name. Tasti’s backend no longer uses Bright Data to retrieve Instagram posts. Tasti may store source metadata, derived recipe details and copied source images to show an imported recipe with attribution.

Tasti uses YouTube API Services to retrieve public video information such as the title, description, channel name, thumbnail, duration, and source identifier, and to support embedded playback. The public metadata may be stored and processed for recipe imports as described above. Tasti does not request access to your private YouTube account data. Google handles information from its services under the Google Privacy Policy.

Opening an original website or embedded video connects your device to that publisher or video provider, including YouTube, TikTok, Instagram, or Facebook. Their pages and players may serve content and advertisements, process information such as your IP address, browser, device, and viewing activity, and store or access cookies or similar technologies on your device under their own policies. Tasti’s optional analytics choice does not control processing by those original sources.

Pasted-text recipe extraction is no longer available, including in older app versions; new requests through that feature are rejected without sending their text to Groq.

Community safety

If you report a profile, Tasti saves your account, the reported profile, the reason and details you provide, and a snapshot of that profile's name, username and avatar reference. Authorized reviewers can use the report and record their decision. If either account is deleted, Tasti removes its linked report and review notes from the active database. Blocking a person stores the relationship so Tasti can limit interactions and visibility between you.

Copyright requests

If you send a copyright notice or counter-notice, Tasti processes the contact details, signatures, content identifiers, and dispute information you provide to assess and respond to the request. Tasti may share relevant notice information with affected parties. A qualifying counter-notice, including its contact details, is forwarded to the original complainant. Copyright correspondence may be retained separately from an app account when needed to resolve disputes, enforce the repeat-infringer policy, or meet legal obligations. See the copyright complaint procedure in our Terms.

Website waitlist

When you join on this website, Tasti stores your email address, signup time, a permanent signup number, the privacy-notice version, and records needed to prevent duplicate signups and deliver your welcome email. The waitlist is stored privately in Supabase and does not create an app account. Resend receives your email address and the welcome message to send it. A delayed welcome email does not remove your place. We also keep delivery status and retry records so a temporary failure can be recovered without repeatedly sending the same welcome.

Cloudflare hosts the website and processes requests. Cloudflare Turnstile checks for automated abuse, using request and browser information; this protection is separate from optional analytics. We do not put your email into website analytics. Earlier waitlist submissions collected through Tally may be transferred into this waitlist, keeping their original order where known.

We keep waitlist information while managing early access, until it is no longer needed or you ask to be removed. To request removal or a copy, email otie.net@gmail.com. Removal does not change anyone else’s signup number. Provider delivery and backup records can have separate retention periods.

Optional website analytics

When website analytics is available, it starts automatically for visits Cloudflare locates in the United States, United Kingdom, or France, unless you have opted out. For every other or unknown location, we first ask you to choose “Allow analytics.” Cloudflare estimates the country from your connection; it is not GPS location and can be inaccurate, for example when using a VPN. Joining the waitlist does not give permission for analytics.

We count page views, selected navigation clicks, scroll-depth milestones, email-field selection, signup attempts, and confirmed signups to improve this website. Page views have separate country, mobile/tablet or desktop, and broad referring-site totals. These categories are not combined into individual profiles. Reloading adds another page view; these are activity totals, not a count of unique people.

Cloudflare processes connection information, including IP addresses and browser headers, to serve and protect the website and derive these broad categories. Our analytics store keeps daily counters rather than individual browsing histories. Counter records and report payloads contain no visitor or session identifiers, IP addresses, full browser headers, email addresses, form contents, or arbitrary URL parameters. Analytics is not linked to your waitlist entry or app account. We do not use website session recording, heatmaps, advertising pixels, or automatic capture of page contents.

After each UTC day, we send the daily totals to PostHog for reports. The active counter store deletes each day’s counters seven days after that day ends; provider backups and PostHog reports have separate retention as described below. Reports may be incomplete because of consent choices, browser blockers, network failures, or abuse filtering.

We save only your explicit analytics allow/decline preference in your browser’s local storage. You can turn analytics off through “Analytics preferences” in the footer when analytics is available. This stops future collection and cancels pending requests, but cannot withdraw requests already received or remove your contribution from earlier aggregate totals. Your opt-out applies to later visits in that browser until you change it or clear local storage. We also honor Global Privacy Control and Do Not Track signals, even if you previously allowed analytics. Analytics may be unavailable or blocked without affecting signup.

Service providers

Tasti relies on service providers for functions such as authentication, hosting, database and photo storage, analytics, search interpretation, and recipe import. Tasti does not sell personal information or use tasting content for third-party advertising.

For the website waitlist, Cloudflare provides hosting and abuse protection, Supabase stores signups, Resend sends welcome emails, and PostHog processes optional analytics under the website settings described above. The website does not use your app analytics preference as permission.

Retention and deletion

Normalized recipe searches remain in the active first-party database until you clear your recipe search history or request account deletion. Clearing history removes active search sessions and derived search data without removing saves, ratings, tastings, or posts.

You can request account deletion in the app under Feed → menu → Delete account (older versions: Profile → Privacy → Delete account). Tasti records the request and runs a background process to remove linked account data, authentication, journal content and stored media from active systems, and to request deletion of linked product analytics from PostHog. If you used Sign in with Apple, Tasti also attempts to revoke that connection. The app may return to Welcome after it accepts and saves your deletion request and clears account data on this device, while server deletion may still be in progress. If Apple revocation cannot be verified, you can remove Tasti under Sign in with Apple in your Apple Account settings or contact support. A new account is a new identity; seeing Welcome or creating one does not confirm that every deletion step has finished.

Deletion starts after you confirm. Removing analytics data can take several days; provider delays may take longer. Keep Tasti installed. In app versions that show Deletion status, open it on Welcome or from Delete account in the Feed menu (older versions: Profile → Privacy) on the device that requested deletion. The status screen shows Account deleted only after the server confirms completion and local account cleanup succeeds. If that option is unavailable or you need help, contact support.

Some information may remain separately: another person's own posts and replies, shared external recipes without your attribution, and records needed to track deletion, handle support requests, protect the service, or meet legal obligations. Copies already delivered to other people or downloaded from shared content cannot be recalled. Service-provider backups may retain copies after active data is deleted, and a later restore could reintroduce data until deletion is reapplied. We cannot promise immediate deletion from backups or a fixed expiry for every provider record. Contact support for help with the status of a request.

Your choices

Product analytics stays off until you choose Allow and continue or turn on Product analytics in Privacy Settings and Tasti confirms your choice. Settings opens Privacy Settings with analytics off, so you can leave it off and continue using Tasti. An earlier informational notice does not count as consent to this analytics request. Search history and taste predictions are part of the current app rather than optional privacy settings. Updating to this version restores those features if the retired shared switch was off; your product-analytics and legacy AI-search choices remain separate.

In Privacy Settings, the Product analytics switch saves automatically, and you can leave the page while a change saves. Turning analytics off takes effect immediately on this device while it is saved to your account; enabling it waits for server confirmation. If saving fails, the app offers a retry. You can also clear recipe search history. Turning off product analytics stops new submissions from this device. Once the account update succeeds, Tasti cancels queued unsent events; this does not delete events already delivered to PostHog. You can also choose what to post, who to connect with, and whether to grant photo or video access.

You may request help accessing, correcting, exporting, or deleting information by emailing otie.net@gmail.com. Rights vary by location.

Children

Tasti is not directed to children under 13, and Tasti does not knowingly collect their personal information.

Changes

This policy may change as Tasti develops. Material updates will be reflected by a new effective date and, when appropriate, an in-app notice.

Contact

For privacy questions or requests, email otie.net@gmail.com.