eatstride.Your information, your choice.
PRIVACY POLICY · UPDATED OCTOBER 3, 2026
EatStride helps you track food, plan meals and follow your progress. This policy explains how EatStride handles information when you use eatstride.com.
What you enter and where it goes
Your profile may include your name, age, height, weight, activity level, optional sex used for target estimates, goals, food preferences and location you enter for restaurant searches. Your tracker holds food and movement logs, weight entries, notes, groceries, favorites, restaurant history and meal plans.
Apple Health companion (private testing)
When you explicitly connect the iPhone companion, you choose whether to upload steps, weight, and workouts to your signed-in EatStride account. The current test version uploads seven days of daily step totals and up to 30 days of weight and workout readings when you connect, update your sharing selection, or tap Sync now. If you enable automatic sync, the companion also uploads on opening and when iOS delivers background Health updates. Background timing is controlled by iOS. Health access and account upload consent are separate. We do not write to Apple Health.
Uploaded Health readings are encrypted in our server database and are not sent to AI providers or used for advertising. The last successful summary stays until it is replaced by a new sync, you disconnect, or you delete your account. Disconnecting removes these active server copies; it does not change Apple Health or manual food/activity logs. You can also revoke read access in the Health app. Revoking access there does not by itself delete a prior server copy.
Guest tracker data stays in your browser. Signed-in tracker data syncs to our server database unless you pause account sync. A browser copy remains for quick access. Pausing sync does not delete an existing cloud copy. Signing in does not automatically upload an existing guest history. Signing in uses Clerk and the identity provider you choose; connecting Gmail is a separate permission.
Optional Gmail receipt access
Google’s Gmail read-only permission grants access to read messages in your mailbox; Google does not offer a receipt-only permission. EatStride uses this access to search for food delivery and grocery receipts when you open the email-import flow or request a scan. It does not send, change or delete your email.
Normal scans search matching receipts from the last 30 days. The older-purchase search uses the product words you enter and searches up to 180 days. We retrieve matching message IDs, senders, subjects, dates and message contents to identify groceries, restaurants and past order items. The current integration searches supported senders including DoorDash, Uber Eats, Amazon and Whole Foods.
Matching email contents pass through our server and are returned to your browser for review. Receipt bodies are held temporarily for that request and review; the application does not save them to its account database. We store encrypted Google access and refresh tokens to maintain the connection. Imported restaurant names, order dates and item names, and groceries or meals you choose to save, become part of your tracker data. Receipt identifiers or fingerprints may be retained to prevent duplicate imports. Purchases are not automatically recorded as food eaten.
We do not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. Gmail receipt scanning and extraction do not send email contents to an AI service. Human access to Google data is limited to your explicit permission for particular data, security investigations, legal obligations, or other access permitted by Google’s Limited Use requirements.
EatStride’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Processing and transfers of Google data are limited to providing or improving the user-facing features described here, necessary security purposes, applicable legal obligations, or other transfers permitted by that policy.
Services used to provide features
Vercel hosts the app and its server functions. Our database infrastructure stores signed-in tracker records and encrypted connection credentials. Clerk handles account authentication. These service providers process information needed to operate their part of EatStride.
When you explicitly search the USDA food database, the food query is sent to USDA. Nearby restaurant search sends your entered city or postal code to mapping services, currently OpenStreetMap Nominatim and Overpass. Opening an external menu or map takes you to that provider. Do not put personal details into food or location search fields.
If enabled, optional AI meal interpretation sends the description you submit to OpenAI. Optional AI restaurant research sends your entered postal code and meal calorie/protein targets to OpenAI and its search service. These actions are labeled separately and are not required for ordinary logging. The app requests that AI responses not be stored through the response-storage feature; providers may still retain operational or safety records under their own policies. Raw Gmail receipts are not automatically attached to these requests.
Shared restaurant information
We cache public restaurant listings and published menu facts so users can reuse the same information without repeated lookups. Public records contain restaurant locations, source URLs, menu items and retrieval dates. Your selected restaurants, receipt history, pasted ordering links, food logs and targets are kept in your personal tracker and are not published to that catalog. Location matching uses your usual restaurant names in your browser; our mapping providers receive the area you enter, not your receipt history. Public menu pages are fetched without your delivery-account cookies.
Usage information and security
On public pages, we count page views, account-start clicks and guest-start clicks by day, page and a small set of traffic-source categories. These aggregate counters contain no account identifiers, cookies, food information, full referring URLs or search terms. They respect browser Do Not Track and Global Privacy Control signals. Short-lived in-memory request hashes limit abuse; they are not written to the analytics database. These counts measure actions, not unique visitors. We also use aggregate account totals to understand service growth.
Optional feature-use sharing records daily counts linked to your account, such as opening Today or logging food, unmatched lookups, corrections, unfinished logging attempts, and broad time-to-log ranges (under 30 seconds, 30–90 seconds, or over 90 seconds). These counts do not contain food names, calories, weight, receipt text or search terms. You can turn this off in Settings. Separate request-limit and AI-usage records help protect the service and control costs. Hosting and authentication providers may process technical records such as IP addresses, request times and browser information for operations and security.
We use HTTPS, account-based access checks and encrypted Gmail credentials. Browser storage and sign-in cookies support the app; browser copies are not a substitute for securing your device. Avoid using a shared browser for private tracker data. No service can promise absolute security.
Retention, export and deletion
Your saved tracker information remains until you remove it or delete your account. In Account → Settings & sync, you can export a browser backup or signed-in account report, and delete your account. Account deletion removes active tracker, connection, usage and research records, attempts to revoke Gmail access, and removes the sign-in account. A hashed deletion marker remains to prevent old devices from uploading deleted account data again.
Disconnect Gmail in Account → Connections to revoke access and remove saved connection credentials. Previously imported items stay in your tracker until you delete them. You can also revoke access from your Google Account connections. Clearing browser data removes that browser’s copy; it does not delete cloud data. Copies on other devices and downloaded backups must be removed separately. Infrastructure backups and security logs may persist under provider retention schedules; deletion from active records is not a promise of immediate erasure from every backup.
Questions and changes
Contact support@eatstride.com for privacy, access or deletion requests. We may need to verify account ownership before acting. We will update this page when practices change and request additional permission before using Google data for a new purpose that requires it.