Privacy, without the fog.

KnownIn is a professional identity and career workspace operated by DevStudioLabs, a sole proprietorship in Mumbai, Maharashtra, India. This policy covers the website, authenticated workspace, hosted AI features and MCP service. External assistants, job portals, LinkedIn and other services have their own policies.

• Account and identity: email, sign-in information, optional photo, professional profile, contact links, skills, experience, projects, education, certifications and custom sections.
• Resumes: saved versions, template settings, job descriptions, fit reports, learning gaps, resume preferences and generated or assistant-uploaded PDF artifacts. A PDF can contain the personal details included in its selected profile/version.
• Opportunities and answers: Planned and submitted jobs, source links, role requirements, status, submission confirmations, notes, follow-up dates, company career-board sources and private application answers with disclosure preferences.
• Networking: contacts, LinkedIn URLs, identity sources and confirmation state, hiring excerpts and checked dates, conversation/job links, editable drafts, selected resumes, next actions, restrictions and user-reported send/reply history. Sent events may retain the message and resume label/hash available at confirmation.
• Connections and operations: API-key hashes and metadata, OAuth client/consent records and token hashes, profile-change history, usage counters, subscription/payment references, request/security logs and limited product analytics. Razorpay processes payment details; we store subscription state and references rather than full card details.

We use these records to authenticate your account, maintain your workspace, create and deliver resumes, track opportunities and conversations, serve an enabled public card, enforce usage/security controls and support billing. Hosted chat parsing and AI tailoring send the content needed for that operation to Google Gemini. Ordinary MCP storage operations do not all invoke KnownIn-hosted AI; your connected assistant may process information independently.

We do not sell workspace content or train our own models on it. We keep networking messages and research excerpts outside the general professional-profile history and product-event payloads. AI-provider and external-assistant handling is subject to their applicable terms and settings.

You can connect an assistant with an API key or OAuth. API keys can grant broad account access. OAuth grants the scopes shown at consent, which may include profiles, resumes, applications, private answers, sources and networking. Review that access before connecting a client. A saved answer marked “never” is blocked by the answer-resolution workflow; this is not a guarantee against a broadly authorized client reading other account data or retaining information it previously received.

Revoke API keys and OAuth connections in Settings to stop future authenticated access through those credentials. Revocation does not recall data already copied into an assistant, its memory, downloaded files or another service. Manage those copies through the relevant service.

Contacts and conversations are private account records, separate from your professional profile and public card. You or an authorized assistant supply them. KnownIn does not scrape LinkedIn, read its inbox, send messages, make connections or schedule automatic follow-ups. Copying a draft, opening LinkedIn or downloading a resume does not confirm a send or a job application.

Only save information you are entitled to use for a professional purpose. Avoid sensitive or unnecessary personal information about contacts. Respect do-not-contact restrictions. A profile lookup is not proof of hiring, and old hiring evidence is flagged for rechecking rather than treated as a confirmed vacancy.

• Google Firebase/Google Cloud: authentication, account databases, file storage and configured product analytics.
• Google Gemini: hosted AI parsing and tailoring. Google’s Gemini API terms describe provider data handling, including differences between service configurations.
• Vercel: application hosting, Web Analytics, Speed Insights, request diagnostics and the country signal used for regional pricing.
• Upstash: rate-limit counters and request identifiers where rate limiting is enabled.
• Razorpay: subscription/payment processing and related transaction records.
• Clients you connect: the AI assistant or application receives information within its granted access. Its provider is independently responsible for its own processing and retention.

Providers may process data outside your country. Applicable provider terms and safeguards govern that processing; this policy does not promise a particular data-residency location.

Your public card is optional. When enabled, the profile fields and sections selected for publication and its social-preview image can be accessed without login. Review the preview, including any contact details, before publishing. Networking, private answers and application records are not automatically added to that card.

Disabling a card prevents it from being served as an active public card, but search engines, recipients and other services may retain cached or downloaded copies. Resume downloads and signed artifact links are separate ways to share content; a recipient can keep a copy after downloading it.

Sign-in uses cookies and Firebase authentication storage. We use Firebase analytics, Vercel Web Analytics and Speed Insights for product usage, performance and diagnostics. Hosting and rate-limit services also handle technical request information such as network identifiers.

First- and latest-touch campaign labels can be stored in your browser for up to 30 days. These are limited to allowed attribution tokens, such as source, medium and campaign. Our campaign-event code does not include arbitrary query strings, email addresses or raw destination URLs as campaign attribution. Do not place sensitive information in URLs or campaign labels.

• Review and correct: update professional facts through Chat or an authorized assistant. Manage application and networking records in the workspace or through supported tools.
• Export: Settings → Account & Security provides an account JSON export including profile sections, saved career records, networking, connection metadata and PDF artifact metadata. Download PDF files separately. Secret credentials are not exported.
• Limit access: revoke keys/connections, change answer-disclosure preferences, disable public sharing or restrict a networking contact.
• Delete: request account deletion from Settings using the confirmation flow. You can also contact support about access, correction, deletion or a privacy complaint.

These controls do not limit any rights available under applicable law. Contact support@devstudiolabs.in for requests that the workspace cannot resolve.

Workspace records are retained while your account exists or until you remove supported records. Application audit history records the account/source, reason and previously reported submission details. Correcting a job to Planned clears active confirmation fields but preserves that history. Application audit history remains after deleting an individual job and is included in account export; account deletion removes it. Editing a draft does not rewrite a previously confirmed sent-message snapshot; that history remains until the associated history/contact/account is removed.

Successful account deletion removes the account’s tenant data, networking records, stored files, API keys, OAuth data, subscription record and authentication account. The service attempts to stop an active subscription before completing deletion. If that step or another deletion step fails, it reports an error so you can retry or contact support.

Deletion from KnownIn does not erase copies held by recipients or connected assistants. Independently held payment records, support correspondence and provider operational records may follow their own retention requirements and policies. We do not promise that every external record disappears immediately.

Account access uses server-side authentication and tenant checks. API keys and bearer tokens are stored as hashes where supported by the credential flow; raw credentials shown or issued to your client must be protected by you. We verify payment signatures and restrict database access. No security measure guarantees absolute protection. Do not send passwords, secrets or unnecessary sensitive information in chat, notes or drafts.

KnownIn is intended for adults aged 18 and over. It is not directed at children. Contact support if you believe a child has supplied personal information.

We update the date on this page when this policy changes and provide additional notice where required. Review it when enabling new features or connecting another assistant.

KnownIn is operated by DevStudioLabs (sole proprietorship), Mumbai, Maharashtra, India. For privacy questions, requests or complaints, email support@devstudiolabs.in.