Privacy Policy

Depending on what you use, ChecIt may process your account details, profile and food preferences, optional health information, location, searches, saved items, agent conversations, social content, device identifier hash, push token, and purchase entitlement.

For reservations, we process the restaurant, time, party size, status, seating or occasion choices, and special requests. ChecIt never collects payment-card numbers, CVV, banking passwords, one-time codes, or payment secrets.

When you consent, Mixpanel processes first-party product events so we can understand whether ChecIt works and improve it. We do not use IDFA, sell personal data, or track you across other companies’ apps or websites. You can withdraw both uses through the shared Personalization & product analytics control in Settings.

Paid business content is visibly labeled Highlighted ✦. It is not third-party behavioral advertising.

You can publish profile details, posts, comments, photos, videos, reactions, playlists, and stories to the audience shown in the product. Stories stop appearing to that audience after 24 hours. Limited owner archives, moderation records, and deletion records may remain.

Private accounts use follow requests. Content access depends on accepted follows and applicable blocks; an old media link does not grant permanent access. Accounts that identify themselves as teens receive additional private-account controls. Public publishing and age-related settings should accurately reflect your circumstances.

Follows help shape your feed. Blocks and mutes are private safety choices. Reports are sent to authorized moderation workflows, not posted publicly.

If you connect a personal OpenAI API key, ChecIt encrypts it on the server and uses it to authenticate your in-app Agent replies, including photos attached to those chats. The key is sent only to OpenAI for the supported model-access check and these requests. It is not included in model prompts, ordinary logs, data exports, or other users’ access. Voice, SMS, separate photo tools, and background chat titles do not use your personal key.

You can replace or remove a personal key in API settings. Removal deletes its saved encrypted value and prevents new requests from using it; a provider request already sent may still complete. We retain redacted connection metadata, usage counts, and security events for operation and account export until account deletion. OpenAI processing, charges, and retention also follow your provider account settings and terms.

ChecIt developer keys permit only the scopes shown when you create them. The initial profile:read scope returns your own channel identity fields: ID, handle, display name, bio, avatar URL, and links. We store a verifier rather than the issued token, along with its label, scope, expiry, revocation, and usage metadata. The token is shown once. Revoke a key to stop new authorized requests; information already retrieved by an integration is not recalled.

Requests and replies submitted through Help are linked to your account and available to authorized support staff. Categories, status labels, and messages help us respond. Do not include passwords, API keys, payment details, or other sensitive credentials in a support request.

People invited to the same Tasting Room can see who joined, the display names and food items participants share, quantities or notes, presence, and each person’s share of the total. People outside that cart cannot read it. Payment details are never part of the cart.

When you separately enable an automatic plan, we store the exact meal, restaurant, choices and preparation requests, schedule, time zone, expiry, tip, spending and order-count limits, and your authorization. For delivery, we also store the address and coordinates you review. Address lookup uses Google Maps on the web or your device geocoding service on mobile. A delivery address is fixed for that plan and does not follow your current location.

When an authorized order is submitted, its details and delivery information where applicable are shared with the selected restaurant for fulfillment. Your private account records the result and spending against the plan. Notifications use generic status text. A pending confirmation may be stored on the originating device to reconcile a lost connection without creating a duplicate plan. Authorizations and results are available through account export and removed with account deletion, subject to the limited retention described below.

Location supports nearby food, maps, deals, and community results only when you allow it. You can deny or revoke location and continue with less local relevance. Precise search location is not shown to other users or merchants. A delivery address and coordinates you explicitly confirm for an order are shared with its restaurant for fulfillment.

With both ChecIt location consent and device or browser permission, we refresh your search center while ChecIt is open in the foreground, including when you return to it. We do not request background location tracking. Your manually chosen search radius stays the same. For signed-in accounts, the current search center and saved radius can sync through your profile to your other devices. Turn off location in ChecIt Settings or your device or browser settings to stop new location collection.

ChecIt combines an app-install identifier with limited device and environment signals on your device, then sends only a one-way hash to enforce trial and promotion limits and prevent abuse. The raw signals are not sent. The hash is not used for advertising or cross-app tracking.

Cloudflare Stream processes and delivers user videos as HLS streams. Expo processes push tokens and delivery receipts for alerts you enable. Supabase provides authentication, database, and storage; OpenAI provides requested AI or transcription; Google Places provides place data; USDA FoodData Central may provide nutrition data.

Invalid push tokens are disabled. You can change notification categories in Settings and device permissions.

SMS is opt-in and uses a verified phone number. ChecIt and Twilio process messages, opt-in or opt-out state, and delivery information. Reply STOP to opt out; message and carrier rates may apply.

User-started dictation audio is sent for transcription and is not intentionally retained by ChecIt. Live restaurant calling is disabled until enabled for a legally reviewed region. When enabled, a reviewed call uses only the Information Profile fields you approve; transcript display requires the applicable consent.

Optional nutrition, allergen, meal, calorie, and macro information supports planning and review. Chec Health is informational and is not medical advice. This data is not used for advertising.

When you attach a photo to a chat, ChecIt sends the prepared image and your prompt to OpenAI to answer that request. Preparing the image reduces its size and removes embedded metadata. Chat attachment image bytes are not saved in ChecIt conversation history; the text you send and Chec's response follow your conversation history choices. An unsent or retryable attachment remains temporarily in the current chat on your device until you remove it, finish sending, or leave or reset that chat.

Only send images you have permission to use. Avoid private documents and sensitive information. Provider processing and retention follow the applicable provider terms and our configured account settings; we do not promise zero provider retention. A photo cannot reliably establish food safety, allergens, exact nutrition, prices, or availability.

Signed-in users can export a copy of their ChecIt data and delete their account from Settings. Deletion removes account data and owned media, subject to limited legally required transaction, security, moderation, and deletion-proof records. Merchant analytics suppress small reservation cohorts.

For help, email checitinfo@gmail.com.

Data may be processed in the United States or other regions where our providers operate. ChecIt is not directed at children under 13 or the applicable local digital-consent age.