resaw (operated by Tanmay Patel, Mumbai, India). Last updated: October 24, 2026.
This Privacy Policy explains how resaw ("we," "us," or the "App") collects, uses, and protects information when you use our mobile application and connected services. By using resaw, you agree to this Policy.
1. Who we are
resaw is a personal save-and-organize application. It lets you save links, images, documents, and notes, and helps you organize, summarize, and rediscover them. resaw is operated by Tanmay Patel, an individual based in Mumbai, India. Contact: hello@resaw.app.
2. Information we collect
Account information. When you sign in with Apple or Google, we receive your name, email address, profile photo (if provided by that account), and a user identifier to create and secure your account. Sign in with Apple and Google Sign-In are the only supported ways to create an account.
Content you save. The links, text notes, images, documents, captions, and titles you save, together with metadata we derive from them, such as tags, summaries, categories, and locations.
Content fetched from links. When you save a link, we retrieve publicly available information and media from the source page (for example, Instagram, YouTube, or TikTok) to generate previews, summaries, and step-by-step views.
Instagram data export you import. If you use the Import from Instagram feature, you select a saved_posts file from a data export you requested from Instagram yourself. We read the post links, captions, hashtags, and save dates it contains and store them as items in your account. We do not connect to your Instagram account directly and have no access to anything beyond what is contained in the file you provide.
Location. We extract place names from content you save and look them up on our servers to display them on a map. If you grant location permission, your device location is used on your device to show your position on that map and to surface nearby saved places. It is not sent to our servers, stored, or used to track you.
Usage and diagnostics. Basic interaction events, such as when you open or revisit a saved item, recorded against your account to improve the product, together with crash and error reports to keep the app stable.
Product analytics. We record what happens in the app: which screens you open, whether a save or an import finished, which version you are running, and when something fails. These events are processed for us by PostHog on its European servers. They are sent from our own servers rather than by a tracker inside the app, and each one carries an anonymous identifier derived from your account, the app version and the action taken. They never carry your name, your email address, your device identifier, your IP address, your location, or the content of your saves. Any text that could contain a link or an address, such as an error message, is replaced before it is sent. Write to hello@resaw.app and we will exclude you and delete everything we hold about you there.
Subscription status. The app identifies you to our subscription infrastructure provider, RevenueCat, by your resaw account identifier, never by your name or email address. RevenueCat processes your purchase data under that identifier, and the app also tells it when the upgrade screen is shown. If you buy resaw Premium, we receive your purchase and entitlement status through the app stores and RevenueCat. We do not receive your full payment card details.
Device information. To apply the one-device limit of the free plan, resaw stores a random identifier created on your device and your device's model name (for example "iPhone 17 Pro"). It never reads the name you gave your device. The identifier is kept in your iPhone's keychain, and our servers keep it with the model name, the platform, the app version, and when the device was first and last used, for your 10 most recently used devices. This is recorded on every plan, so the right device stays active if a subscription ends.
Notification tokens. A device push token, if you enable notifications.
Ideas, problems and feedback you send. When you suggest an idea, report a problem or vote for a card under What's coming, we keep what you wrote and your votes in your account; each vote is also recorded on that card with your plan and how many saves you have. Ideas, problems and feedback you send from the app are emailed to our own inbox through Brevo (Section 6), with your email address so we can reply, and stay in that inbox after you delete your account.
Movies and series. When resaw recognises a movie or series in something you saved, it keeps the title it found and where that title can be watched in your country. If you use the Watchlist, it also keeps which titles you marked as watched and your thumbs up or down; those stay in your account and are never shared.
We do not collect contacts, browsing history, health data, or advertising identifiers, and the app does not contain advertising SDKs. Usage analytics are sent from our servers, not by a tracker inside the app; the exceptions are the notice sent to RevenueCat when the upgrade screen is shown (see Subscription status) and the Mixpanel library described next. The app still carries the Mixpanel library from an earlier release. It sends nothing unless you turn on Settings > Share Usage Data, which is off until you turn it on, and we will remove it in a later update.
3. How we use your information
To provide the core service: saving, organizing, summarizing, and resurfacing your content.
To power features such as automatic summaries, search, chat with your saved content, recommendations, and map or trip features.
To process subscriptions and enforce plan limits: the free plan's save and one-device limits, and each plan's monthly AI credits. For each AI feature you use, we record which feature it was, how much AI work it took and the credits it cost; that record never includes what you asked or what the AI answered.
To send notifications you have enabled.
To maintain security, prevent abuse, and diagnose and fix problems.
We do not sell your personal data, we do not share it with data brokers, and we do not use your content for advertising or to track you across other companies' apps and websites.
4. AI processing
resaw's organizing, summarizing, search, and chat features rely on third-party AI providers. To generate titles, tags, summaries, embeddings, chat answers, and structured views such as cook-along steps, the content you save (including links and the page content fetched from them, your notes, your captions, images you save, and the questions you ask) is sent to those providers for analysis. The providers we currently use are Google, through the Gemini API, and Groq, both accessed from our backend over their respective APIs. We do not train any models on your content ourselves. We access the Gemini API through a billed Google Cloud account, which under Google's Gemini API Additional Terms of Service qualifies as a Paid Service, meaning Google does not use your prompts or responses to improve or train its models. Groq's standard Services Agreement likewise prohibits it from using API inputs or outputs to train or fine-tune any of its models without our explicit separate permission, which we have not given. If our arrangement with a provider changes in a way that affects this, or if we change providers, we will update this Policy accordingly.
5. Optional messaging integrations
You can choose to save to resaw by sending a message to resaw's business account on WhatsApp, or to resaw's bot on Telegram. This is strictly opt-in. Nothing is connected until you open Settings, then Connected Accounts, and send the one-time code the app gives you to our account or bot. Saving by Instagram message is not offered: we test it with our own accounts only, and we will update this Policy before it is offered to anyone else.
What we receive. Only the messages you send to resaw's business account or bot: the links, text, forwarded posts and files you choose to send. Each message arrives with the ID of the account that sent it and, depending on the app, its phone number, username or profile name. We cannot read your other chats or your contacts.
What we store. What is needed to tie your messaging account to your resaw account (your WhatsApp user ID or phone number, or your Telegram user ID), together with the items you send. Those are saved to your account and then treated like anything else you save (Sections 2 to 4). When you connect a messaging account, resaw also keeps the name of that account (your Telegram username, your Telegram first name if you have no username, or your WhatsApp number, or your WhatsApp profile name when WhatsApp does not share your number) so that Settings can show you which account is connected; it is deleted when you disconnect that account or delete your resaw account.
Short-lived records. To stop anyone guessing a linking code, we keep a count of the wrong codes sent from a number or account; it expires after an hour and is deleted within about a day. So that a message delivered to us twice is handled once, we keep a note that a message was handled, under a one-way fingerprint of the message's ID and with none of its content; it expires after a day and is deleted within about a day after that.
If you have not connected. If you write to resaw's business account or bot without connecting, our servers keep nothing of what you send, and we do not look up your profile. Only the short-lived records above are kept: the note that a message was handled and, if what you sent was a six-digit number, the count of codes.
Replies. We reply only to messages you send us, with a short fixed text such as "Saved to resaw". We never message you first, never post on your behalf, and never put anything from your resaw account into a reply.
Disconnecting. You can disconnect at any time in Settings, then Connected Accounts. That removes the messaging account's ID and name from your resaw account, and nothing it sends is saved from then on. Items you already saved stay in your account until you delete them. Deleting your resaw account removes the connection, the items and the files you sent (Section 9).
The messages themselves stay in the chat, on the servers of WhatsApp or Telegram, in your own chat history, which you control. Messages on WhatsApp reach us through Meta Platforms' WhatsApp Business Platform, and our use of it is subject to the Meta Platform Terms and Developer Policies. Messages on Telegram reach us through Telegram's Bot API.
6. Service providers we share data with
We share data with the following service providers, strictly to operate the service:
Google Firebase and Google Cloud. Authentication, database (Firestore), file storage, serverless functions, web hosting, and geocoding and maps.
Google, through the Gemini API. AI analysis of the content you save. See Section 4.
Groq. AI analysis of the content you save, as a fallback provider. See Section 4.
A content-extraction service we operate, and the YouTube Data API. Retrieving publicly available content and video metadata from the links you save.
Apple (Sign in with Apple) and Google (Google Sign-In). Account authentication.
Meta Platforms (WhatsApp Business Platform). Delivers the messages people send to resaw's WhatsApp business account, and our replies. See Section 5.
Telegram. Delivers the messages and files people send to resaw's Telegram bot, and our replies. See Section 5.
RevenueCat and the Apple App Store. Subscription infrastructure and billing for resaw Premium. See Section 2.
Sentry. Crash and error diagnostics.
Microsoft Clarity. Website usage analytics and session replay, on resaw.app only. Not used in the app.
PostHog. Product analytics for the app, received from our servers and stored in the European Union. See Section 2.
Mixpanel. Opt-in app analytics, off unless you turn on Settings > Share Usage Data, stored in the European Union. When it is on, the app sends Mixpanel the usage events described in Section 2, linked to your account ID, with the country and city worked out from your connection (the IP address itself is not stored), and a recording of the screens you use with all text, images, web pages and maps hidden. Turning the switch off stops both. We will remove it from the app in a later update, and then delete the data held there.
Expo. Push notification delivery.
Brevo. Email delivery: the welcome email, reminders and the Android waiting list confirmation (your name and email address), and the ideas, problems and feedback you send from the app, which reach our own inbox (what you wrote and your email address, and for ideas and problems also your plan, how many saves you have, how long ago you signed up, and your app version). See Section 2.
Movie of the Night (Streaming Availability API). Finds where a movie or series in your saves can be watched. Our servers send it the title we recognised in a save, or a title you typed, and the country you watch in, never your account details or the save itself. Poster images on the Watch card and the Watchlist load directly from its servers, which see your device's IP address, as any website does.
We may also disclose information where required by law or to protect rights, safety, and security.
7. This website
Sections 1 to 6 describe the resaw app. This section covers resaw.app itself, which collects a small amount of separate information.
We use Google Analytics to count visits and see which pages people read, so we know which guides are worth writing more of. It records the pages viewed, approximate location derived from IP address, and general device and browser information. It is not connected to your resaw account, and we do not use it to identify anyone.
Every advertising feature is switched off. We do not run ads, we do not build advertising audiences, and we do not use this data to follow you across other websites.
We also use Microsoft Clarity to see how pages are actually used: pointer movement, clicks, scrolling, and a reconstruction of the page as it appeared. It sets its own cookies. We use it to find what confuses people, not to identify anyone, and it is never connected to your resaw account.
Because session recording stores data on your device, visitors in the EU, the EEA, the United Kingdom and Switzerland are asked first. Until you choose, Clarity does not load at all and Google Analytics measures without cookies, so nothing is stored. Choosing "No thanks" is remembered and keeps it that way. Elsewhere both run, and Google Analytics sets its own cookies to recognise a returning visit. You can opt out anywhere using Google's browser add-on, and we honour the Do Not Track setting by loading no analytics at all when it is switched on.
The app itself contains no advertising SDKs. Its product analytics are described in Section 2 and are sent by our servers, not by a tracker inside the app; the exceptions are the notice sent to RevenueCat when the upgrade screen is shown (see Subscription status) and the Mixpanel library, which sends nothing unless you turn on Share Usage Data.
8. Data retention
We keep your account and saved content until you delete it or delete your account. Diagnostic logs are generally retained for approximately 30 days before automatic deletion.
9. Your rights and data deletion
You can:
Delete individual items in the app at any time.
Disconnect a messaging account you connected, in Settings, then Connected Accounts, at any time. This removes that account's ID and name from your resaw account. See Section 5.
Delete your account and all associated data from inside the app. Open Settings, then Delete Account. This permanently removes your account, your saved items (including saves on the waiting list), your uploaded files (including files you sent by message), the data derived from them, any messaging account you connected (Section 5), and the device records described in Section 2; the random identifier stays in your iPhone's keychain but is no longer linked to any account. When you delete your account, we also ask RevenueCat to delete your record there. Deleting your account does not cancel a subscription billed by Apple; cancel that in your iPhone's Settings. Before deleting, the app asks why you are leaving; that answer is kept without your name, email or account identifier so we can improve resaw for the next person.
Or email hello@resaw.app with the subject "Delete my data." We will process verified deletion requests within 30 days.
Depending on your location, you may also have rights to access, correct, or export your data, or to object to certain processing. Contact us to exercise these rights.
10. Security
Your data is stored on Google Cloud infrastructure and protected by per-user access rules, so that only you, and our backend acting on your behalf, can access your content. We use industry-standard encryption in transit. No method of transmission or storage is completely secure, but we take reasonable measures to protect your information.
11. Children
resaw is not directed to children under 13, or the minimum age required in your country, and we do not knowingly collect data from them.
12. International transfers
Your information may be processed in the United States and other countries where our service providers operate. We rely on appropriate contractual and technical safeguards for such transfers.
13. Grievance redressal (India)
In accordance with the Information Technology Act, 2000 and applicable rules made under it, the Grievance Officer for resaw is:
Tanmay Patel Email: hello@resaw.app Mumbai, Maharashtra, India
You may contact the Grievance Officer with any complaint or concern regarding this Policy or the handling of your personal data. We will acknowledge and seek to resolve valid complaints within the timelines prescribed by applicable law.
14. Changes to this Policy
We may update this Policy from time to time. We will post the updated version here and revise the "Last updated" date above.