Privacy policy
What CatchIt handles, why it is needed, and the choices you have.
Last updated 27 October 2026 · Pre-launch draft
1. About this policy
This policy describes the CatchIt marketing website at getcatchit.app and the current pre-release CatchIt apps. CatchIt provides a personal inbox for notes, links, images, and supported files. Contact hello@getcatchit.app with privacy questions.
The legal operator details, production service providers, processing locations, and retention periods will be finalized before the apps are publicly released.
2. The information you give us
The apps handle your account name, email address, password hash, verification status, and an optional profile photo. They store the notes, links, images, files, tags, and related metadata you choose to save, including creation and change times. Password recovery and verification use temporary codes.
If you email us, we receive your email address and the information you include. Please do not send passwords, verification codes, or sensitive saved content in support emails.
3. Website visits and device storage
This marketing site uses Google Analytics only if you choose Allow analytics. It measures page visits, basic device and browser information, traffic sources and campaign labels, and clicks on download, store, contact, and example-filter controls. We do not send the example search text to Google. Advertising features and Google signals are disabled. Google receives connection information when its tag loads. Assets and fonts are served from the same site. Cloudflare delivers the website and may process connection and security information, such as IP addresses and request details, to serve pages and protect its network.
The apps keep account-specific saved items, drafts, and pending uploads on your device so you can use and recover captures. Native session tokens use platform secure storage. The local content database is not separately encrypted by CatchIt. Browser account pages, if used, rely on session and security cookies. See the cookie policy.
4. How information is used
Account and saved-content data are used to provide sign-in, save and retrieve your captures, synchronize supported changes, deliver verification or recovery messages, manage storage, prevent abuse, and respond to support requests.
For links saved to cloud sync, CatchIt's server may request the saved URL and a page-provided image to create a preview. Those websites receive the requested URL and the server's connection information. CatchIt does not send your account identity or browser cookies. Page titles, descriptions, website names, and small thumbnails are stored with your private save and can be searched or viewed offline after syncing. Device-only guest links are not fetched for previews until you choose to move them to an account.
The current apps do not send saved content to an AI or OCR provider. CatchIt does not include advertising or sell saved content. Any new processing that changes this policy will be described before it is introduced.
5. Access and service providers
Access to captures and private files is restricted to the authenticated account. This is server-side access control, not end-to-end encryption: authorized server operators may be able to access stored data. Operational providers may process information to deliver hosting, file storage, account email, security, or support.
The marketing website is hosted by Cloudflare and uses optional Google Analytics. The mobile apps use optional PostHog analytics hosted in the United States. When you enable Help improve CatchIt, the app sends anonymous usage events, basic app/device information, and a random analytics identifier. CatchIt does not send account names, emails, saved notes, links, files, filenames, tags, search text, or screen recordings to PostHog. Analytics identifiers rotate at account/library changes; they are not linked to your account. Analytics providers may process connection information when receiving requests. A final list of app hosting, storage, and email providers and relevant international processing information will be added before public release. Information may also be disclosed where a valid legal obligation requires it.
6. Retention and deletion
Saved content remains in your account until you delete it or delete the account. Deleting an account removes its active account records, associated captures and tags, and revokes access tokens. Attachment and profile-photo removal is queued; storage cleanup is not instantaneous. Deletion removes access to the affected files before the cleanup job completes.
The production backup lifecycle, security-log retention, support-email retention, and a maximum cleanup period are still being finalized. This draft does not promise immediate removal from every backup or device. Content you have downloaded or copied elsewhere remains under your control.
See account and data deletion for in-app steps and an email request option that does not require the app.
7. Your choices
You can edit your profile, remove an optional profile photo, delete individual captures, or delete your account. Website analytics starts only after you allow it; use Analytics settings in the footer to change your choice. Mobile analytics is off until you enable Help improve CatchIt during onboarding or in You. Turning analytics off stops future collection; it does not erase events already received by the provider. Device permissions control access to files and photos you select. Depending on applicable law, you may have rights to access, correct, receive a copy of, restrict, object to processing of, or delete personal information.
Send requests to hello@getcatchit.app. We may need to verify account ownership before acting. We will explain any applicable retention requirement or limitation. You may also have a right to contact your local data-protection authority.
8. Children and policy changes
CatchIt is not designed specifically for children. Eligibility and regional requirements will be set out in the final release terms. Contact us if you believe a child has provided personal information inappropriately.
We will update this page as the service develops. The date shown above identifies the latest revision; material changes will be communicated through an appropriate service channel.