Privacy Policy

ProfMe is developed and published by ArchByte Studio. ArchByte Studio is the trade name of Satish Rajnale, an individual sole proprietor in India, and is not a separate legal person. This policy covers personal information processed through ProfMe websites, desktop app, account and support flows. Feature availability and provider configuration can vary by release and account. Principal business address: Kalewadi, Pimpri, Pune 411017, India. Privacy contact: privacy@profme.in. Grievance Officer: Satish Rajnale, reachable at privacy@profme.in for privacy grievances and support@profme.in for product complaints.

Depending on features you use, ProfMe processes:

• account identifiers and profile/workspace information supplied through sign-in and account setup;
• sessions, imported source material, audio or screen-capture artifacts, transcripts, summaries, and professional-memory records you ask ProfMe to create;
• preferences, including recording and local-audio retention settings;
• support requests and attachments you submit;
• service, diagnostic, security, and error events generated by the app or infrastructure;
• policy version, acceptance time and method, and account export/deletion job status and evidence;
• billing/customer and transaction status if paid checkout is enabled for your account.

The particular fields and whether they are required depend on the feature and sign-in path. Do not submit passwords, payment-card details, sensitive personal data, or another person’s confidential information unless the feature requires it and you are authorised to do so. When paid checkout is available, payment details are entered through the checkout provider. ProfMe may receive customer, subscription, invoice, and transaction-status identifiers; it is not designed to collect full payment-card numbers or security codes.

We use information to authenticate you; provide capture/import, transcription, AI processing, memory, search, export, and deletion features; maintain your preferences; respond to support; protect users and the service; investigate failures and abuse; meet legal obligations; and administer billing if enabled. AI and speech providers process submitted content under their applicable terms and service settings. Their retention and model-training practices depend on the provider and configuration; ProfMe does not make a blanket no-training or zero-retention promise for every provider.

ProfMe does not automatically notify meeting participants or obtain their consent. Before recording or submitting information about other participants, you must give required notice and obtain any consent or authority required by law, workplace rules, and agreements. Stop capture if you cannot do so. The app’s start confirmation is a user attestation, not proof that participants were individually informed or consented.

Depending on the feature and configuration, information may be processed by Google Cloud (hosting and object storage), Clerk (authentication), Temporal (workflow orchestration), Google Gemini or OpenAI (AI processing), Deepgram where enabled (speech recognition), Sentry (diagnostics), Composio when you connect an integration, and Paddle when paid checkout is enabled. Different providers receive different data; for example, authentication and diagnostics do not necessarily receive meeting content. Provider settings, subprocessors, retention, and processing locations are governed by their applicable terms and can change. ProfMe may process information outside India and does not promise India-only storage or processing.

We may disclose information to comply with law, respond to a valid legal request, protect rights or safety, or handle a business transfer where lawful. ProfMe is not designed to sell personal information or use it for targeted advertising. This description does not cover a provider's independent processing under its own terms.

Some providers may process information outside India. Processing locations depend on the provider, feature, and configuration. ProfMe does not promise that information stays in India. Providers may use subprocessors and apply their own transfer safeguards and terms.

Retention depends on data type and feature. Local audio retention is controlled by desktop settings (30-day default in the current implementation). Cloud audio and video are deleted after successful processing once a durable transcript exists; failed object deletions are retried while the source artifact remains recorded. Full transcripts and Professional Memory remain available for the active account until the user requests deletion or deletes the account. Export download links expire after 10 minutes; export archives are scheduled for deletion after 7 days. The production GCS bucket has no configured lifecycle or soft-delete policy, so storage-level expiration and recoverability of deleted objects are not claimed. Database backups and point-in-time recovery use the current seven-day configuration. Account deletion is asynchronous and may leave limited legal/audit records; its complete production behavior has not been verified.

After an account-deletion request, active account data is queued for deletion. Some limited records may remain for legal compliance, security, fraud prevention, dispute handling, or evidence that a request was processed. Policy-acceptance and deletion-evidence records are retained separately; database backup copies follow the seven-day backup configuration, and third-party provider copies may take longer to expire or may require a separate provider-side deletion request. We do not promise immediate removal from backups or providers or a fixed overall deletion deadline. Production end-to-end deletion and provider-side deletion have not been verified. You may delete local recordings separately from your device. Export archives are temporary; download links expire after 10 minutes and archive cleanup is scheduled after 7 days, subject to production verification.

You can manage available recording preferences and request an export or account deletion in account settings. Export scope excludes data held only by connected services and local-only recordings not uploaded to ProfMe; available ProfMe session/artifact data, memory records, support information, and object-backed media may be included. Review an export for sensitive information before sharing it. Where applicable law provides, you may review personal information we hold, request correction or completion, and withdraw consent for processing that relies on consent; withdrawal may affect features that need that data. For access, correction, privacy questions, or complaints, contact privacy@profme.in. Requests may require account verification. Satish Rajnale is the Grievance Officer and may be contacted at privacy@profme.in. We will acknowledge a grievance within 48 hours and endeavor to resolve it within one month where applicable rules require those timelines; any shorter mandatory period prevails.

ProfMe is intended for adults and is not directed to children under 18. We use safeguards described in the Security Overview, including authenticated accounts, server-side authorization, scoped service access, and short-lived signed download links. No security measure guarantees absolute security. Certification or compliance with a named security framework is not represented.

Material policy changes will be identified by a new version and effective date; the app may require renewed acceptance before relevant use. Privacy contact: privacy@profme.in; general support: support@profme.in. Operator: ArchByte Studio, trade name of Satish Rajnale, individual sole proprietor in India. Principal business address: Kalewadi, Pimpri, Pune 411017, India.