# Privacy policy
Effective November 13, 2026
Looking for a plain-language overview of what noticed can see? [Read the Privacy & data FAQ](/help#privacy-and-data).
## 1. Who we are
noticed Inc. ("we", "us", "our") operates noticed, your personal networking agent. noticed helps you find relevant people, understand your connections, and prepare for conversations and follow-ups. This policy explains how we collect, use, and protect your information across our website, apps, and connected services.
## 2. Information we collect
We collect information that you provide directly or authorize us to access:
- **Account information** — name, email address, and, where supplied, profile picture from your sign-in provider (Apple, GitHub, Google, Microsoft, or LinkedIn). Sign in with Apple may provide a private relay email address instead of your personal address and does not provide a profile picture.
- **Connected source data** — relationship data from services you choose to connect or authorize:
- **LinkedIn** — Connections, Profile, DM interaction metadata. Profile information and connections may also come from an uploaded LinkedIn data export archive. Message text isn’t collected by the extension.
- **X** — Profiles, Mutual follows, DM and reply metadata. Post and DM text aren’t stored.
- **Google Calendar** — Calendar events, Contacts. This data is accessed via the Google API with your explicit consent. Gmail data isn’t part of this connection.
- **Microsoft Outlook** — Contacts, Calendar, Email headers. This includes contact names and email addresses; calendar subjects, times, organizers, and attendees; and mail header metadata such as subjects, participants, timestamps, conversation identifiers, and whether an attachment exists. We do not read or store email bodies, previews, attachment contents, or extended properties, and we cannot send mail or modify your Outlook data.
- **WhatsApp** — Contacts, Interaction metadata. Message bodies, attachments, and media aren’t stored.
- **Telegram** — Contacts, Direct chats, Small-group metadata. Relationship import doesn’t store message bodies, media, channels, or Secret Chats.
- **GitHub** — Public repositories, Contributions, Collaborator graph. This data is accessed via the GitHub API. Private repositories and private gists aren’t imported.
- **Gmail** — Contacts, Email headers, Message labels/categories. Message labels/categories are stored to help filter bulk email. Email bodies and attachment contents aren’t stored.
- **Slack** — People, DM metadata, Group DM metadata. This includes workspace member identity plus direct-message and group-direct-message participant and timing metadata, such as sender identifiers, timestamps, thread identifiers, and reply counts. Relationship import does not store Slack message text, files, reactions, or public-channel history, and it never posts as you.
- **Granola** — Meetings, Notes, Transcripts. Meeting notes and transcripts are stored.
- **Wispr Flow** — Meetings, Attendees, AI summaries. noticed imports minimum-necessary meeting metadata, attendee identities, AI summaries, calendar/conference provenance, and access/deletion state through Wispr Flow’s read-only MCP connection. Full transcripts, dictation history, private Thoughts, and Notetaker chat are excluded.
- **Attio** — People, Companies, Activity metadata. Bodies, transcripts, attachments, and files aren’t stored.
- **HubSpot** — Contacts, Companies, Deals, Engagement metadata. Bodies, recordings, attachments, and media aren’t stored.
- **Slack Agent messages** — Messages you intentionally send to or mention the noticed Agent are processed and retained as conversation history so the Agent can reply and preserve context. Slack data is not used to train, fine-tune, or improve AI models.
- **Telegram Agent messages** — Messages you intentionally send to the noticed Agent are processed and retained as conversation history so the Agent can reply and preserve context.
- **Chats and submitted content** — messages, replies, notes, attachments, and photos or other captures you submit are stored to provide your conversation history, relationship context, and requested features.
- **Notifications** — account-linked device identifiers, push notification tokens, permission status, and delivery information let us send and manage notifications.
- **Optional app permissions** — camera and photo access support captures you choose to submit. With location permission, the app uses your device location and the platform's geocoding services (Apple on iOS, Google on Android) to identify the city and country for an encounter; the encounter sent to noticed includes that city and country rather than coordinates. Dictation uses the device's speech recognition and microphone access to turn speech into text. Recognition may involve Apple's or Google's servers; the transcript becomes submitted content when you send it.
- **App analytics** — we use PostHog for account-linked app lifecycle events and sign-in provider and outcome events. The iOS and Android apps disable session replay, automatic screen and touch tracking, network and log capture, and automatic exception capture.
- **App ad measurement** — the iOS and Android apps use Meta's app events SDK to measure whether Meta ads led to an install or a new account. It reports app launches and sessions and, once, that a new account was created with its sign-up method (email, Apple, Google or Outlook), together with standard device and network information such as device model, OS version and IP address. It never sends your name, email, account ID, chats, contacts or network. The iOS app asks for Apple's tracking permission after you sign in; Meta receives your device's advertising identifier only if you allow it. Android has no per-app tracking prompt: the Android app sends Meta your advertising ID unless you have deleted your advertising ID in Android settings. Resetting it only replaces it with a new one.
- **Usage data** — interactions with the platform, feature usage, and technical information such as browser type and IP address.
## 3. How we use your information
- Provide, operate, and improve the noticed platform and its features.
- Build and maintain your professional network graph and profile.
- Surface relevant connections, introductions, and networking opportunities.
- Send professional outreach you approve from your connected email account.
- Display calendar context to help you prepare for upcoming meetings.
- Match your contacts across platforms to create a unified view of your network.
- Answer messages you send to the noticed Agent through connected chat services.
- Send you transactional messages related to your account and connected services.
- Detect, investigate, and prevent abuse or unauthorized access.
## 4. Google API data
Our use and transfer of information received from Google APIs adheres to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. Specifically:
- We use Google user data **solely to provide and improve the user-facing features of noticed** — building and maintaining your network graph, matching your contacts across platforms, displaying calendar context to help you prepare for meetings, and sending outreach you explicitly approve from your connected account. We do not use Google user data for any other purpose.
- We only use Google data for the purposes described in this policy and as displayed in the consent screen.
- We do not sell Google user data to third parties.
- We do not use Google user data for advertising purposes.
- We do not use user data to train, fine-tune, or improve AI models, and we do not share it with AI providers for that purpose.
- We do not allow humans to read your Google data except where you provide explicit consent, where it is necessary for security purposes, to comply with law, or where the data is aggregated and anonymized.
## 5. Browser extension (noticed Relationships)
Our browser extension, **noticed Relationships**, imports your own first-degree LinkedIn connections into your noticed account. It is [open source](https://github.com/noticedso/relationships-extension) so you can verify exactly what it does.
- It reads **only your own connection list** — names, headlines, profile links and connection dates — and only when you click Connect or Scan. It never reads your messages or anyone else’s data.
- It reads your LinkedIn session cookie **in your browser only**, to authenticate the request as you. That value is used solely as the request’s security header and is never sent to noticed or stored.
- Imported connections go **only to your own noticed account**, over an encrypted connection, and are handled as described in the rest of this policy.
- The extension holds no password and no separate login — it uses your existing signed-in noticed session.
- We do not sell or share this data, or use it to train AI models.
## 6. Data sharing
We do not sell your personal information. We share data only in these circumstances:
- **Advertising measurement** — Meta receives the iOS ad-measurement events described above and processes them under its own terms to report and optimize noticed's Meta ads. You can withhold the advertising identifier by declining tracking in iOS Settings.
- **Service providers** — trusted third-party services that help us operate the platform (hosting, analytics, and AI processing). These providers process data only to provide the service on our behalf, are bound by confidentiality obligations, and may not use the data for their own purposes. Any Google user data they process is subject to the Limited Use requirements above. Vercel AI Gateway routes AI requests to model services. All of our AI providers operate under our Zero Data Retention policy, including providers used outside Vercel AI Gateway.
- **With your consent** — when you explicitly choose to share information, such as sending an introduction through the platform.
- **Legal requirements** — when required by law, court order, or governmental authority.
## 7. Data retention
We retain your information for as long as your account is active or as needed to provide you with the service. You can disconnect any provider at any time from your account settings, which removes our access to that provider's data. When you delete your account, we delete your personal data within 30 days, subject to the limited retention described below. Deletion removes your account and invalidates your noticed sessions. Cleanup at connected providers, analytics services, and file storage is processed separately and may complete asynchronously.
We retain limited records where needed for legal and billing obligations, to prevent reuse of revoked sign-in credentials, or to complete outstanding deletion and revocation work. These can include transaction records without an active account, restricted identifiers and timestamps, and cleanup references. Credentials needed for outstanding provider revocation remain encrypted until that work is confirmed. These records are restricted to those purposes and do not preserve an active account or login.
Deleting your personal account does not delete shared Team conversations or content still used by other participants. That shared content may remain available to them.
## 8. Data security
We use industry-standard security measures to protect your data, including encrypted connections (TLS), encrypted storage for OAuth tokens, and access controls. However, no method of transmission over the internet is 100% secure, and we cannot guarantee absolute security.
## 9. Your rights
Depending on your jurisdiction, you may have the right to:
- Access the personal data we hold about you.
- Request correction of inaccurate data.
- Request deletion of your data.
- Disconnect any connected provider and revoke our access to its data.
- Export your data in a portable format.
- Object to or restrict certain processing of your data.
In the iOS or Android app, open Settings, find Account, and choose Delete account to request permanent account deletion. During LinkedIn onboarding, the back button also offers Delete account. You can also exercise your rights by contacting us at [contact@noticed.so](mailto:contact@noticed.so).
## 10. Cookies
We use essential cookies required for authentication and session management. We do not use third-party advertising cookies or cross-site tracking cookies.
## 11. Children
noticed is not intended for use by anyone under the age of 16. We do not knowingly collect personal information from children.
## 12. Changes to this policy
We may update this policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the effective date. Your continued use of the platform after changes constitutes acceptance of the updated policy.
## 13. Contact
If you have questions about this privacy policy, contact us at [contact@noticed.so](mailto:contact@noticed.so).