← Back to Krivyo

Privacy policy

What Krivyo captures, and where it stays

Effective 2 August 2026

01What Krivyo captures

While recording, the extension may process:

• Screenshots of the visible browser tab.
• Click, type, select and screen-change events, including timestamps.
• Element labels, accessibility attributes, selectors, bounding boxes and other metadata needed to create a process guide.
• Typed or selected values needed for the generated documentation.
• Sanitized page context, application name, browser information and recording identifiers.

Passwords, email addresses and recognized sensitive fields are masked. Metadata text is length-limited and common sensitive patterns are redacted. Screenshots can still contain other information visible on the page, so you must review a capture before sharing it.

02How the information is used

The information is used only to build and display the recorded process timeline, generate PDF process documentation, support editing, review and troubleshooting you request, and improve product reliability when optional usage data is enabled.

03Local storage

Recording events and process models are stored in browser extension session storage. Screenshots are stored in the extension's local IndexedDB database. A new capture, restart or empty-capture cleanup clears the prior screenshot set. Your document profile, logos, privacy consent and preferences remain in extension local storage until you change them, clear extension data or uninstall the extension.

04Network transfers

Krivyo does not automatically upload your process screenshots or entered values. Network transfers occur only in these cases:

• Optional usage data: only when enabled, successful PDF downloads and ratings you select may send an installation ID, capture ID, extension version, application name, browser label, step count and rating. No screenshots or entered values are included.
• Issue reports: the report details are sent when you submit the form. Process JSON, diagnostics and captured screenshots are sent only when you select the corresponding attachment options.
• Logo search: using Wikimedia logo search sends the search term to Wikimedia services.

All extension-managed transfers use HTTPS.

05Service providers, sharing and sale

User data is not sold, used for personalized advertising or shared with data brokers. When you submit feedback, the selected report data is sent to a Supabase-hosted feedback service. When you use logo search, the search term is sent to Wikimedia services. Data is otherwise transferred only when needed to provide the feature you requested, for security or legal reasons, or as permitted by the Chrome Web Store User Data Policy.

06Human access

Humans do not review your captured process data unless you explicitly submit it for support, access is necessary for security, access is required by law, or the data has been aggregated and anonymized for internal operations.

07Retention and deletion

Local recording data can be replaced by starting a new capture and can be removed by clearing extension storage or uninstalling Krivyo. Feedback submissions are retained only while needed for support, security and product improvement. To request deletion of submitted feedback, email support@krivyo.in and include the capture ID shown in your report.

08Security

The extension limits metadata length, masks recognized sensitive form fields before screenshots, sanitizes URLs and uses encrypted HTTPS connections for network requests. No system can guarantee that a screenshot contains no sensitive information; users remain responsible for reviewing exported documents before sharing them.

09Limited Use

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

10Changes and contact

Material changes to data practices will be disclosed in the extension before the revised practices take effect. For privacy questions, data-access or deletion requests, email support@krivyo.in.

Krivyo · India · support@krivyo.in