1. Who we are and how to contact us
This policy is specific to Hey Stella, not a general policy for every Mektra product. Mektra operates Hey Stella. For support, privacy questions, access requests or deletion requests, contact heystella@mektra.ai.
A business that puts customer or employee information into a Hey Stella workspace may have its own obligations to those people. If your information was entered by a workspace customer, that business is often the best first contact for questions about why it collected or used your information. We can help with questions about Hey Stella’s handling of it.
2. Account and workspace information
We process account identifiers, names, email addresses, sign-in and session information, and information needed to authenticate you. We also process workspace names and settings, memberships, roles, ownership, invitations, invitation email addresses and membership activity.
Clerk provides Hey Stella’s account and session authentication. Signing in with Google shares basic identity information, such as your Google account identifier, email address and profile information, for authentication. You do not need to create a Replit account to use Hey Stella.
3. CRM and business records
We store the information you and authorized workspace members enter or import: people and company records, contact details, notes, tags, custom fields, deals, values and currencies, pipeline stages, tasks, due dates, priorities, calendar events and record relationships. Records can also include owners, creation and update times, archives and action history.
Workspace records are used to provide search, lists, scheduling, relationship context, activity receipts and the other features you request. Only enter information you are authorized to collect and share. Avoid unnecessary highly sensitive information, passwords, authentication secrets or payment-card details in CRM fields or Stella messages.
4. Stella and AI processing
Stella processes your instructions and permitted workspace context to find records and perform supported actions. Hey Stella stores conversations, sent messages, assistant responses, structured results and action receipts so you can revisit your work. Authorized workspace access controls also apply to this history.
When AI-assisted interpretation is enabled, an instruction and limited reference context can be sent to OpenAI through our AI infrastructure provider. An instruction may itself contain names, contact details, business information or message content that you choose to include. Not every Stella request uses an external model, and the current proposal flow does not automatically send a complete CRM database or entire conversation history.
AI-provider handling and retention depend on the provider and applicable service configuration. We do not make a blanket promise of zero third-party retention or zero third-party training for all possible providers. Ask us before submitting regulated or unusually sensitive data. Hey Stella itself does not operate a general-purpose model-training feature using your workspace records.
5. Voice and microphone information
Voice features, when enabled and supported by a configured provider, can request microphone permission and process audio to create a transcript or generate a spoken assistant response. Voice availability can differ by environment and workspace; a voice interface does not mean a live speech provider is available.
The current Hey Stella voice flow handles uploaded audio temporarily rather than saving raw recordings as durable CRM or conversation records. A transcript is an editable draft until you choose to send it. Once sent, its text is retained as an ordinary Stella message. Spoken responses can be generated from an authorized saved assistant response.
An enabled speech provider may process audio, transcripts or response text under its own service terms and retention settings. Temporary handling within Hey Stella does not establish the provider’s retention period. Contact us for the current provider details before using voice with sensitive information.
6. Communications
Communications features can store senders, recipients, CC/BCC addresses, subjects, message content, drafts, delivery or failure status, timestamps, thread relationships, provider identifiers and attachment metadata. A record may be linked to a person, company or deal. Attachment metadata does not guarantee that an attachment can be downloaded or previewed in Hey Stella.
Drafting is different from sending. When you authorize a supported send, message content and addressing information are transferred to the connected delivery provider and recipients. Private and shared communication visibility depends on the applicable ownership and workspace controls. Delivery, SMS and other channel capabilities depend on an enabled provider; an interface or catalog entry is not a guarantee that a channel is connected.
7. Google sign-in, Gmail and Calendar
Google sign-in and Google service connections are separate authorization flows. Normal sign-in requests basic identity information, not Gmail, Calendar, Drive or contacts permissions. You choose separately whether to connect Gmail or Google Calendar and approve the permissions shown by Google.
An enabled Gmail connection can read and synchronize message content and metadata into Communications and send messages you authorize. An enabled Calendar connection can read selected calendars and event information, and create, update or cancel events through supported synchronization actions. Calendar data can include titles, descriptions, times, time zones, locations, meeting links and recurrence information.
Google connections are associated with the authorizing member and workspace. Imported Calendar events can become workspace records visible to authorized workspace members, so connect only calendars appropriate for that workspace. Connection ownership does not give every member blanket access to another person’s Google account.
You can disconnect supported connections in Hey Stella and revoke access through your Google account. Disconnecting stops further authorized access and clears stored connection credentials; it does not automatically erase messages, events, record relationships or audit history already retained in the workspace, nor does it undo actions already completed at Google.
Hey Stella’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used for the user-facing features you authorize, not sold, used for advertising or used by Hey Stella to train general-purpose AI models. Human access and onward transfers of Google data are limited to the purposes and exceptions allowed by that policy, such as your affirmative permission, necessary security work or applicable law.
Google API Services User Data Policy8. Other integrations and service providers
When you connect another supported service, we process the account information, permissions, credentials and selected records necessary for that connection. Permissions, data direction and availability vary by integration. Submitting an integration request or seeing a provider in the catalog does not connect it or authorize data transfer.
Our service providers include Clerk for authentication, Replit for hosting and infrastructure and the AI integration gateway, OpenAI for enabled AI processing, and Google for Google identity and connected Gmail/Calendar features. Hosting and database infrastructure process service data to store and deliver Hey Stella. Additional speech, communications or integration providers receive relevant information only when those features are configured and used.
Providers may process information in countries other than your own under their applicable terms. This policy does not claim a particular data-residency region, certification or cross-border transfer mechanism that has not been established for your workspace. Contact us for current processor and transfer information.
9. How information is used and shared
We use information to operate Hey Stella, authenticate users, manage authorized workspace access, store and display business records, process instructions, synchronize services, support users, diagnose failures and protect against abuse. Information is shared with authorized workspace members, recipients of your communications and providers needed for the features you use.
We may also disclose information when required by law or necessary to investigate abuse or protect rights and security, subject to applicable restrictions. Any business transfer involving service data must follow applicable law and, for Google data, Google’s Limited Use requirements. Hey Stella does not include an advertising-data marketplace or a feature for selling your CRM data.
11. Retention, archives and deletion
Hey Stella retains account, workspace and business data for the purposes described in this policy, including operating a workspace, supporting its history, resolving issues and meeting applicable obligations. Different records and providers can have different retention needs. No universal automatic deletion period is promised here.
Archiving a record, removing a task from an active view, leaving a workspace or disconnecting an integration is not the same as permanently erasing all underlying data. Audit history, related records and imported content may remain. Backups and third-party copies can have separate retention practices.
For an account or workspace deletion request, contact heystella@mektra.ai. We assess identity, workspace authority, other members’ rights, legal obligations and technical scope before acting. We will explain applicable limits and timing rather than promise an unverified immediate purge or backup-deletion deadline.
12. Security
Hey Stella uses authenticated requests, workspace membership and role checks, and database access controls designed to restrict unauthorized access between workspaces. Google connection tokens are stored using application-level encryption. Access and integration actions are checked on the server, not only by hiding controls in the interface.
No service, access control or encryption technique can guarantee perfect security. You are responsible for securing your account, devices and authorized members, reviewing connected-service permissions and notifying us promptly of suspected unauthorized access. This policy does not claim a security certification, blanket encryption coverage or an uptime guarantee.
13. Your choices and privacy rights
You can update supported records and settings, manage authorized memberships, disconnect integrations and use available record exports. Current CSV exports cover supported CRM records; they are not a comprehensive account, workspace or conversation export. Hey Stella does not currently provide a universal self-service account-erasure control.
Depending on applicable law, you may have rights to access, correct, delete or receive information, restrict or object to processing, withdraw consent, or complain to a relevant data-protection authority. Send requests to heystella@mektra.ai. We may need to verify identity and authority, and we will consider the rights of other workspace members and customers. Withdrawing a permission does not undo prior lawful processing.
14. Children and changes to this policy
Hey Stella is a business service, not a product directed to children. Users must have the legal capacity and authority described in the Terms. Contact us if you believe a child has supplied personal information to Hey Stella so we can assess and address it.
We may update this policy as features, providers or legal requirements change. The updated date identifies the current version. Where required, we will provide additional notice or obtain consent before a material change takes effect. Questions about this policy can be sent to heystella@mektra.ai.