Privacy Policy

1. Information We Collect

When you create an account, we collect your email address and any profile information you choose to provide. When you use Matteca, we collect the data you voluntarily log including tracker entries, goals, journal notes, and finance entries. That includes health and fitness data you log by hand, such as sleep, body weight, food, calories, water and workouts. We store it as account data, like everything else you log.

If you add images or files to your notes, or photos to a photo tracker, we store them in private storage tied to your account. Only you, and the people you share the page with, can open them, through links that expire within an hour (15 minutes on a public read-only link). Photos have their location and camera details removed on your device (in your browser, or in the iPhone app) before they are uploaded. They are not shared with any AI you connect: for a tracker photo, an AI can see only that a day has a photo, never the photo itself. Removing an image or file from a note, or deleting a tracker photo, does not yet delete the stored copy straight away; deleting your account removes all of them.

If you add photos to your dashboard's Photos card, we store them in private storage only you can open, with location and camera details removed before upload. An AI you connect never sees the photos themselves. Removing a photo or the card deletes it; deleting your account removes all of them.

When you edit a note we keep earlier copies of it: at most one every 10 minutes while you edit, plus one before you restore an older copy and one before a connected assistant changes it. For each note we keep the latest 50 copies or every copy from the last 90 days, whichever is more, up to 500. Copies are deleted when the note is deleted forever or your account is deleted. Templates you save stay with your account until you delete them.

On the website, dictation uses your browser's built-in speech recognition. Matteca never receives or stores that audio, but your browser may send it to its maker's speech service (for example Google in Chrome, Apple in Safari). Voice memos (website only) are saved as audio files in the same private storage as note images and files, opened only by you through short-lived links, and deleted with your account.

You can choose to log your average heart rate, calories, machine level and incline with a gym set. We store them with your gym sets and use them only to show your workouts and estimate calories. A connected assistant can see them if you give it the Gym & routines or Dashboard overview area.

A reminder can be linked to a note; its title (by default the note's title) appears in the push notification.

If you allow notifications in the iPhone app, it sends your device's push token to Matteca, which stores it with your account to deliver your reminders. Signing out usually removes it, and deleting your account always does. Expo (650 Industries) delivers the notifications: it receives that push token and the reminder's title.

The iPhone app uses the camera only when you choose to scan a food barcode or take a photo for a photo tracker, a note or your profile picture. If you unlock locked notes with Face ID, iOS checks your face on the device; Matteca never receives your Face ID data.

The iPhone app also checks Expo for app updates. Expo receives the install's update client ID and its IP address.

We record when you sign in. On the website we also collect basic usage data such as device type and browser type to improve the service (see section 7). The iPhone app sends no analytics. Beyond what you enter, it sends us only your push token (if you allow notifications) and the device details in a bug report you choose to send.

You can submit a feature request without an account. When you do, we store the text you type and a random identifier saved in your browser, or on your device in the iPhone app (used only to stop the same browser or device starring a request more than once). We do not link a feature request to your name, email address, or IP address.

2. How We Use Your Information

Your information is used to:

• Provide and maintain the Matteca service
• Calculate your daily scores, streaks, and analytics
• Process your subscription payments through our payment provider
• Send you important service-related communications
• Improve and develop new features

3. Third-Party Integrations

Connections to outside services (the work tools Notion, Jira and Asana, and Google Calendar) are paused. You cannot connect a new one, and while they are paused we do not read, sync or send anything through an existing connection.

If you connected one of these before the pause, that connection and its access token are still stored, encrypted, with your account, so it can work again if we switch connections back on. They are deleted when you disconnect the service (once connections are back) or delete your account. To have them deleted sooner, email support@matteca.com.

When connections are on, a work tool connection is read-only and reads only your work activity: task completions, status changes, and time logged. It does not access your files, messages, or any data beyond work activity events. A Google Calendar connection reads your calendar events and adds or updates the events you choose to sync from Matteca. Disconnecting asks the service to revoke our access and deletes the stored connection and its access token.

When you search for a food or scan a barcode, our server looks it up in USDA FoodData Central and Open Food Facts (and Nutritionix, when we have it switched on). It sends only the search text or the barcode, never your name, email or account.

If you sign in with Apple or Google, that company confirms who you are and shares your name and email address with us, under its own privacy policy. In the iPhone app, Google's sign-in software declares that it may also collect device and usage data for Google's own analytics.

4. Data Storage and Security

Your data is stored securely on Supabase (powered by PostgreSQL) with row-level security policies ensuring you can only access your own data. Our website, and the server the iPhone app talks to, are hosted on Vercel (Vercel Inc.), which handles your requests on our behalf. All data is transmitted over HTTPS. We do not sell, rent, or share your personal data with third parties for marketing purposes.

If you lock notes with a PIN, we store only a salted one-way hash of it, never the PIN itself, and a count of wrong attempts to slow down guessing. Unlocking sets a strictly necessary cookie that lasts 10 minutes. Locked notes are not encrypted: they are hidden in the app until you enter your PIN, left out of search, and never shown to or changed by an assistant you connect.

When you share a page, the Matteca users you invite can read it, and edit it if you give them edit access. Anyone with a read-only link can read the page without an account. You can turn a link off or remove a person at any time, and they can no longer open the page from then on. Files on a shared page open through links that expire within an hour for people you invite, and within 15 minutes on a read-only link, so a file someone already opened can stay reachable for that long. People you invite see your name; only you see their email. While a page is open, your edits and your cursor are sent to the other people on it through Supabase Realtime. Pages you open are also kept on your device so you can keep writing offline, and they sync when you reconnect. We clear that copy on a device when you sign out there, lock or delete the page, and after you lose access to it, the next time you open Notes online on that device. A copy with changes that have not synced yet stays on that device until they do. Deleting your account, or a session that simply expires, does not clear the copies on your other devices: sign out on each device, or clear that site's data in its browser. If two devices change the same part of a page offline, we keep both versions and flag it. Locking a page turns its share link off. Deleting your account deletes your pages, links and invites.

5. Payments

When you buy a subscription, your payment is processed by Paddle.com Market Limited ("Paddle"), which acts as the Merchant of Record and authorised reseller for the purchase. Paddle collects and processes the information needed to complete and manage your transaction, such as your name, email address, billing address, and payment details. Paddle handles this data as an independent controller under its own privacy notice.

Matteca does not store your full payment card details. We receive only limited transaction data from Paddle (such as your subscription status and the email used) so we can manage your account access. See our Refund Policy for how refunds are handled.

6. Data Retention and Deletion

Your data is retained as long as your account is active. You can delete your account and all associated data yourself at any time, from Settings in the web app or, in the iPhone app, from Settings, then Delete account (it is also in the menu under your name, and on your Profile). Deletion is immediate and permanent: your login, every tracker entry, and every uploaded image and file are removed, and there is no undo and no backup to restore from. If you cannot reach the app, email support@matteca.com and we will process the request within 30 days.

7. Cookies and Analytics

We use essential cookies for authentication and session management. These are always active because the service cannot function without them.

One more strictly necessary cookie, matteca_notes_unlock, is set only when you unlock notes you have locked with a PIN, and lasts 10 minutes.

On the website only, we also use PostHog (PostHog Inc.), a third-party product analytics processor, to help us understand how Matteca is used and to fix bugs. Data sent to PostHog is processed and stored in the United States. Through PostHog we may collect:

• Usage and interaction events (pages visited, buttons clicked, features used)
• Device and browser information, and an approximate location derived from your IP address
• Session recordings (a visual replay of how you interact with the app), captured for a sample of sessions. Everything you type into a form field is masked automatically. On top of that, sensitive figures shown on screen - weight, calorie/macro numbers, food log details, finance amounts (income, spend, recurring income), sleep times/hours, and workout heart rate, distance, time, pace, level and incline - are blacked out, along with free-text personal areas such as your journal/notepad entries and profile details (name, email). None of this is ever legible on the replay
• Error, crash, and diagnostic reports, used to identify and fix bugs

This analytics tracking uses cookies and local storage and only runs if you accept it in our cookie consent banner. You can decline it there, and you can change your choice at any time by clearing your site data and revisiting the banner. We do not sell this data, and it is retained only as long as needed for the purposes described above. A small number of internal team accounts are excluded from this tracking entirely.

Our landing page displays a Product Hunt launch badge. The badge image is loaded directly from Product Hunt (api.producthunt.com, operated by Product Hunt Inc. in the United States), so every visit to the landing page makes a request to their servers before you have made any cookie choice. That request carries your IP address, your browser's user agent, and the address of the page you are on. We do not receive that information, and we do not use the badge to identify or track you; Product Hunt handles it under its own privacy policy. The badge sets no cookie on our site. The same is true of the web font the landing page loads from Google Fonts (fonts.googleapis.com): it is a request to Google that carries your IP address, user agent and referring page, and nothing more.

If you star a feature request, we save a random identifier in your browser's local storage (or on your device in the iPhone app) so your stars are remembered on that device. It is anonymous and is not linked to your identity.

On the website, if a save fails (usually because you went offline), we keep what you typed in your browser's storage so you don't lose it, and we keep the change itself so we can send it when you're back online. Both stay on your device, are never sent to us except as the save you were already making, and are cleared as soon as the save succeeds or you discard it. We don't keep passwords, card details, or anything you type into a payment field this way.

8. Bug Reports

If you report a bug, using the bug icon in the top bar, the link on onboarding, or the right-click menu, we receive your description plus diagnostic context: your device and browser, the page you were viewing, the time, and the last few error messages the app logged. A screenshot is included only if you add one yourself, and you choose the area it captures. If you have accepted analytics cookies, the report may also include a link to your PostHog session recording so we can see exactly what happened. This information is used only to investigate and fix the bug you reported, is visible only to the Matteca team, and is retained only as long as needed to resolve it.

In the iPhone app, a bug report carries your description, the screen you were on, a screenshot only if you add one, and your iOS version, app version, screen size and the time. It has no session recording.

9. AI Access (connecting your own AI)

Matteca lets you connect your own AI account - such as Claude or ChatGPT - so that AI can read and change your Matteca data on your behalf. This is entirely optional and is off unless you set it up yourself.

If you connect an AI, your Matteca data is sent to that AI provider. When your AI reads or changes something in Matteca, the data involved leaves our systems and is transmitted to the company that operates that AI (for example Anthropic for Claude, or OpenAI for ChatGPT). Once it reaches them, it is governed by their privacy policy and terms, not ours. We do not control how they use, store, train on, or retain it. You should read the privacy policy of any AI you connect before connecting it.

You choose how much access to give. You can grant read-only access, or allow the AI to make changes, and you can narrow that to specific areas of the app. Some things are never available to a connected AI, regardless of what you allow: your password, your email address, your subscription and billing, deleting your account, submitting bug reports or feedback, connecting or disconnecting other apps, and uploading files.

To let you see and undo what your AI does, we keep an AI activity log for 30 days. Each entry records which connection acted, what it did, and a copy of the affected data as it was immediately beforehand so the change can be reversed. That copy can include the same personal information as the record it relates to - for example food, weight, sleep, finance or journal entries. It is stored with the same protections as the rest of your data, is visible only to you, and is deleted automatically after 30 days.

You can revoke any connected AI at any time from Settings, which immediately ends its access. Revoking does not retrieve data that was already sent to that AI provider.

10. AI Memory

If you connect an AI, it can save notes about you so it remembers useful context next time - your goals, your habits, what you are working toward, or anything else it judges worth keeping. This is what we call AI Memory. New accounts start with it off. You can turn it on, and off again, at any time from Settings.

If you signed up before 26 September 2026, it was switched on for you during setup. We should have asked, and we did not - the setup flow turned it on without putting the choice in front of you. We have changed that, so accounts created after that date start with it off. We have not switched it off on your behalf, because for anyone already relying on it that would quietly break something that was working. So the choice is yours: the switch is in Settings under AI Memory, turning it off takes one tap, and any notes already saved can be deleted.

What gets saved is decided by the AI, not by us. It records what it thinks is relevant, which can include personal details you mentioned in conversation rather than only things you tracked in Matteca. You can see everything that has been saved, edit any of it, and delete individual notes or all of them, from Settings. Memories are kept until you delete them - they do not expire on their own.

Memories are shared between every AI you connect. A note saved by one AI can be read by another you connect later. They are also sent to whichever AI reads them, which means they leave our systems and reach that provider, exactly as described in section 9.

Memories are encrypted at rest, so a stolen copy of our database would not reveal them. Nothing in Matteca shows your memories to us, and we do not read them. To be straightforward with you about the limit of that: because Matteca has to decrypt a memory in order to hand it to your AI, this is not a system where it would be technically impossible for us to access them. We are telling you what we do and do not do, not claiming a guarantee we cannot make.

Your memories are never sent to a model provider by us. Matteca has no AI assistant of its own: the only way a memory leaves Matteca is when your own AI, connected through AI Access, asks for it, and then it goes to whichever assistant you connected.

11. Changes to This Policy

We may update this privacy policy from time to time. We will notify you of significant changes by posting a notice on the service. Continued use of Matteca after changes constitutes acceptance of the updated policy.

12. Contact

Matteca is operated by Muhammad Ali Raza, a sole proprietor. If you have questions about this privacy policy, contact us at support@matteca.com.