Mekari Snap Chrome Extension Privacy Policy

1. Information we handle

Captures and recordings you create

Snap processes screenshots of a selected area, visible tab, or full webpage; screen, window, or tab recordings; and the edits you make, including annotations, redactions, crops, cuts, and voice-over. If you enable them, recordings can include microphone audio, tab or system audio supported by the selected source, and a camera overlay. You choose the capture or recording action and the available inputs.

Captured material can contain personal communications, faces, voices, business information, financial or health information, or other sensitive information that is visible or audible in the selected source. Snap does not need you to provide those categories separately. Avoid capturing information you are not authorized to process or disclose.

Capture metadata and preferences

We handle capture titles, which may initially use the webpage title; capture identifiers; creation and modification times; dimensions; duration; file type and size; upload progress; processing status; edit instructions; and sharing settings. Preferences, local drafts, upload receipts, selected input-device identifiers, and recording-recovery information may be stored in your browser or extension storage. Local creation timestamps may appear in exported recordings.

Account and authentication information

When you connect a Mekari account, Snap obtains a stable provider account identifier, name, and email from Mekari Account and maintains its own user and workspace-admission records. Snap uses authorization codes and short-lived provider credentials on the backend to obtain the profile. It does not retain provider access or refresh tokens after that operation. Snap issues a separate session token for the website or extension; the server stores a hash of that token, while your client stores the usable token.

Your Mekari password and OTP belong on the Mekari Account sign-in page. Snap’s hosted production service does not ask for or receive them. Connecting the extension does not place a long-lived session token in a redirect URL. Snap does not require access to your Google Drive, Gmail, contacts, or Google browsing history.

Operational and security information

Snap records limited authentication, sharing, deletion, and security events, such as internal user or capture identifiers, event type, and time. Diagnostics may include failure stages and technical errors. Hosting and traffic-security providers can receive IP addresses, browser/request information, URLs requested on Snap, and timestamps as part of delivering and protecting the service. This is separate from tracking your browsing across other websites.

Snap does not intentionally place capture contents, passwords, OTPs, authorization codes, or usable session tokens in its application diagnostics. Share links and requests still pass through the infrastructure that delivers them, so treat a share URL as confidential until you intend to share it.

Product usage and reliability

Snap reports feature names and numeric measurements to its own server to improve capture, editing, recording and sharing. Events can include capture mode, client and version, successful or failed actions, recording duration, image dimensions, file size and whether optional recording inputs were enabled. They do not include screenshot contents, captured text, titles, source webpage URLs, keystrokes or raw error messages.

Random installation and viewer identifiers are transformed on the server before storage. Signed-in product events are associated with your Snap account; signed-out activity remains separate. Shared-page events measure visible visits, playback and download clicks, rather than media requests or background refreshes. Viewer-browser counts are estimates, not verified people. The private product dashboard is restricted to the authorized product owner.

You can turn off optional usage analytics in Mac Settings, Chrome extension Settings, the website account menu or the shared-page analytics control. Essential account, upload and share records continue to support the service. Client queues are bounded and expire after 30 days. Raw product events are retained for 180 days; aggregate lifetime counts remain. Existing service audit records follow the retention described below.

2. Why we use information

We use information to perform the capture and recording actions you request; display and edit your drafts; create exports; connect your account; maintain your personal library; resume uploads; deliver and revoke share links; generate previews and video formats; scan uploads for malware; prevent abuse; diagnose failures; respond to support or privacy requests; and meet applicable legal obligations.

Where applicable, processing is based on providing the service you request, your instructions or consent, legitimate operational and security interests where permitted, or a legal obligation. Optional camera and microphone use also requires the relevant browser or operating-system permissions. This notice is not blanket consent for unrelated processing.

Snap does not sell or rent personal data; transfer it to advertising platforms or data brokers; use it for personalized advertising, creditworthiness, or lending decisions; or send captures to AI model APIs for training or analysis. The current Snap website and extension do not include advertising or behavioral-analytics SDKs.

3. Chrome permissions and device access

When you invoke Snap on a webpage, Chrome’s activeTab permission allows Snap to load a helper for selection, full-page capture, and recording overlays on that page. The store extension requests persistent host access only to https://snap.mekari.app/* for account and capture services. It does not automatically load a helper on every website. After navigating to another website, invoke Snap again to restore camera previews and click effects; an ongoing screen recording continues. That access supports capturing the page you choose and showing recording controls; it is not used to build a browsing-history profile or monitor unrelated activity. Snap does not request Chrome’s history permission, collect a separate list of sites you visit, or read bookmarks. A captured page title or visible address can still reveal a website in material you choose to save. Full-page capture may inspect layout and temporarily scroll or adjust the page to assemble the screenshot.

Camera and microphone access is optional and controlled by your settings and browser permissions; permission may be remembered by Chrome. A previously granted permission does not mean Snap is continuously recording. Capture and recording begin through the extension’s capture/record actions, and screen/window selection uses Chrome’s available source picker. Click positions and timing are used for the enabled recording click effects and sound; Snap does not maintain a separate cross-site click-analytics profile or keystroke log. You can disable inputs and effects or revoke permissions in Chrome or your operating system.

4. Local processing and cloud saving

Local captures, recording chunks, thumbnails, and editing drafts are stored in the extension’s IndexedDB. Preferences and client session information use Chrome extension local/session storage; the extension does not use Chrome storage sync. The website uses its own local/session storage for account sessions and pending sign-in proofs. Local capture does not require an account. Downloaded files and copied content are under the control of your device, clipboard, and any applications to which you send them.

Using cloud saving or creating a cloud share link uploads the relevant media, metadata, and any required editing or voice-over material to the configured Snap service. If you have explicitly enabled a cloud destination, that setting can initiate cloud saving for subsequent captures. Uploaded media is processed on the server for the requested features, including malware scanning and preview or video generation. The current malware scan runs within Snap’s server environment rather than submitting the file to an external scanning service.

The extension does not upload all open tabs, a DOM/HTML archive, browser history, or background microphone/camera recordings to the cloud. Cloud requests concern the captures and actions you choose.

An optional local Snap server can receive media for conversion on your own computer and can write processing files there. This is distinct from cloud saving. Changing the configured server address changes the destination of account and cloud requests; only use a server you trust. This notice describes snap.mekari.app, not an independently operated replacement server.

Edits or redactions in an export do not automatically erase earlier drafts, previously uploaded originals, or copies already downloaded. Delete those copies separately when needed.

5. Who can receive information

People holding your share link

Your library is personal; ordinary users do not gain access to it merely by joining the same Mekari workspace. When you enable a share link, anyone with that link can view and download the capture without an account. The shared page can show its title, your display name, creation time, and media metadata. A recipient can forward the link or retain a copy.

Links expire after three calendar months. Re-sharing creates a new link and invalidates the old one. Revoking sharing or deleting the capture blocks new requests using the link, but cannot recall downloaded copies, screenshots, or media already delivered or buffered. Owner-only media URLs issued before revocation may remain valid for their short lifetime, up to 60 seconds.

Service and platform providers

• Mekari Account / Mekari: handles sign-in and provides the account profile used by Snap. Other Mekari services have their own processing practices; see the Mekari Privacy Notice.
• BytePlus / ByteDance cloud infrastructure: hosts Snap’s server, stored media, database, and operational backups. See BytePlus privacy information.
• Cloudflare: routes and protects HTTPS traffic to the hosted service and can process request information and content transmitted through that connection. See Cloudflare’s Privacy Policy.
• Google Chrome and the Chrome Web Store: provide browser capture/permission, extension distribution, and browser identity-flow functionality under their own terms. Installing the extension or using browser features can involve information processed by Google under its own Privacy Policy.
• Recipients you choose: receive files or links when you download, copy, share, or submit them using another application or service.

We limit transfers of extension user data to what is necessary for Snap’s disclosed purpose, security and abuse prevention, compliance with applicable law, or a business transfer with the prior consent required by Chrome’s Limited Use rules. Authorized personnel may read user content only with explicit permission for the specific content, where necessary for security, where legally required, or in aggregated and anonymized form for permitted internal operations. Content you intentionally share with recipients is accessible to those recipients as described above.

6. Retention and deletion

• Local drafts and preferences: remain until you delete them, clear the relevant browser/extension storage, uninstall the extension, or the browser removes stored data. Files downloaded outside extension storage are not deleted by those actions.
• Cloud captures: remain in your personal library until you delete them or request removal. The three-month limit applies to link access, not deletion of the original.
• Capture deletion: removes the active library record, disables access through its share link, and requests removal of its associated server files. It does not remove independent local drafts, recipient copies, or operational backups. Contact us if you need confirmation that all associated stored copies have been addressed.
• Authentication: ordinary Mekari-connected Snap sessions expire after eight hours. Pending login transactions expire after 15 minutes; handoff codes expire after 60 seconds and are single-use. Expired authentication records are cleaned during sign-in housekeeping rather than necessarily at the instant of expiry.
• Account records, security/audit records, and backups: can outlast a capture or session. Capture deletion does not automatically purge them. Retention is limited by their continuing purpose, including account operation, recovery, investigation, or legal obligations; privacy requests trigger a review of the records and copies that must be removed or retained. The current service does not offer a fixed automatic backup-purge deadline.

Where information must be retained for a specific legal or security reason, we restrict its use to that reason. Signing out does not delete captures or drafts. Website and extension sessions are separate; signing out of Snap does not globally sign you out of Mekari Account.

7. Your choices and privacy rights

In the extension you can choose a screenshot area/source, start/pause/stop recording, disable camera/microphone/source audio and click effects, keep material local, delete a capture from local history, and sign out from the account panel. In the web library you can revoke links or delete cloud captures. You can also clear extension data or remove Mekari Snap through Chrome’s extension controls and revoke camera/microphone permissions through Chrome or operating-system settings. Removing the extension does not delete your cloud library. Local and cloud copies must be managed separately.

To request access, correction, export, account deletion, removal of remaining stored copies, or information about retention and processing locations, email policy@mekari.com and identify Mekari Snap and the relevant account. There is currently no self-service account-deletion button. Do not send a password, OTP, session token, or unnecessary sensitive capture contents. We may seek proportionate information to verify authority and locate the relevant records.

Depending on applicable law and the circumstances, you may also have rights to restrict or object to processing, withdraw consent without affecting prior lawful processing, receive a portable copy, or complain to the relevant data-protection authority. We handle requests subject to applicable law, identity/authority verification, and justified retention obligations. An employer’s instructions and applicable agreements may govern workplace data; they do not make another ordinary Snap user the owner of your personal library.

8. Security and international processing

Hosted Snap connections use HTTPS. Snap uses authorization checks, hashed server-side session and share tokens, bounded uploads, malware scanning for hosted uploads, and restricted service access. Snap is not an end-to-end encrypted vault: its server and delivery infrastructure must process uploaded media. No service can guarantee absolute security. Keep devices and accounts secure, and report suspected exposure promptly.

Hosting, support, and traffic-delivery infrastructure may process information outside your country. Applicable cross-border requirements and safeguards depend on the processing context and service arrangements. Contact the privacy team for information relevant to your account; this notice does not promise that all data stays in a particular country.

Snap uses browser storage for essential features rather than advertising cookies. Mekari Account and infrastructure providers may use their own authentication or security cookies. Snap’s current pages do not embed third-party marketing pixels or analytics SDKs.

9. Chrome Web Store Limited Use

Our use of information obtained through Chrome or Google APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. These restrictions also cover derived data. The purpose, transfer, human-access, and prohibited-use limits described above apply to that information.

Other Mekari notices do not broaden these permissions. New uses require prior disclosure and any consent required by applicable law and Chrome policy.

10. Intended audience and other people’s data

Snap is intended for workplace and business use, not directed at children. If you believe a child’s information or another person’s information was submitted without appropriate authority, contact us. You are responsible for having the authority and any permissions needed to capture other people, communications, or confidential material.

11. Changes to this notice

We update this page when Snap’s practices change and identify the effective date above. Material changes will be disclosed through the service or another appropriate channel, with any consent required for the new processing. Publishing a new notice does not itself authorize an otherwise prohibited use of previously obtained extension data.

12. Contact

Mekari privacy team — PT Mid Solusi Nusantara / relevant Mekari operating affiliate
Email: policy@mekari.com
Subject: Mekari Snap privacy request

The Mekari Privacy Notice provides additional corporate contact and privacy information. This page describes Snap’s specific practices and Chrome extension data-use restrictions.