Adarsh Media · Outreach CRM

Privacy policy

Effective date: 14 October 2026

This policy explains how Adarsh Media handles information in its private team outreach CRM at www.adarshmediacrm.com.

Information in the CRM

The CRM is a shared work tool for the Adarsh Media team. It may contain:

  • Team account identifiers, names, role settings, password hashes and session/security records.
  • Company and prospect contact details, research, sources, notes, outreach drafts and status history.
  • Assigned tasks, deadlines, shared calendar events, meeting details, participant identifiers and reminder settings.
  • Information a team member chooses to enter, import or include in a document they ask the CRM to process.

Login email fields are used as account identifiers. The CRM does not use those fields to send account emails or password-reset messages.

How information is used

Adarsh Media uses this information to provide the shared CRM, coordinate company research and outreach, assign work, schedule meetings, maintain account security, and keep an activity history for the team. Access to CRM records depends on account roles and workspace permissions.

The CRM does not sell personal information. It does not send outreach messages automatically. If a user opens a Gmail compose window or another social platform from the CRM, that user reviews and sends the message directly in that service.

Google Calendar data

Google Calendar connection is optional. A teammate connects their own Google account and grants the CRM access to events on calendars they own. The CRM requests the calendar.events.owned permission.

The CRM uses Google Calendar data only to provide the Calendar features the user chooses to use. When the meeting creator explicitly chooses to send or update Google invitations, the CRM sends the meeting title, description, start and end times, and selected attendee email addresses to Google Calendar. It can also ask Google to create a Google Meet conference for that meeting.

The CRM stores the Google refresh token encrypted with AES-GCM and uses it to perform the requested Calendar actions. Google access tokens are requested when needed to complete those actions. Google Calendar data is not used for advertising or sent to the CRM’s AI provider.

A teammate can disconnect their Google account in the CRM; this deletes the stored connection token from the CRM. Disconnecting does not remove invitations already created in that person’s Google Calendar. The meeting creator can cancel synced invitations through the CRM, or manage them directly in Google Calendar.

AI-assisted features

If AI features are enabled for the workspace, a user may choose to request message drafting, research quality checks, contact suggestions, document mapping, or summaries. For those requests, the CRM sends the relevant company, research, draft, or document text to OpenAI for processing. An uploaded document’s extracted text may be sent when the user requests AI document mapping; the original uploaded file is not stored by the CRM.

AI features are optional and are not used to send messages automatically. The CRM configures its OpenAI Responses API requests with storage disabled where applicable. OpenAI’s own terms and privacy information describe its handling of data it processes.

Storage and sharing

The CRM is hosted on Vercel and stores shared workspace records in a Turso/libSQL database. Information is available to authorized team members and administrators according to their CRM permissions. Google receives meeting details and attendee email addresses when a user explicitly sends or updates Google invitations. OpenAI receives relevant content only when an enabled AI feature is requested.

Adarsh Media may also disclose information if required by law or to protect the security and operation of the service. The CRM does not sell CRM data or use Google Calendar data for advertising.

Retention and choices

There is no automatic CRM-wide deletion period. Workspace information remains in the CRM until an administrator removes it or as otherwise needed to operate and secure the service. Some activity history may remain after a company record is removed. Team members can ask the CRM administrator about access, correction or removal of their account information and records they provided.

Disconnecting Google Calendar removes the CRM’s stored connection token but does not delete calendar events or invitations already created in Google. A synced meeting can be cancelled through the CRM by its creator; users can also manage events in Google Calendar.

Security

The CRM uses HTTPS, salted password hashing, secure session cookies, role-based access controls, and encrypted storage for Google refresh tokens. These safeguards reduce risk, but no online service can guarantee absolute security.

Changes to this policy

Adarsh Media may update this policy as the CRM or its data practices change. The effective date at the top of the page shows when it was last updated.

Contact

For privacy questions or requests about information in the CRM, contact Adarsh Media at team@adarshmedia.com.