Privacy Policy

Last updated: September 6, 2026

IterArc is a personal life management app built by an independent developer in Budapest, Hungary. This policy explains exactly what data the app collects, how it is processed, where it is stored, and your rights regarding that data.

1. Data Controller

IterArc is operated by Barnabás Tóth (sole developer), Budapest, Hungary. For privacy inquiries, contact: [email protected]

2. What Data We Collect

Account Information

• Google Sign-In: Email address, display name, and profile picture URL from your Google account. We use Google OAuth 2.0 with scopes: openid, profile, email. We do not access your Google contacts, calendar, photos, or any other Google data.
• Display name: You choose a display name during onboarding. This can differ from your Google name.

Health & Body Data

• Profile information: Weight (kg), height (cm), age, biological sex, activity level — entered voluntarily during onboarding. Used to calculate calorie and protein targets.
• Weight measurements: Logged as habit completions when you weigh yourself. Stored as numeric values with timestamps.
• Step count: Read from Android Health Connect (read-only). We request only the READ_STEPS permission. We do not read heart rate, sleep, workouts, or any other health data. Step data is cached locally on your device and synced as habit completion values.
• Fasting data: Your eating window configuration (start/end hours) and fasting adherence status, derived from food entry timestamps.

Food & Nutrition Data

• Food photos: When you photograph a meal, the image is uploaded to our server for AI analysis. Photos are retained for 365 days and then permanently deleted by an automated daily cleanup job. The same 365 days applies to every account — there is no paid tier that keeps your photos longer or a free tier that drops them sooner. They are kept so that your food log, entry detail and calorie views can show the photo, and so you can edit an entry within its 7-day edit window. If you delete a food entry, its photo is removed on the next daily cleanup run rather than waiting out the 365 days.
• Parsed nutrition data: Calories, macronutrients (protein, carbs, fat, fiber), micronutrients (iron, calcium, omega-3, B12, vitamin D, potassium, magnesium, zinc), and Daily Dozen food category servings. This parsed data is retained.
• Food descriptions: Text descriptions and notes you add to food entries.
• Recipes: Recipe names, ingredients, nutritional values, and preparation notes you create.

Habit Data

• Habits: Names, schedules, behavior loop definitions (cue, craving, response, reward), identity statements, stacking relationships, reminder times.
• Completions: Timestamps, typed values (e.g., weight in kg, step count), skip/miss status.
• Streaks & statistics: Computed from completion history. Current streak, 30-day consistency, longest streak.

Household Data

• Shared within your household: Shopping list items, shared recipes, household settings (timezone, briefing times, quiet hours). All household members can see each other's habits, food entries, and household settings.
• Not shared: Your personal profile (weight, height, age) and push notification tokens are visible only to you.

Financial Data

• Bank connection: If you connect a bank account (e.g., Revolut), the connection runs through Enable Banking, a licensed PSD2 account information service provider (AISP) that acts as our processor for open-banking access. Through it we read transaction history, account balances, and account metadata. Access is read-only — neither we nor Enable Banking can move money on your behalf.
• Consent: Bank access requires explicit PSD2 consent via your bank's authentication flow. Consent is valid for 90 days and must be renewed.
• Transaction data: Merchant names, amounts, currencies, dates, and AI-assigned spending categories.

Device & Technical Data

• Push notification tokens: Firebase Cloud Messaging (FCM) device tokens, stored to deliver habit reminders and daily briefing notifications.
• On-device cache: Your sign-in session, the last-loaded screen data, and Health Connect step reads are cached on your device. The app has no offline write queue — every entry is sent to the server as you make it, and a failed save is reported to you rather than stored for later.

3. How We Process Your Data

AI Processing (Google Gemini)

Food photos and optional text notes are sent to Google's Gemini API, which analyzes the image to estimate nutritional content. Google processes this data according to its Gemini API terms and privacy policy. We do not send your name, email, or profile information — only the food photo, your notes, and your saved recipe names for matching purposes.

The AI Coach

When you talk to the in-app coach, your message, the recent messages in that conversation, and the parts of your own data the coach needs to answer (for example today's habits or food totals) are sent to Google's Gemini API. The coach runs on our server-side Google credential — there is no per-user API key, and your credentials are never sent to Google. Per-user daily and weekly usage limits are enforced on our server.

Transaction Categorization

When automatic pattern matching cannot categorize a bank transaction, the merchant name and description may be sent to Google's Gemini API for categorization. No account numbers, balances, or personally identifying financial information is sent.

Daily Briefings

Morning and evening briefing summaries are generated deterministically on the server from your data snapshots (habit completions, food totals, weight trends). No AI/LLM is used for briefing generation in the current version. Briefings are composed from template rules in the app.

4. Where Your Data Is Stored

5. Data Sharing

We do not sell, rent, or share your personal data with third parties for marketing purposes. Data is shared only with:

• Google (Gemini API): Food photos, coach conversations, and merchant names for AI analysis (processing only, under Google's Gemini API terms).
• Google/Firebase: Push notification tokens for delivery.
• Enable Banking: Your PSD2 consent and the bank access tokens issued against it, for as long as the consent lasts.
• Household members: Shared data as described in Section 2.

6. Data Retention

• Food photos: Retained 365 days for every account, then permanently deleted by an automated daily job. Deleting a food entry removes its photo on the next daily run.
• All other data: Retained until you delete your account.
• Bank consent: PSD2 consent expires after 90 days. Tokens are invalidated.
• AI processing logs: Token counts and latency metrics are logged internally for rate-limit monitoring. No personal content is stored in these logs.

7. Your Rights (GDPR)

Under the EU General Data Protection Regulation, you have the right to:

• Access: Request a copy of all data we hold about you.
• Rectification: Correct inaccurate data via the app's edit functions.
• Erasure: Request deletion of your account and all associated data.
• Data portability: Request your data in a machine-readable format.
• Withdraw consent: Revoke Health Connect permissions, disable push notifications, or disconnect bank accounts at any time via the app's settings.
• Object: Object to processing of your data.

To exercise any of these rights, contact [email protected].

8. Security

• All data in transit is encrypted via TLS/HTTPS.
• Database access is protected by Row-Level Security (RLS) policies — each user can only access their own household's data.
• No passwords are stored — authentication is via Google OAuth tokens managed by Supabase Auth.
• Food photos are stored in a private Supabase Storage bucket with signed URLs (not publicly accessible) for the 365-day retention window.

9. Children

IterArc is not intended for use by children under 16. We do not knowingly collect data from children.

10. Analytics & Tracking

IterArc does not use any third-party analytics, crash reporting, or advertising SDKs. The website (iterarc.com) does not use cookies or tracking scripts. We do not run Google Analytics, Firebase Analytics, Sentry, Mixpanel, or any equivalent service.

11. Changes to This Policy

We may update this policy when new features are added. The "last updated" date at the top reflects the most recent revision. Significant changes will be communicated via the app.

12. Contact

For any privacy-related questions or data subject requests:

• Email: [email protected]
• Developer: Barnabás Tóth, Budapest, Hungary