PRIVACY

Privacy Policy

Last updated: September 30, 2026

This policy explains how LINKERNO collects, uses, discloses and protects information when people visit our website, create a workspace, request a trial, use a LINKERNO-configured Virtual Front Desk, interact with LINKERNO Web Chat, request professional services, or use supported scanning and automation features.

Information from businesses that contact or join LINKERNO

We may collect a contact person’s name, business name, business email, phone number, website, business address or service area, industry, estimated inbound-call volume, current phone setup, plan selection, requested coverage, workflow preferences, communications with us, account activity, verification state and other information a business chooses to provide during signup, onboarding, billing, project scoping or support.

Automated workspace and onboarding records

When a business creates a workspace, LINKERNO may create internal business and user records, onboarding status, readiness results, verification status, website-import status, trial entitlement state, billing state and other operational records needed to prepare and secure the account. These records may also show whether a customer-facing feature is Off, Shadow, Controlled Rollout, Live, on hold or awaiting provider readiness.

Information from callers and website visitors using a configured front desk

Depending on the business’s approved workflow, LINKERNO may process a person’s name, callback number, email, service location or ZIP code, requested service, description of the issue, urgency, preferred timing and other information reasonably needed for the inquiry. The exact information depends on the applicable business configuration.

Website Chat

When a business enables LINKERNO Web Chat, LINKERNO may process and store chat messages, contact information voluntarily provided in the conversation, inquiry details, timestamps, conversation/session identifiers, channel status and related operational records needed to provide the service, prevent abuse, route the inquiry, create contacts or leads, maintain security and support the business.

Automated systems may be used to respond, classify or organize a conversation using approved or imported business knowledge. Web Chat may be placed in Shadow or pre-live mode before public activation. LINKERNO is designed to preserve uncertain requests for follow-up rather than intentionally inventing business facts.

LINKERNO may also store a business’s Web Chat enable/disable preference, the time that preference was recorded, readiness-check results, failed-check names, current channel mode, mode-change reasons and a limited operational audit history. These records are used to decide whether the channel may move from Shadow to Live, to return it to Shadow if a critical readiness condition is lost, or to keep it Off when the business disables it. Readiness automation does not authorize unrelated marketing use of customer-chat content.

Action readiness, booking, follow-up and transfer records

LINKERNO may store capability-level readiness records for supported booking, messaging follow-up, warm-transfer, callback and related action workflows. These records can include the current action mode, provider-health or readiness status, task status, readiness reason, timestamps, queue transitions, idempotency or deduplication identifiers, and limited operational audit information needed to prevent duplicate or premature external actions.

If a business configures warm transfer, LINKERNO may store the business’s enable/disable preference, transfer destination, transfer/escalation instructions and the provider-readiness state used to determine whether transfer may remain Shadow or become eligible for Live execution. A transfer destination is used to route or prepare an approved business workflow and is not collected for unrelated LINKERNO marketing. LINKERNO may move eligible tasks from Shadow to Queue when readiness later passes, or return a queued task to Shadow if a required capability is no longer ready.

For supported Retell voice configurations, LINKERNO may send the minimum provider configuration needed to prepare an approved live-session transfer, including the transfer destination, transfer rules and a concise private handoff instruction for the receiving party. The private handoff may use caller information already collected in the same service interaction, such as a caller name, callback number, reason for calling, urgency and a short summary, when that information is reasonably needed for the service handoff. LINKERNO stores provider verification status, configuration timestamps, destination/rules fingerprints and related audit information so it can detect stale or mismatched transfer settings without storing provider API credentials in the client portal.

Warm transfer is designed to execute during the live voice session. LINKERNO blocks background replay of a transfer task and does not treat an internal transfer request or queued record as proof that a human handoff succeeded. Provider events, call records or other outcome information may be used to distinguish a completed transfer from a failed or cancelled attempt.

Per-customer or per-lead information used for booking, follow-up or transfer can include the inquiry/contact information already captured for the service request, appointment identifiers, provider confirmation identifiers, consent or opt-out state where applicable, and action outcome information. A request or queued action is not treated as a completed provider action merely because LINKERNO created an internal task.

LINKERNO Native Calendar

If a business enables Native Calendar, LINKERNO may store the business’s booking hours, timezone, appointment duration, minimum-notice setting, booking horizon, enable/disable preference, current readiness mode and a limited mode-change audit history. For each confirmed appointment, LINKERNO may store the appointment identifier, requested and confirmed start/end time, duration, provider confirmation identifier, booking status, confirmation fingerprint and timestamps needed to prevent duplicate or conflicting bookings.

Native Calendar uses these records to calculate available slots, reject overlaps that could cause double booking, process supported book/reschedule/cancel actions and distinguish a requested appointment from a provider-confirmed booking. These scheduling records are used for the configured customer workflow and are not collected for unrelated LINKERNO marketing.

Live voice appointment booking

For supported live voice booking, LINKERNO may process the signed Retell call context needed to map the active call to exactly one configured business, including the Retell call identifier, agent identifier, destination number and caller number when provided by the voice platform. LINKERNO may also process a caller name or callback number when already provided in the call and needed to create or complete the appointment record.

When availability is requested during a call, LINKERNO creates a short-lived appointment offer containing an offer token, temporary slot identifiers, available start/end times, timezone and appointment duration. The offer is bound to the mapped business and Retell call identifier and normally expires after 15 minutes. LINKERNO stores the server-side offer temporarily so that a later booking request can be limited to a slot that was actually offered during the same call. After selection, LINKERNO may store a non-plaintext fingerprint of the offer token, selected slot identifier, provisional appointment-to-call correlation, booking timestamps, provider confirmation identifier and outcome information needed for idempotency, conflict prevention, auditing and support.

Voice booking requests are authenticated using a signed provider request before LINKERNO uses the request payload. LINKERNO does not rely on a business identifier supplied by the voice model to choose the customer account. Availability is checked again immediately before booking. If the slot is no longer available, the offer expired, the call cannot be mapped unambiguously, or the provider/readiness checks fail, the booking may be rejected and the assistant may request new availability. These scheduling and security records are used to operate the configured customer workflow and are not collected for unrelated LINKERNO marketing.

Calls, recording, transcription and messaging

Depending on configuration and applicable requirements, LINKERNO may process call metadata, caller information, summaries, transcripts, recordings or messages. Recording, transcription and automated messaging are not treated as automatically enabled for every customer. Applicable notices, permissions, carrier requirements and legal obligations should be addressed before use.

Website Scanner and website-derived information

If a user submits a public business website to a LINKERNO scanning or onboarding feature, LINKERNO may retrieve publicly available homepage content and technical metadata needed to evaluate supported website, conversion, contact, trust or search-readiness signals. LINKERNO may store scan results, score components, recommendations, source attribution and operational timestamps needed to provide the feature and improve the workflow.

Website synchronization

When a business enables supported website synchronization, LINKERNO may retrieve publicly available content from the business website to detect changes and prepare knowledge candidates. Candidate changes are not intended to be silently published into customer-facing automation without the applicable review or readiness process.

Professional services and project data

If a business requests AI automation setup, AI implementation, CRM or calendar integration, website development, migration, consulting or another separately scoped professional service, LINKERNO may process the business information reasonably necessary to scope, configure, test and support that project. Depending on the project, this may include website content, workflow descriptions, form fields, CRM or calendar configuration, integration identifiers, test records, business-process documentation, account contacts and technical logs.

LINKERNO aims to request the minimum project access reasonably necessary for the agreed work. Passwords, API keys and provider credentials should be handled through supported secure configuration methods where available and should not be placed in public website content, ordinary marketing forms or other unnecessary locations. A custom project does not authorize LINKERNO to use business data for unrelated purposes. If a project would require materially different data, regulated information or additional third-party providers, the scope and applicable safeguards should be addressed before production use.

Search and social visibility monitoring

LINKERNO may run automated technical checks against its own public pages or configured customer-facing surfaces to test availability to search-engine and social-preview crawlers, robots directives, sitemap access, canonical metadata, Open Graph, social-card metadata, structured data and related visibility signals. These technical checks do not by themselves reveal private social-account analytics and do not guarantee indexing, rankings, reach or traffic.

How we use business and inquiry information

We use information to create and administer accounts; operate configured communications; prepare and verify business knowledge; organize and route inquiries; provide client-portal views; perform support, security and fraud-prevention functions; scope and deliver agreed professional services; run billing and trial workflows; monitor reliability; troubleshoot errors; improve configured workflows; maintain records; and comply with applicable law.

First-party attribution and analytics

LINKERNO may use first-party cookies or similar first-party identifiers to remember the initial landing page, referring page, campaign parameters and LINKERNO call-to-action selected, such as a trial, demo, scanner or assessment link. This helps us understand which LINKERNO pages lead to requested services. Attribution data is not intended to contain passwords, full payment-card numbers or the text of a private customer inquiry.

Payments and LINKERNO company finance records

Payments may be processed through third-party payment providers. LINKERNO does not need to store full payment-card numbers when payment is handled by an external payment processor. We may store provider customer, subscription, invoice, payment-status or portal identifiers needed to administer billing. For LINKERNO company finance reconciliation, we may also receive provider-confirmed refund and dispute events, their amounts, currencies, statuses or outcomes, and identifiers that connect them to a LINKERNO subscription invoice. We may also receive Stripe-confirmed balance transaction identifiers, gross amounts, processing fees, currencies and transaction dates linked to our own subscription charges. These records are restricted to the company owner and are not combined with client businesses’ customer payments.

Authorized LINKERNO platform owners may also enter company operating-expense records in a restricted administrative ledger. These records may include a date, category, amount, currency, vendor or provider name, a transaction or invoice reference, and whether the owner checked the record against its source. The ledger is for LINKERNO company expenses and is kept separate from client businesses’ customer payment records. It is not a client-facing workspace feature. Owners should not enter card numbers, bank credentials or customer inquiry data in expense fields. These records support accounting, reconciliation, security and legal compliance, and may be retained with other billing and audit records.

Phone provisioning and provider configuration

When a business enables a supported phone connection or requests a new number, LINKERNO may send the minimum configuration information needed to the applicable telephony provider. Provider credentials used by LINKERNO are kept server-side and are not displayed to client users. Paid phone resources are not intended to be provisioned merely because a workspace exists.

Service providers

LINKERNO may use service providers for hosting, telecommunications, AI processing, email, messaging, payment processing, scheduling, security, storage, analytics and automation. Provider availability and the exact provider set may change as infrastructure is tested, replaced or expanded. We aim to provide only information reasonably necessary for each provider’s role.

Retention

We aim to retain routine customer-inquiry records only as long as reasonably necessary for the configured service and related business purposes. Our current operational target is generally no longer than six months for routine inquiry records unless a longer period is needed for security, dispute resolution, legal obligations, account administration or another documented purpose. Business-account, contract, billing, tax, security, project, configuration and audit records may need to be kept longer.

Security

We use reasonable administrative, technical and organizational safeguards appropriate to the information and our stage of operation. LINKERNO includes readiness checks, access controls, provider-health checks, rate limits and guarded automation in parts of the platform. No internet, telecommunications or storage system can be guaranteed completely secure.

Marketing

Information submitted by a caller or website visitor for a service inquiry is not collected for unrelated LINKERNO marketing. A business that receives an inquiry is responsible for using that information lawfully when following up. LINKERNO may separately communicate with businesses that directly request information about LINKERNO, subject to applicable law and communication preferences.

California privacy and privacy requests

California residents may have privacy rights under applicable California law depending on the law and circumstances. Requests for access, correction, deletion or another applicable right can be submitted through the Privacy Request page or by emailing info@linkerno.com. We may need information reasonably necessary to locate the relevant record and verify the request.

Changes to this policy

We may update this policy as LINKERNO’s services, providers and legal obligations develop. The “Last updated” date above shows when this version was revised.

Contact

LINKERNO
13466 Wildrose St
Searles Valley, CA 93562
(323) 677-7643
info@linkerno.com