Skip to main content
Lynka stores operational business data that can include customer details, prospect information, communication history, financial records, support issues, and team activity. The product can provide access controls and data lifecycle tooling, but your business remains responsible for using that data appropriately in the countries where it operates.

​
Give people only the access they need

Teams should use product-area access, action permissions, and record scope rather than giving every employee broad Admin access. This is both an operational and data-governance habit. A salesperson may not need the general ledger. A support user may not need supplier payment information.

​
Prospect data needs care too

LeadGen and imported prospect lists can contain information about people and businesses that are not yet customers. Do not treat prospecting data as exempt from privacy and communication rules. For European data subjects, GDPR and related ePrivacy or national rules may be relevant depending on the data and outreach method. Other countries in your target regions can have their own privacy and communications requirements.

​
Data lifecycle

Lynka has account and workspace lifecycle functions, export workflows, retention support, and access/audit infrastructure in the current backend. Customer-facing policies describe the contractual treatment of data. For legal terms, use: A feature that allows you to store, export, delete, message, or generate a prospect does not by itself determine whether your specific use is lawful. Use the product controls together with the policies and professional advice that apply to your business.
Last modified on September 7, 2026