LYNTURA · LEGAL
Privacy Policy
Lyntura is operated by Mayott Media LLC. This policy explains how information is handled when you visit our website, use a business workspace, or interact with a business using Lyntura.
1. Our role and this policy
Mayott Media LLC (“we,” “us”) provides Lyntura's CRM and related services. We determine the processing needed to operate our website, administer customer accounts, secure the service, provide support, and manage our billing relationship. When a business uploads leads or uses Lyntura to communicate with its contacts, that business generally determines why those contact records and communications are processed; we process them to provide its requested services and meet our own applicable obligations.
If you received a message from a Lyntura customer, that customer's privacy notice and choices also matter. Contact the identified sender about its collection of your information, marketing consent, or records. We can help route a request when we can identify the relevant workspace. This policy does not replace a separately agreed data-processing agreement or another business's notice.
2. Information we collect or receive
- Account and business details: names, business names, email addresses, phone numbers, roles, permissions, account preferences, authentication records, and support communications.
- Workspace content: contacts and leads, imported spreadsheet fields, lists, notes, opportunities, tasks, appointments, templates, files, images, workflow instructions, and other information authorized users provide.
- Communications and activity: message content, sender/recipient details, call events and duration, delivery/failure records, replies, consent and opt-out records, and recordings or transcripts when those features are enabled. Campaign features may also record email-open or link-click events where configured. Those signals can be incomplete or affected by recipient privacy software.
- Billing information: plan and order details, invoices, measured usage, payment status, processor customer/payment references, and limited payment-method details returned by the processor. Payment-card entry is handled in the payment provider's interface, not ordinary CRM notes.
- Technical and security information: IP addresses or derived identifiers, browser/device information, requests, timestamps, login and verification events, audit records, errors, and essential cookies or local preferences. Hosting, network, and identity providers may also process technical information when you use their services.
- Connected services: information and authorization records needed for integrations an authorized user enables. The categories depend on the permissions and feature selected.
Information comes from you, your workspace administrators and colleagues, business customers and their contacts, enabled service providers, and the use of the Services. Do not enter information you lack permission to use or unnecessary high-risk personal information.
3. Why we use information
We use information to authenticate users; maintain business workspaces and permissions; store and organize records; carry out requested messages, calls, workflows, and integrations; generate requested AI assistance; process payments and reconcile usage; respond to support requests; investigate abuse and errors; protect the service; comply with legal obligations; and handle disputes and authorized data requests.
We do not treat importing a lead, creating an account, or accepting the Terms as permission to send unrelated marketing. A business using Lyntura is responsible for obtaining the permissions required for its outreach. Account-security and service notices are distinct from marketing subscriptions.
Where a law requires a legal basis, our processing depends on the purpose and context, including providing contracted services, legitimate interests in operating and securing a business service, compliance with legal obligations, or consent where required. We do not rely on the words “legitimate interests” to replace consent where consent is legally necessary.
Agent Hub training and private support
Where engagement tracking is enabled, opening an event’s Google Calendar or calendar-download link while signed in records your account, session occurrence, link type and click time. This helps authorized Hub owners and support staff plan training and understand engagement. Opening a link does not confirm that you saved the event or attended. Optional RSVPs are a separate record. Attendance is not inferred from either action; it requires a separate attendance source.
Private support requests may include the carrier, an existing ticket or reference number, the issue, urgency, assigned support owner and redacted attachments. Requests and attachments are available to the requester and authorized Hub support staff, not the public community or other agents. Important support actions are audited. Do not submit client health records, identity documents, credentials or payment details through this feature. Use the carrier’s approved secure process for those records.
Calendar and carrier links open their providers’ services, which have their own privacy practices. A private training subscription link can be read by anyone holding that link until it expires or is revoked; keep it private.
Activity, support and AI
Activity on the service is logged. When you use Lyntura, we record activity such as sign-ins, pages and features used, device and browser details, errors, and support requests. When you ask for support, these details are attached to your request so we can resolve it quickly.
How we use this information. We use it to provide and secure the service, to respond to support requests, to enforce our terms, to comply with law, and to train and improve the AI features and assistants that Lyntura provides.
Messages and content. Messages, posts and other content you create on Lyntura are stored on our systems. We may access them to provide support, keep the service safe, enforce our terms, or comply with law. We do not sell your messages or content.
Staff work, supporting files and hours
Staff Operations stores task assignments, progress, comments, decisions, support requests, meeting recaps and files your team chooses to attach. These records support internal work and accountability. Access depends on current Hub membership and the relevant role or assignment. Task files follow the task's access; meeting recap files and private support notes are restricted to authorized staff. Reassigning a task can change who can access its files.
Employees can submit their own hours. The Hub owner can designate people to review hours for completeness. That permission does not grant access to compensation or authorize a payment. Payroll preparation and review use separate permissions, and final payroll approval remains with the Hub owner. Submitting hours or approving a task does not transfer money.
Internal reporting relationships and carrier-specific upline history are administrative records. They do not grant access to payroll or other private workspaces. Member-facing names follow the account's display-name setting; authorized identity administrators can view the required real identity separately.
Supporting uploads are stored with the workspace and limited by file type, size and workspace capacity. They are served as private downloads after access checks. Do not attach Social Security numbers, birth dates, bank-account forms or E&O documents to ordinary task or pipeline notes. The approved contracting intake opens with its external provider; these sensitive intake fields are not automatically imported into Staff Operations.
Hub support replies remain in the Hub unless a separately authorized and verified external connection is used. Manual signature copying does not grant mailbox access. Connection setup status is shown separately from a verified provider synchronization. Contact your workspace owner for access, correction and retention requests under the applicable workspace and Lyntura policies.
5. Google sign-in and optional Google integrations
If you choose Google sign-in when available, Google processes the authentication and provides basic identity information under the requested identity scopes. The sign-in feature verifies Google's identifier and token claims and stores an association between that identifier and your existing CRM account. It does not match an unverified email to create a new license or give access to another company. Initial linking requires proof of the existing CRM account, and applicable CRM security verification still applies.
Google sign-in does not request access to Gmail or Google Calendar and does not store a Google refresh token for those services. Separately enabled integrations may request additional permissions in their own authorization flow; review that flow before consenting. We use information obtained through Google to provide the requested feature. Lyntura'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 where applicable. Information received through Google APIs is not used to develop, improve or train AI models.
You can manage a linked Google sign-in through available account-security controls or contact us for help, and review or revoke Lyntura's access in your Google account connections. Disconnecting Google does not automatically delete your CRM account, business records, invoices, or security history.
5a. Connected email and read-only Outlook calendar views
Connecting a mailbox in Settings is optional and separate from signing into Lyntura. Each person connects their own account and approves the permissions on Google's or Microsoft's website. An employer's Microsoft administrator may also need to approve the application. A connection does not add users to your Lyntura business or give access to another customer's workspace.
Reading email. The read-only connection uses Gmail's gmail.readonly or Microsoft Graph's delegated Mail.Read, with identity and offline-access permissions needed to identify and maintain the connection. These permissions can cover the authorized mailbox beyond a single CRM contact. Lyntura's pipeline monitoring is a separate choice: it matches new incoming email to existing contacts you can access and stores message identifiers, subjects and dates on contact activity timelines. Authorized colleagues with access to that contact may see that activity. A matched message body is fetched only when you request it, shown as plain text to the connecting user, and not saved to shared CRM records or sent to AI. Attachments and remote images are not fetched by this reader.
Sending with Outlook. Where enabled and separately approved, delegated Mail.Send allows Lyntura to submit an individual email you review and send from your connected Microsoft account to an accessible CRM contact. Microsoft receives the recipient, subject and message needed to process that request and saves a copy in Sent Items. An accepted request is not proof of delivery. Lyntura temporarily encrypts a prepared message for its 10-minute review window. That review expires automatically; the saved message content is erased after a send attempt or by the next cleanup after expiry. Lyntura retains send-attempt identifiers, account and contact references, outcome information and a keyed message digest for up to 90 days to prevent accidental duplicate submissions and explain the result. These records do not contain a readable copy of the sent subject or body. This connection does not enable bulk campaigns or automatic marketing, and existing read-only connections do not gain sending access without fresh consent.
Read-only Outlook calendar view, where available. The optional calendar view requests delegated Calendars.Read to display event titles, dates and times from your own connected calendar. It is private to the connecting user. Lyntura fetches a limited date range when you request it and does not persist those event details or copy them to shared CRM appointments. This view does not create or change appointments, send meeting invitations, or provide two-way calendar synchronization. Those actions would require a separately disclosed feature and fresh permission.
Security and choices. Lyntura stores encrypted authorization tokens to maintain the access you approved; it does not ask for or store your Google or Microsoft password. Access is bound to your CRM account and company. Disconnecting removes Lyntura's saved mailbox authorization and stops further connection use. Previously recorded business activity and security records may remain under the retention policy below. You can also revoke access through Google account connections or your Microsoft account or organization's application controls. Microsoft processes its own services under the Microsoft Privacy Statement.
Mailbox bodies and connected-calendar content are not provided to AI by these integration features. Google API information remains subject to the Limited Use commitment above. We do not sell connected-mailbox information or use it for unrelated advertising. The permissions actually granted and the feature available to your account control what Lyntura can do.
5b. Optional connected calendars and appointment sync
Separate permission and customer choice. Calendar connections are optional and are enabled only where the feature is available. You sign in directly with Google or Microsoft, approve the calendar permissions, and choose a calendar in your CRM workspace. Connecting a calendar does not enable email monitoring, email sending or a paid subscription.
Permissions requested. Google Calendar requests calendar.calendarlist.readonly to list available calendars and calendar.events to read and manage events. Microsoft requests delegated Calendars.ReadWrite and User.Read, plus sign-in and offline-access permissions. These provider permissions can cover more calendars than the one selected in Lyntura; Lyntura's sync feature uses the calendar you choose. Your organization's administrator may need to approve the connection.
Information used and stored. We store the connecting account identity, selected calendar, encrypted authorization tokens, connection status, sync results, and links between CRM appointments and provider events. We keep a bounded private snapshot of event identifiers, titles, dates, times, and all-day or recurrence indicators to display your calendar. Private-marked events display a generic title. The background check currently covers approximately 30 days before and 60 days after the check; linked appointments may be checked separately. Event bodies and attachments are not stored by this sync feature.
Visibility and two-way changes. Unlinked external events are visible only to the connecting user in Lyntura. CRM appointments remain visible under the company's existing access controls. You can choose one default calendar for new CRM bookings assigned to you, or link eligible appointments individually. Changes to linked appointment times or cancellations can flow in either direction. Conflicting edits, recurring events, all-day events and events with guests may need review rather than automatic changes. Synchronization is periodic, not instantaneous.
Your controls. You can pause synchronization or disconnect in Calendar connections. Pausing clears the private event cache; disconnecting also removes the saved authorization credential. Saved CRM appointments and their linkage or audit history may remain under the service's normal retention rules. Disconnecting does not delete events already in your provider calendar. You can separately revoke Lyntura's access in your Google or Microsoft account.
Purpose limits. This integration does not provide calendar data to AI or use it for advertising. Google API information remains subject to our Google Limited Use commitment. The current automatic synchronization does not send meeting invitations. Any separately offered invitation workflow must disclose its recipients and require confirmation.
5c. Optional Google Contacts automations
Google Contacts is a separate connection that you choose in CRM Settings. It does not use your Google sign-in, Gmail-reading permission, or calendar permission to obtain access to your contacts. You review its own disclosure and approve Google’s requested Contacts permission before it can run. Availability still depends on provider configuration and approval.
A workflow’s Create Google Contact action uses its owner’s own connected Google account. It can copy the visible lead’s name, email address, phone number, and company. It does not copy insurance information, policy details, health information, internal notes, or message history. The connection can search your Google Contacts to identify an existing exact match and avoid creating a duplicate. An existing matching contact is reused rather than silently overwritten.
We store the connected account identifier, encrypted authorization credential, and scoped operation receipts needed to run and reconcile that action. Receipts include a CRM contact reference, a payload hash, operation status, and the resulting Google contact reference; they are not a general copy of your Google address book. Your connection is private to your account and workspace. Other users do not receive access to your Google account merely because they share a company or Agent Hub.
You can disconnect in Settings and revoke Lyntura’s access in your Google account. Disconnecting prevents later actions through that connection; it does not delete contacts already created in Google. Manage those contacts in Google Contacts. Adding a contact does not create marketing consent or authorize an email, text, or call.
5d. Optional personal reminders and connected-mailbox sending
Separate permission and availability. Where this feature is available to your account, you can authorize reminder email from your own connected Gmail or Outlook mailbox. This is separate from signing in, reading email, calendar sync and campaign delivery. Lyntura requests Gmail's gmail.send or Microsoft Graph's delegated Mail.Send in a separate consent step, together with the existing connection's approved permissions. A read-only connection does not gain sending access automatically. Provider review, organizational administrator approval, your account's access and the feature's current readiness can limit availability.
What a reminder does. An authorized workflow owner selects the trigger, timing, channel, message and recipient before publishing. A reminder can create an internal task, send a personal text where the sender and recipient are eligible, or submit one email to the owner, an active teammate, an accessible CRM contact or one explicitly entered email address. External email recipients require the owner's confirmation of permission and remain subject to contact-access and suppression checks. The reminder feature does not authorize bulk marketing, arbitrary sender impersonation, CC or BCC recipients, or the use of another person's mailbox. Each scheduled email uses the workflow creator's selected connected account.
Information used and retained. Lyntura stores the workflow settings, reminder title and body, timing, creator and recipient references, delivery destination, selected connection reference and per-channel outcome in the CRM database. A reminder may include contact values that the owner selected in its template. Authorized workspace administrators can see workflow and reminder information under their existing access. Email submission sends the destination, subject and message to Google or Microsoft; the provider processes the message under its own terms and may retain it in the mailbox and recipient systems. Lyntura retains operational and billing evidence to explain outcomes, prevent duplicate attempts and attribute usage. These reminder records follow the general retention policy below; they do not use the separate ten-minute message-review or 90-day manual-send retention described in Section 5a.
Personal text reminders. Each person who receives a personal SMS reminder records their own phone number and explicitly opts in through Settings. Saving a number is not proof that its ownership has been verified. Teammates can receive this type of reminder only while their own opt-in is active. Lyntura sends through the workspace's eligible, registered telephone connection and records sender, recipient, delivery and payer information. A number purchase or CRM license alone does not establish texting readiness. Applicable usage is attributed to the workflow creator's billing arrangement, which may include company sponsorship, rather than automatically charged to the recipient.
Your controls and delivery limits. You can pause a workflow, disable scheduled sending for a mailbox, withdraw your personal SMS opt-in, or disconnect the mailbox in Settings. You can also revoke the application's access through Google or Microsoft. These controls block new eligible submissions after they are checked; they cannot recall a message already submitted to a provider. Disabling sending within Lyntura does not revoke the underlying provider grant or erase provider copies. Accepted means the provider accepted the request, not that the recipient received or read it. A failure or uncertain outcome needs review; Lyntura does not automatically repeat a channel already accepted or whose submission result is uncertain.
AI assistance. AI may help draft a workflow or message from the instructions and allowed workspace context you provide. It does not choose an unresolved person or mailbox, confirm recipient permission for you, or turn on sending merely because it produced a draft. Review recipients, content and timing before publishing. The connected-mailbox reminder feature does not supply mailbox bodies or calendar content to AI. Google API information remains subject to the Limited Use commitment in this policy.
6. AI, media, and automation
When you ask an AI feature to help, the service may process your prompt, relevant current document or email content, selected workspace context, instructions, and generated output. The current AI assistance uses configured private computing infrastructure. This does not mean the entire CRM avoids external network or service providers. Images and media can be stored and served through the configured storage connection; communications, identity, and payment features use the providers described above.
Do not put passwords, payment-card details, or unnecessary sensitive personal information into prompts. AI conversations and outputs may be retained as workspace or diagnostic records. Review generated content and automation actions before use; AI output is not guaranteed to be accurate. A materially different use of previously collected personal information requires the notice and consent described in Section 11 where applicable.
7. Storage, security, and retention
The CRM uses operator-managed server storage for its database and configured media storage, with network and feature providers involved as described above. We use administrative, technical, and access safeguards designed to protect information. No system is completely secure, and we do not promise perfect security, zero downtime, exclusive on-device processing, or that all providers store information in a single country.
We keep information for as long as reasonably needed for the purpose it was collected, service delivery, an applicable agreement, legal or tax requirements, security, abuse prevention, and resolving disputes. The appropriate period depends on record type, account status, customer instructions, legal obligations, and technical backup constraints. Account deactivation or subscription cancellation does not automatically delete all records. Security and billing records and workspace history may be retained after a user leaves.
For verified deletion requests, we assess the applicable duties and exceptions, remove or de-identify information as appropriate, and communicate relevant limits. This process may require manual review; it is not a promise of an automated or immediate purge. Backups, audit history, provider copies, and records subject to a legal hold may not be erased immediately. Retained backup copies remain subject to applicable deletion obligations and limits on further use. Disabling a standard user or removing a demonstration account may retain leads and business history. Ask us about data return or deletion before closing a workspace if your business needs an export.
8. Cookies, local storage, and email signals
Essential cookies support sign-in, session security, verification, and authorized account preview. Browser storage may remember appearance, navigation, motion, or editor preferences. Blocking essential cookies can prevent login. Optional public-website analytics is described below. Our infrastructure providers may still process request logs and necessary security information.
Customer communications may include configured delivery, open, or click tracking. The sending business should explain its tracking practices and obtain any required consent. An unsubscribe request controls marketing from that sender; it does not necessarily stop essential account-security or legal notices.
Optional website analytics
Our public Lyntura and Lyntura CRM marketing pages use Google Analytics only after you choose Allow analytics. Analytics helps us understand page visits, approximate location, device/browser categories and engagement. Google receives technical request information and uses first-party identifiers to distinguish visits. See how Google uses information from sites that use its services.
We do not load the Google Analytics tag before permission. Declining keeps analytics off. We respect supported Global Privacy Control and Do Not Track signals. Select Cookie preferences in a page footer to change your choice; withdrawing permission stops measurement and removes this site's Lyntura analytics cookies. Each website remembers your choice separately for up to 180 days. Blocking browser storage may require you to choose again.
This implementation measures approved public pages. It does not add Analytics to signed-in CRM pages or transmit CRM contacts, mailbox content, form entries, URL query strings or fragments. Automatic form, search, download and outbound-link measurement, Google Signals and advertising personalization are disabled. Reporting uses static page names and cleans referrer addresses to their origin. Google Analytics does not provide a complete count of all visitors: declined consent and browser protections can limit measurement.
Analytics consent cookies and identifiers expire within 180 days in this implementation. Provider-side retention follows the Analytics property's configured retention settings. You can also use Google's Analytics opt-out browser add-on. Google domain ownership verification in Search Console is separate from this optional visitor measurement.
9. Your choices and privacy rights
You can review available account settings, update information, manage authorized integrations, use applicable unsubscribe or STOP mechanisms, and contact the relevant business about its records. If you are an account user, your workspace administrator may handle access or correction requests. If you are a lead or recipient, contacting the business that collected your information is often the quickest route; we will assist with identifying or forwarding the request when appropriate.
Depending on your location, applicable thresholds, and legal exceptions, you may have rights to access or obtain a copy of personal information, correct it, request deletion, restrict or object to processing, withdraw consent, opt out of certain advertising or sale/sharing, appeal a request decision, or complain to a competent privacy authority. Where California law applies, this includes applicable rights to know, correct, delete, opt out of sale or sharing, limit certain uses of sensitive information, and receive nondiscriminatory treatment. We do not require you to waive a non-waivable privacy right.
Send a request or appeal to andrew@mayottmedia.com with enough information to identify the relevant business and request. You do not need to create a new account to make a privacy request. We may verify identity or an agent's authority using proportionate information before disclosing, changing, or deleting records. Do not email identity documents or sensitive records unless we arrange a suitable method. We respond within applicable legal periods and explain a refusal where required. An authorized agent may contact us subject to required verification.
Where the Texas Data Privacy and Security Act applies, Texas consumers may request access, correction, deletion, and a portable copy of covered personal data, and opt out of covered sales, targeted advertising, or profiling used for legally significant decisions. You may appeal a declined request by replying to the decision or emailing the contact above with “Privacy appeal.” If an appeal is denied, you may contact the Texas Attorney General. Applicable exceptions and non-discrimination protections remain in effect.
We do not use the current marketing page for cross-context behavioral advertising or operate a sale/sharing preference toggle. Browser “Do Not Track” or opt-out signals do not disable necessary service or security records. If you have questions about an opt-out signal, email us; any handling of such signals remains subject to applicable law.
10. International processing and children
Information may be processed in the United States and locations where relevant providers operate. Where a transfer requires safeguards under applicable law, those safeguards must be established through the applicable agreement or transfer mechanism; using Lyntura is not a waiver of those requirements. Contact us before onboarding a workspace that requires a particular data location or regulated international-transfer arrangement.
Lyntura is intended for adult business users, not children. Do not create an account for a child or intentionally submit children's personal information without an expressly agreed lawful, supported purpose. If you believe we have received children's information inappropriately, contact us so we can investigate and take appropriate action.
11. Changes and contact
We will update the effective date when this policy changes. We will provide appropriate notice of material changes and obtain consent when required before using previously collected information for a materially different purpose. An update is not retroactive permission to disregard an earlier privacy commitment.
Mayott Media LLC, based in Texas, United States, operates Lyntura. Contact andrew@mayottmedia.com for privacy questions, individual-rights requests, deletion assistance, or concerns about data handling. Please identify the relevant business/workspace without including passwords, verification codes, or full payment details.