Privacy
Last updated: 6 September 2026
PIN is built by Harshit Singh, a solo founder, as a personal-library app for iOS and Android. This page describes — in plain English — what data PIN collects, how it's used, and the third-party services involved. If anything here is unclear, email founder@catchandpin.app and we'll explain it directly.
Who's responsible
The data controller for PIN is Harshit Singh (the developer of PIN), reachable at founder@catchandpin.app. PIN is operated from India and serves users globally.
What we collect when you join the waitlist
When you sign up for early access on this site we store your email address, the platform you picked (iOS or Android), the page that referred you, your user-agent string, and a one-way hash of your IP (not the raw IP). We use these to send you your download link, prevent abuse of the signup form, and understand which channels people are arriving from.
What we collect inside the app
Your account: when you sign up, we store your email address, name (if you provide one), and a Clerk-managed authentication identity. Passwords are never stored in plain text — they live with Clerk, our authentication provider.
Your saves: every pin you create — its URL, title, extracted text or article body, your note, image (if any), and the collections you put it in — is stored on infrastructure we operate. Pins are scoped to your account. Sharing a collection makes its contents available to the people you invite or, for a public collection, anyone with its link.
Usage data: we record product analytics, such as screens visited and features used, to understand what is working. These events can be linked to your account identifier; they are not anonymous. We do not intentionally include the body of your saved content in product analytics events.
AI features — what gets sent where
AI processing is part of PIN's save pipeline, not only the Ask tab. Supported saves may be sent to content-extraction and AI services to extract text, analyse images or video, create summaries and topics, and generate search embeddings.
Pebble processes your questions, relevant saved content and conversation context. Studio processes saved interests, research and creator-profile information to prepare content packs. Voice references you select can guide writing. Notes that request an action may also trigger AI processing.
Our current model routing uses OpenAI, with DeepSeek available for selected functions. Web research can send queries to search providers. The data sent depends on the task and can include saved text, images, transcripts, your instructions and profile details. Not opening Ask does not disable automatic AI processing.
AI output can be inaccurate. Review it and the available sources before using or publishing it. For questions or requests about AI processing, contact founder@catchandpin.app.
When you save a link, we fetch it
PIN and its content-extraction services request URLs you save to retrieve available metadata, media and readable text. The destination receives these network requests. A saved URL can itself contain personal information or access tokens, so take care with private links.
Public collections (when you share)
For private collaboration, collection owners and administrators can invite members and manage access. Members can see the shared collection and its contents according to their permissions, including contributor information and comments.
If you publish a collection, anyone with the public link can view its titles, previews and source links without an account. The public web view does not display private pin notes or your other collections. We ask search engines not to index these pages, but cannot prevent someone with access from copying or redistributing content. Revoking access cannot recall copies already made.
Third-party services we use
PIN is built on top of several infrastructure providers. Each sees a narrow slice of data needed to perform its function. The list below is current as of the date at the top of this page; if we add, remove, or change providers in a way that affects how your data is handled, we'll update this list and email registered users.
- Clerk — authentication. Handles your email, password, sign-in sessions.
- Neon Postgres (US-East) — database. Stores your pins, collections, conversations.
- Vercel — hosts our backend and serves our marketing site. Sees request logs.
- Vercel Blob — storage for uploaded images, PDFs and generated media.
- OpenAI and DeepSeek — model providers for automatic analysis, Pebble, Studio and other AI features, depending on configuration.
- Tavily, Exa, NewsData and Serper — search and research providers used when configured for Pebble and Studio. They receive search queries required for the task.
- PostHog — product analytics, including feature events and account identifiers.
- Sentry — error tracking. Receives crash reports, may incidentally capture parts of your UI state if a crash happens. We do not feed pin content to it intentionally.
- Resend — transactional email. Receives your email address to deliver download links product updates, collection invitations and digest emails.
- Upstash Redis — rate limiting. Sees your user ID and request counts, not content.
- Langfuse — AI observability when enabled, including traces of AI operations and associated inputs or outputs.
- Content-extraction services — process supported saved URLs and media to return text, transcripts and metadata.
- AISeller / Docket — the website support widget is loaded from a third party. Messages or voice input you choose to provide are processed by that service.
- Notification delivery services — device tokens and notification payloads are processed to deliver enabled mobile notifications.
Data location and retention
PIN uses cloud infrastructure in the United States and service providers that may process data in other locations. Data can therefore be transferred outside your country. We retain account and library data to provide the service while your account exists.
Account deletion removes the primary account and associated library database records. Uploaded files, backups and records held by authentication, analytics or other service providers have separate deletion and retention paths. Do not assume all copies are erased immediately. Contact us to request deletion of remaining service-held data; see the account deletion page.
Cookies and local storage
Website: hosting and the third-party support widget receive technical information when they load. The widget may use browser storage and processes information you share with it. The interactive Pebble playground uses prepared examples and keeps its selections in page memory; it does not submit your choices to an AI service.
Mobile app: PIN stores authentication information, a local library snapshot and pending changes on your device. Sync can transmit changes while the app is open or during supported background activity. Locally available text can be used offline; AI features, remote media and syncing require a connection.
Emails can include account messages, collection invitations, requested access links and digest or product updates. Use the unsubscribe control in digest emails to stop them, or contact us about other non-essential email. Essential account or invitation messages may be handled separately. We do not sell your email address.
Your rights
You can, at any time:
- Access — see what we've stored about you by opening the app.
- Export — download a JSON file of every pin, note, and collection from Account → Export my data.
- Correct — edit any pin, note, or your profile inside the app.
- Delete — delete your account from Account → Delete account. This is irreversible.
- Object or restrict processing — email us if you want to opt out of analytics, AI processing, or any specific use of your data while keeping the account open.
If you're in the EU/UK and want to exercise GDPR rights, email us and we'll respond within 30 days. If you're in India, your rights under the DPDP Act are honored on the same timeline.
Children
PIN is not designed for children under 13. If you're under 13, please don't sign up. If we learn we have data on someone under 13, we'll delete it.
Security
We use industry-standard practices: HTTPS for all network calls, encryption at rest on managed-database storage, and short-lived session tokens. No system is perfectly secure though, and PIN is built by a solo founder, not a hardened security organization. If you store something on PIN that you would not be okay losing or having exposed, please reconsider.
Changes to this policy
If we make material changes to this privacy policy, we'll email registered users and update the “Last updated” date at the top. Minor wording or formatting changes won't trigger a notification.
Contact
Questions? Concerns? Want to exercise a right? Email founder@catchandpin.app. You'll hear back from a real person.