Privacy Policy

This Privacy Policy explains how Blink Intelligence LLP ("Blink," "we," "us," or "our") collects, uses, stores, discloses, and otherwise processes personal data and related information in connection with the Blink platform, including our web applications, mobile applications, desktop applications, collaboration tools, AI-powered meeting intelligence features, integrations, and related services (collectively, the "Service").

This Privacy Policy is intended primarily for business and organizational use of Blink. Blink is designed as a B2B collaboration, productivity, and meeting intelligence platform used by companies, teams, and other organizations through managed workspaces.

By accessing or using the Service, you acknowledge that personal data may be processed as described in this Privacy Policy.

1. About Blink

Blink is a collaboration and AI-powered organizational productivity platform that helps organizations manage meetings, communication, knowledge, tasks, decisions, and workflows. Depending on customer configuration, Blink may provide features such as:

meeting recording and transcription;
AI-generated summaries, tasks, decisions, and action items;
workspace collaboration and project tracking;
task and workflow management;
calendar and email-related integrations;
organizational knowledge and retrieval tools;
reporting, analytics, and administrative controls.

Blink may be deployed in different technical environments, including cloud, on-premise, and hybrid deployments, depending on the customer’s infrastructure and commercial arrangement.

2. Scope of This Privacy Policy

This Privacy Policy applies to personal data processed in connection with:

Blink web applications and dashboards;
Blink mobile applications;
Blink desktop applications;
AI-powered meeting and collaboration features;
integrations with third-party services;
customer-managed and organization-managed workspaces;
customer deployments, including cloud, on-premise, and hybrid environments;
support, security, and service administration activities related to Blink.

This Privacy Policy does not govern third-party products, services, websites, or platforms that may integrate with Blink but are operated independently by third parties. Those services remain subject to their own privacy notices, terms, and practices.

3. Data Roles and Responsibilities

3.1 Organizational Use

Where Blink is used by a company, team, institution, or other organization under a managed workspace or commercial arrangement, that organization generally acts as the owner and administrator of the workspace and is typically responsible for determining the purposes for which Blink is used within its operations.

In such cases, Blink generally processes data in order to provide the Service to the customer organization, support workspace functionality, ensure security and reliability, and perform other service-related operations described in this Privacy Policy and any applicable commercial agreement.

3.2 Customer Responsibilities

The customer organization is responsible for:

determining whether Blink is appropriate for its intended use cases;
ensuring it has a lawful basis to use Blink in its business environment;
providing required notices to employees, contractors, participants, or other users;
obtaining any required consents for recording, transcription, monitoring, analysis, or sharing of communications;
configuring access controls, retention settings, and administrative permissions appropriately.

3.3 Blink Role

Blink acts as the service provider and operator of the platform and processes data as necessary to provide, secure, maintain, support, and improve the Service, subject to applicable law and contractual arrangements.

3.4 No Consumer-Focused Offering

Blink is primarily a B2B and organization-focused platform. It is not intended as a general-purpose consumer application for children or personal social use.

4. Categories of Information We Process

Depending on how the Service is configured and used, Blink may process the following categories of data.

4.1 Account and Identity Information

We may process:

full name;
work email address;
organization, team, or workspace affiliation;
job title or role, where provided;
profile photo or avatar;
login identifiers;
authentication and access-related identifiers;
account preferences, settings, and permissions.

4.2 Workspace and Collaboration Data

We may process:

workspace names and identifiers;
project structures and collaboration spaces;
meeting notes;
tasks, subtasks, statuses, assignments, and workflow updates;
kanban boards, project plans, and internal collaboration records;
decisions, action items, comments, and related operational content;
documents, files, attachments, and text content uploaded to or created within Blink.

4.3 Meeting and Communication Data

Where meeting-related features are enabled by the customer or user, Blink may process:

audio recordings;
transcripts of meetings or conversations;
attendee names and email addresses;
chat content exchanged within supported workflows;
meeting summaries and recaps;
AI-generated tasks, decisions, insights, and action items;
related metadata such as timestamps, duration, participants, and organizer information;
screen-shared content, where supported and enabled.

4.4 Calendar and Scheduling Data

Where integrations are enabled, Blink may process:

calendar events;
meeting titles;
invitee and organizer details;
date and time information;
scheduling metadata;
availability-related metadata made available through the relevant integration.

4.5 Technical, Device, and Usage Information

To operate and secure the Service, we may process:

IP address;
approximate geographic location inferred from network activity;
device type and device identifiers;
operating system and version;
browser type and version;
app version;
crash data and diagnostic information;
service telemetry;
authentication events;
access logs;
session-related data;
user interaction logs relevant to product operation, security, or troubleshooting.

4.6 Administrative and Audit Data

We may process:

administrator actions;
permission changes;
user provisioning and removal events;
workspace-level settings changes;
export events;
access-control logs;
audit trails necessary for security, compliance, and incident investigation.

4.7 Support and Communications Data

Where you contact us or interact with our support channels, we may process:

contact details;
organization details;
issue descriptions;
support messages and attachments;
troubleshooting materials;
service communications related to security, billing, product changes, and legal notices.

5. Sources of Information

Blink may receive information from the following sources:

directly from customer organizations and authorized users;
from workspace administrators;
from users interacting with the Service;
from customer-configured integrations;
from devices, browsers, and applications used to access Blink;
from service logs and product telemetry;
from customer communications with Blink support or account teams.

6. Permissions and User Control

Blink seeks access only to the extent reasonably necessary to provide the requested functionality of the Service.

Depending on the platform and feature set, Blink may request access to:

microphone, for recording and transcription;
calendar, for scheduling and meeting integration;
notifications, for reminders, alerts, and product updates;
other system permissions that are clearly tied to a user-initiated product feature.

Users and organizations can control or revoke many permissions through:

device settings;
operating system controls;
workspace settings;
admin controls;
configuration of relevant integrations.

The customer organization remains responsible for ensuring that use of Blink features is lawful in the context in which they are enabled.

7. Recording and Microphone Use

7.1 User-Initiated Recording

Blink accesses the device microphone only when recording or transcription features are explicitly initiated within the Service by the user or by a clearly configured meeting workflow.

7.2 No Hidden Listening

Blink does not perform undisclosed background listening or continuous audio monitoring outside the context of a user-initiated or clearly indicated session.

7.3 Recording Indicators

When recording is active, Blink is intended to provide visible status indicators within the application interface so that users are aware that recording or transcription is in progress.

7.4 User Control

Users may stop recording at any time through available controls, subject to the technical design of the feature and any workspace rules established by the customer organization.

7.5 Customer Responsibility for Notice and Consent

The customer organization and relevant users are responsible for:

determining whether recording is lawful;
notifying participants where required;
obtaining any necessary consent or other lawful basis for recording and transcription.

Blink does not provide legal advice on whether consent is required in any particular jurisdiction or context.

8. Call and Meeting Recording Clarification

Blink does not intercept, record, or monitor ordinary phone calls, messages, or device-level communications outside the intended operation of Blink features.

Recording functionality applies only to:

meetings;
sessions;
collaboration contexts;
or integrated workflows

that are enabled through Blink or through supported integrations with user or customer awareness.

Blink does not access unrelated personal device communications outside the scope of the Service.

9. Purposes of Processing

Blink processes information for the following purposes:

9.1 To Provide the Service

Including to:

create and manage workspaces and user accounts;
authenticate users;
enable collaboration features;
support meetings, note-taking, task management, and workspace operations;
provide AI-powered outputs such as summaries, recaps, tasks, and decisions;
support integrations requested by the customer.

9.2 To Operate, Maintain, and Improve the Service

Including to:

monitor reliability and availability;
troubleshoot technical issues;
diagnose service failures and bugs;
improve usability, functionality, and product quality;
optimize system performance.

9.3 To Secure the Service

Including to:

detect, prevent, and investigate fraud, abuse, and unauthorized access;
maintain logs and audit trails;
enforce security controls and access restrictions;
identify suspicious or malicious activity;
protect Blink, our customers, and users.

9.4 To Communicate With Customers and Users

Including to:

respond to support requests;
send product, operational, billing, and legal notices;
provide service-related updates;
communicate changes to policies or functionality.

9.5 To Comply With Legal and Regulatory Obligations

Including to:

respond to lawful requests from courts, regulators, or authorities;
maintain business records;
enforce our legal rights and contractual terms;
protect against legal claims and security incidents.

9.6 To Improve Internal Models and Performance Using De-Identified Data

Blink may use aggregated and de-identified data to improve system performance, internal analytics, operational reliability, and product functionality, provided that such use does not involve identifiable customer content being used in a manner inconsistent with this Privacy Policy or applicable law.

10. AI Processing and Transparency

Blink uses artificial intelligence and automated analysis technologies to support productivity and collaboration features.

AI-related processing may include:

speech recognition and transcription;
natural language understanding;
summarization of meetings and discussions;
extraction of tasks, action items, and decisions;
contextual retrieval and semantic search;
structuring and classification of collaboration data.

AI functionality operates on data that customer organizations and authorized users choose to submit, record, upload, connect, or otherwise make available to the Service.

AI-generated outputs are probabilistic and may contain:

inaccuracies;
omissions;
misclassifications;
incomplete interpretations.

For that reason:

AI outputs should be reviewed by users;
they should not be treated as inherently complete or error-free;
customer organizations remain responsible for decisions made using the Service.

Blink does not represent that AI outputs are a substitute for professional, legal, financial, HR, or compliance review.

11. AI Training, Data Isolation, and Improvement Practices

Blink does not use identifiable customer content as general-purpose shared training data for external or public models.

Our general principles include:

no cross-customer data mixing for customer-facing outputs;
logical isolation by organization or workspace;
role-based internal access controls;
segmentation of customer environments according to deployment model and configuration.

Blink may use aggregated and de-identified data to:

improve service quality;
enhance reliability and performance;
improve internal analytics;
support product development and operational optimization.

Where applicable, customer organizations may request additional information regarding Blink’s handling of AI-related processing through commercial or legal channels.

12. Workspace Administration and Organizational Controls

Where Blink is used in an organization-managed environment, workspace administrators may have the ability to:

add, provision, suspend, or remove users;
configure workspace settings and permissions;
manage projects, teams, and access rights;
review activity occurring within the workspace;
manage retention or deletion settings where available;
export certain workspace data where such functionality is enabled;
administer or oversee content and collaboration activity within the workspace in accordance with the customer organization’s internal rules and applicable law.

Users of organization-managed workspaces should understand that their use of Blink may be visible to or managed by their organization’s administrators.

Blink is not responsible for the internal governance choices of customer organizations, including how they configure administrator permissions or internal monitoring policies.

13. Legal Basis and Lawful Processing

Blink is designed primarily for business use in the Republic of Kazakhstan. We process personal data as necessary to:

provide and operate the Service;
perform contractual obligations and pre-contractual steps;
protect legitimate business and security interests;
comply with applicable legal obligations;
rely on consent where required by law or product design.

Where the customer organization is responsible for determining how Blink is used in its environment, that organization remains responsible for ensuring that an appropriate lawful basis exists for the relevant processing activities.

14. Sharing and Disclosure of Information

Blink does not sell personal data.

We may disclose or make data available in the following circumstances.

14.1 Service Providers and Technical Partners

We may share data with service providers, hosting providers, infrastructure partners, security vendors, support providers, and other technical subprocessors that assist us in operating and securing Blink, subject to contractual confidentiality and data protection obligations.

14.2 Customer-Enabled Integrations

If a customer enables integrations with third-party systems, data may be exchanged with those systems as necessary to provide the requested functionality.

14.3 Within the Customer Organization

Data within a workspace may be accessible to the customer organization and its authorized administrators in accordance with the customer’s configuration and internal governance.

14.4 Legal and Compliance Requests

We may disclose information where we reasonably believe disclosure is necessary to:

comply with applicable law;
respond to lawful requests from governmental authorities, courts, or regulators;
enforce our contractual rights;
investigate fraud, security incidents, or misuse of the Service;
protect the rights, safety, property, systems, users, customers, or Blink.

14.5 Corporate Transactions

We may disclose or transfer information in connection with an actual or proposed merger, acquisition, restructuring, financing, sale of assets, reorganization, or similar corporate transaction, subject to appropriate confidentiality and data protection safeguards.

14.6 Professional Advisers

We may disclose information to legal, financial, audit, insurance, or professional advisers where reasonably necessary for legitimate business purposes and subject to confidentiality obligations.

A list of subprocessors may be made available upon request.

15. International and Cross-Border Processing

Blink is currently structured with a Kazakhstan-first privacy posture, and data is generally intended to be processed and stored in Kazakhstan, subject to the customer’s deployment model and infrastructure configuration.

In some cases, limited cross-border processing or access may occur, including where necessary for:

technical support;
infrastructure operations;
security operations;
integrated service functionality;
lawful business continuity measures;
customer-requested configurations.

Where cross-border processing is required, Blink applies reasonable contractual, organizational, and technical safeguards appropriate to the nature of the data and the applicable legal requirements.

16. Data Storage and Security

Blink implements reasonable and industry-aligned technical and organizational measures designed to protect personal data and workspace information.

These measures may include:

encryption in transit;
encryption at rest;
role-based access controls;
least-privilege access principles;
audit logging;
monitoring and alerting;
authentication controls;
internal access restrictions;
vulnerability management practices;
backup and recovery procedures appropriate to the deployment model.

Depending on the deployment model, Blink may be operated in:

cloud environments;
customer-controlled on-premise environments;
hybrid environments.

No system or transmission method can be guaranteed to be completely secure. Accordingly, Blink does not guarantee absolute security, uninterrupted operation, or complete immunity from unauthorized access, technical failure, or malicious activity.

17. Retention of Data

Blink retains personal data and related records only for as long as reasonably necessary to provide the Service, maintain security, support legitimate business operations, and comply with legal obligations.

Unless otherwise agreed with the customer organization or required by law, Blink generally applies the following retention approach:

Account and workspace access data: retained for the duration of the active customer relationship and for a limited period thereafter as reasonably necessary for security, dispute resolution, and administrative continuity.
Meeting recordings, transcripts, summaries, and collaboration content: retained for the duration of the workspace lifecycle or until deleted by the customer organization or authorized user, subject to technical retention cycles and backup windows.
System logs, access logs, and security telemetry: generally retained for up to 180 days, unless a longer period is required for security investigations, legal holds, or compliance purposes.
Support-related records: retained for as long as reasonably necessary to resolve issues, maintain service history, and protect legal interests.
Billing, finance, and accounting records: retained for the period required by applicable law and standard financial recordkeeping requirements.
Backups: retained according to internal backup schedules and overwritten or deleted in the ordinary course, subject to recovery, security, and business continuity needs.

Because Blink is a B2B platform, retention may also be influenced by:

customer instructions;
contract terms;
deployment model;
workspace administration settings;
legal preservation requirements.

18. Deletion Requests

Customer organizations and authorized workspace administrators may request deletion of data, subject to:

technical feasibility;
applicable law;
security and fraud-prevention needs;
legal holds;
contractual obligations;
backup and archival cycles.

Deletion may not be immediate in all cases, and residual copies may remain for a limited period in backups, logs, or disaster recovery systems before being overwritten or securely removed in the normal course.

Where a user is part of an organization-managed workspace, deletion requests may need to be submitted through the relevant customer organization or workspace administrator.

19. Rights and Requests

Subject to applicable law, individuals may have rights relating to their personal data, including the right to:

request access to personal data;
request correction of inaccurate information;
request deletion where appropriate;
object to or request restriction of certain processing;
request portability where applicable;
withdraw consent where processing is based on consent.

Because Blink primarily operates in organization-managed B2B environments, requests concerning workspace data may need to be handled in coordination with the relevant customer organization.

Requests may be submitted to: info@blink.pm

Blink may need to verify the identity and authority of the requester before taking action on a request.

20. Automated Decision-Making

Blink does not use fully automated decision-making that is intended to produce legal or similarly significant effects on individuals without meaningful human involvement.

AI-generated outputs provided by Blink are assistive in nature and are intended to support human productivity, not replace human judgment.

21. Children’s Privacy

Blink is not intended for individuals under the age of 18.

Blink does not knowingly offer the Service directly to minors. If a customer organization enables use involving individuals under 18, that customer organization is solely responsible for ensuring that it has all necessary legal bases, notices, permissions, and safeguards required under applicable law.

If Blink becomes aware that personal data has been processed in violation of this section, we may take steps to restrict, delete, or otherwise address such data as appropriate.

22. Security Incidents and Breach Response

Blink maintains internal processes intended to identify, assess, contain, and respond to security incidents affecting the Service.

If Blink determines that a data breach or security incident requires notification under applicable law or contractual obligation, Blink will provide notice to the affected customer organization or other relevant party within a reasonable time and in accordance with applicable legal requirements and operational constraints.

The customer organization remains responsible for any downstream notifications it is required to make to employees, participants, customers, regulators, or other individuals, unless otherwise agreed in writing.

23. Business Transfers

In the event of a merger, acquisition, financing, due diligence process, corporate reorganization, sale of company assets, bankruptcy, or similar transaction, personal data and related service records may be transferred to a successor, acquirer, investor, or affiliated entity as part of the transaction, subject to confidentiality obligations and appropriate continuity of privacy protections.

24. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

changes in the Service;
changes in legal or regulatory requirements;
changes in security practices;
changes in data handling operations;
changes in integrations, deployment models, or organizational structure.

When material changes are made, Blink may provide notice through the Service, by email, through workspace administrators, or by other reasonable means.

The updated version will become effective upon posting or on the date stated in the revised Privacy Policy.

25. Contact Information

If you have questions, privacy requests, or concerns regarding this Privacy Policy, please contact:

Blink Intelligence LLP

Kazakhstan, Astana, Nura District,

Shyngys Aitmatov Street, Building 38, Apt. 256, 010000

Email: info@blink.pm

A Data Processing Agreement and a subprocessors list may be made available upon request where applicable.