Skip to content
ProfMe
Product
Meeting captureRecord audio on your Mac without a botMemory and commitmentsSaved work contextSearch meeting contextFind and revisit saved meeting materialAsk about saved contextCheck answers against their source recordsPrepare for meetingsReview relevant saved context
How it worksUse casesSecurityBlogPricing
ProfMe

A professional memory product that connects context across meetings, people, decisions, projects and commitments.

Developed and published by ArchByte Studio.

© 2026 ProfMe

Product

  • Overview
  • Meeting capture
  • Memory and commitments
  • Search work context
  • How it works
  • Use cases
  • Pricing
  • Guides and journal

Company and trust

  • About
  • Security and data practices
  • AI and recording
  • Contact

Spend less time reconstructing work. Spend more time doing it.

Privacy PolicyTerms of ServiceRefund & Cancellation PolicyAI & RecordingSecuritySupport: support@profme.inPrivacy: privacy@profme.inSecurity: security@profme.inBuyer support phone: +919136757599
Published policy

Security & Data Practices

Version: 1.2.2 · Effective: 16 October 2026

Questions about these policies? Email support@profme.in.

On this page

  1. 1. Operator and scope
  2. 2. Safeguards in the implementation
  3. 3. Data handling and providers
  4. 4. Limits and incident contact
  5. 5. Contact

1. Operator and scope

ProfMe is developed and published by ArchByte Studio. ArchByte Studio is the trade name of Satish Rajnale, an individual sole proprietor in India, not a separate legal person. Principal business address: Kalewadi, Pimpri, Pune 411017, India. This overview describes safeguards visible in the product and repository; it is not a guarantee, audit report, or certification.

2. Safeguards in the implementation

The application uses authenticated accounts and server-side authorization; admin operations are intended to be restricted to configured identities. Policy content and acceptance/audit records are designed to be immutable. User export downloads use short-lived signed links. The production object-storage bucket currently reports no lifecycle or soft-delete policy, so no cloud-object expiration control is claimed here. The product has account export/deletion workflows and local recording-retention preferences, but end-to-end production behavior has not been verified. Code presence alone does not establish that a control is active or effective.

3. Data handling and providers

ProfMe relies on third-party authentication, cloud, workflow, speech, AI, monitoring, and (if enabled) integration/payment services. Depending on feature and configuration, ProfMe uses Google Cloud, Clerk, Temporal, Google Gemini or OpenAI, Deepgram where enabled, Sentry, Composio for connected integrations, and Paddle when checkout is enabled. Providers and regions vary; third-party safeguards and retention are governed by their terms. No claim is made that data is stored only in India.

4. Limits and incident contact

No SOC 2, ISO 27001, ISO 27701, HIPAA, or other independent certification is represented by this overview. No system can be guaranteed secure. Please report a suspected vulnerability or security incident to security@profme.in. Do not include passwords, access tokens, or unnecessary personal data in a report. For consumer complaints, contact Satish Rajnale, Grievance Officer, at support@profme.in.

5. Contact

Security contact: security@profme.in. This Security Overview is version 1.2.2, effective 16 October 2026, 00:00 IST.

Terms of ServicePrivacy PolicyRefund & Cancellation PolicyAI & Recording