Privacy policy

What stays local.
What does not.

This policy explains how Kaptr.me handles account data, saved snapshots, browser-local sessions, sharing and optional AI processing.

Last updated · October 20, 2026Security overview →
LOCALBrowser session & credentialsRemain with the browser used for local capture and refresh.
EU CLOUDAccount, dashboards & saved snapshotsPrimary Firebase data layer configured in Europe.
ENCRYPTEDStored snapshotsHTTPS in transit and provider-managed encryption at rest.
AIAI-submitted contentRemote processing; authorized human review and system improvement may occur.

1. Responsible controller

ControllerActivMedia Diffusion
Address129 Avenue de Genève, Centre Idem 74, 74000 Annecy, France
SIRET914 630 785 00014
Privacy contactcontact@kaptr.me
DPONo dedicated DPO is currently designated; privacy requests use the contact above.

2. Information we collect

2.1 Information you provide

Depending on the features you use, Kaptr.me can process account information such as your email address, username, account preferences, dashboard configuration, subscription or entitlement information, and communications you send to support.

Payment-card details are handled by the payment provider used in the checkout flow rather than being intentionally stored as raw card data by the Kaptr.me marketing site.

2.2 Saved snapshots and dashboard content

When you choose to save content, Kaptr.me processes the screenshot or snapshot and the metadata needed to operate it, which can include the source URL, timestamps, crop or refresh information, dashboard assignment, history and sharing settings. Because you choose what to capture, a snapshot can contain third-party, personal, confidential or otherwise sensitive information.

2.3 Video recordings and video cards

With the Kaptr extension you can make recordings of a browser tab, including meetings (Google Meet), with the tab's sound and, if you choose, your microphone. The video and sound are recorded on your computer and sent directly to your own Google Drive, in a "Kaptr/Videos" folder ("Kaptr/Meetings" for a Google Meet call). Kaptr does not store the video. Apart from the AI recap described below, Kaptr stores only the recording's metadata on your dashboard: its title, the host name of the recorded site (never the full address), the meeting code for a Google Meet call, the start and end dates, its duration, its size, its quality, its processing status, the Google Drive file identifier, the Google account e-mail address that holds the file and the people Kaptr shared it with. These e-mail addresses are stored apart from the recording's card and are readable only by the person who recorded it, never by visitors of a dashboard; they are deleted within a few days after the card is deleted, and with your account. Kaptr keeps a small poster image of each recording (a single frame, about 50 KB) in its own storage to show the card; it is deleted with your account. The video itself stays in your Google Drive. Until a recording has reached Google Drive and you have saved or discarded it, it is kept temporarily in the extension's local storage on your computer and then deleted. The same metadata is kept when you import a Google Meet recording you pick in Google Drive. A video card added to a dashboard stores the provider (YouTube, Vimeo, Loom or Google Drive), the video identifier and its title, never the video.

AI recap of recordings. When the AI recap is on in the extension (Kaptr Business), a speech-only audio copy of the recording is sent to Kaptr's storage (Google Firebase), in files of at most ten minutes, after the recording is saved: after you save it, or when a stopped recording you did not review is saved automatically after 24 hours; its recap is then charged like any saved recording (nothing is sent for a recording you discard). The AI recap is off by default: the extension asks you once, before your first recording, whether to turn it on, and you can change it in its Settings. The audio copy is then transcribed by Cloudflare Workers AI, which also writes the recap (a summary, the decisions, the action items and chapters), as Kaptr's processor. The audio copy is deleted after processing, or after 7 days at most if it is never processed. The transcript and the recap are stored by Kaptr with the recording's card. They are deleted with the card or with your account, and they are visible to the people who can see the video. The video itself stays in your Google Drive.

2.4 Communications

Support messages, privacy requests, billing questions, feedback and feature requests can be retained with the contact information and context needed to answer them.

2.5 Technical and usage information

Kaptr.me and its infrastructure can process technical information needed to deliver, secure and troubleshoot the service, such as IP address, browser and device characteristics, operating system, request or security logs, errors, performance information and feature interactions. The exact information depends on the part of the service being used.

3. Local browser-session boundary

LOCAL SESSION

Your source-site login session stays with the browser performing local capture or refresh.

For extension-based local capture and local refresh, Kaptr.me relies on the session already open in that browser. The service does not need to upload a source-site password or authentication cookie in order to recreate that login on another computer.

If Computer A is signed in to a protected source and Computer B is not, a local refresh from Computer B cannot reproduce Computer A's authenticated session. The browser performing the refresh must itself be able to access the source.

The saved screenshot is different. When you choose to save a capture, the resulting image and operational metadata are sent to Kaptr.me so the snapshot can appear in your dashboard and provide the requested cloud functionality.

Google user data and video recordings

YOUR GOOGLE DRIVE

Recordings stay in your Google Drive; Kaptr only sees the files it creates or that you pick.

With the Kaptr extension you can make recordings of a browser tab, including meetings (Google Meet), with the tab's sound and, if you choose, your microphone. The Google Drive export and video recording features of the Kaptr.me website and extension, separate from the Google Workspace add-on described below, ask Google for the drive.file permission only: Kaptr can open, create and share the files it created in your Drive or the files you explicitly choose with the Google Picker, and no other file. Kaptr uses this access to upload your video recordings, read their processing status and duration, and, when you ask for it through your dashboard settings, let your team members (named readers, only after you save the recording) or anyone with the link (public dashboards, only after the dashboard owner confirms) watch them. Google access tokens are kept in memory for the current browser session only, never stored on Kaptr's servers and never logged.

Kaptr's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Kaptr does not use Google user data to serve advertising, does not sell it, does not use it to train or improve AI models, and does not let humans read it except with your consent, for security purposes, to comply with the law, or when the data is aggregated and anonymized.

Your responsibility when recording. Before you record a call page (Google Meet, Zoom, Microsoft Teams, Webex, Whereby, Jitsi), the extension asks you to confirm that you informed all participants. Whatever the tab, recording people may require informing them and, depending on the country (including under the GDPR in the European Union), a legal basis such as their consent. You decide what you record and remain responsible for it; Kaptr processes the recording's metadata, and, when the AI recap is on, its audio copy, transcript and recap, on your behalf. A recording stops automatically after 3 hours or when the recorded tab is closed and, for Google Meet, when you leave the call or the meeting ends.

Deletion. Deleting a recording card, or your Kaptr account, deletes the metadata Kaptr holds, together with the recording's AI recap and transcript, and deleting your account also deletes the poster image and any audio copy not yet deleted; the video file stays in your Google Drive, where you can delete it. You can remove Kaptr's access to your Google account at any time from your Google Account settings (Security → Third-party apps with account access).

Kaptr.me for Google Docs, Sheets and Slides (Google Workspace add-on)

GOOGLE WORKSPACE ADD-ON

Your Google data: access, use, sharing, protection and deletion

This section applies to the separate Kaptr.me Google Workspace add-on and its Google consent screen. The add-on inserts and refreshes your Kaptr.me snapshots in Google Slides and Google Docs, and previews kaptr.me links in Google Docs, Sheets and Slides. It acts only in the file where you use it. The website and extension's optional Google Drive export and recording features use a separate Google application; they are described in the preceding section.

Google user data we access

Google identity (openid, userinfo.email)For each request to Kaptr.me, the add-on sends a Google-signed OpenID identity token containing your Google account identifier and e-mail address. Kaptr.me verifies the token to identify the Google account and find the Kaptr.me account you linked. This identity token cannot access Google APIs. We do not store or log it.
The open file (presentations.currentonly, documents.currentonly)Inside the Google Slides presentation or Google Docs document where you use the add-on, the add-on reads image markers, image links and layout information needed to count, insert and replace Kaptr.me images. It can insert snapshot images and, for a whole Kapboard, new slides or headings bearing snapshot titles. It does not request access to your other files or send the document's text, file title or a copy of the file to Kaptr.me. Only the Kaptr.me snapshot identifiers found in those image markers are sent when needed to refresh them.
Pasted Kaptr.me links (workspace.linkpreview)When you request a preview of a kaptr.me link in Google Docs, Sheets or Slides, the add-on sends that link to Kaptr.me to obtain its title, image and last-refresh information, subject to your Kaptr.me access rights. Public Kapboards can be previewed without linking an account. The pasted link is processed to answer the request, not stored or logged.
Language (script.locale)The add-on uses the host application's language to display French or English. It does not send your locale to Kaptr.me or store it on the server.
External requests (script.external_request)The add-on uses HTTPS requests to https://kaptr.me to identify the linked account, list its Kapboards and snapshots, prepare time-limited image links, resolve link previews, and download images for insertion or refresh in Google Docs. This permission enables communication with Kaptr.me; it does not grant access to additional Google files. The add-on manifest allows requests only to https://kaptr.me/.

How we use Google user data

We use your Google account identifier to authenticate add-on requests and associate them with the Kaptr.me account you chose to link. If the account is not linked, we display its e-mail address back to you to help you connect the correct account. The open-file markers identify only the snapshots to refresh. A pasted link is used only to return its requested preview. The add-on uses these data solely to provide the visible account-linking, listing, insertion, refresh and preview features described here.

Limited Use. Kaptr.me's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data received through this add-on is not sold, used for advertising or credit decisions, or used to train or improve AI models. The general descriptions of optional AI features elsewhere in this policy do not authorize those uses of Google user data.

With whom we share Google user data

Google provides hosting, authentication and storage for the Kaptr.me add-on backend and processes the identity and account-linking data on our behalf to operate and secure the service. Google's Workspace services also receive the snapshot images and preview information needed to display them inside your file. We do not disclose the add-on's Google user data to advertising platforms, data brokers or AI providers. We do not transfer it for purposes other than delivering the requested features, preventing abuse or meeting applicable legal obligations. Authorized support staff may access specific data only with your consent, when necessary for security or to comply with law, or as aggregated and anonymized information.

The people you allow to access a Google file can see its inserted images under that file's Google sharing settings. Sharing a file does not give its readers your Kaptr.me account credentials. A public Kapboard preview contains information you have made public; removing public sharing removes future public access through Kaptr.me. These choices do not remove copies already inserted into a Google file or saved by another person.

How we protect Google user data

Requests use HTTPS encryption in transit. Stored account-linking data is protected by provider-managed encryption at rest. The backend verifies the Google identity token's signature, issuer, audience and expiration before using it, then checks the linked Kaptr.me account and its access rights for private Kapboards and snapshots. Google access tokens and refresh tokens are not sent to or stored by this add-on's backend. It receives no Google file content or file title. Add-on application logs contain the Kaptr.me account identifier and operational results, never an e-mail address, Google identity token, file title or pasted link.

Private image links use random tokens and expire after 30 minutes. They must be treated as private while valid. These temporary image-link tokens may appear in the image service's request logs because they are part of the requested URL; they are not Google identity or access tokens. Public Kapboard preview images use public links with no expiry and no watermark. Other inserted images carry the Free and Starter watermark unless the account has the watermark-removal right or white-label branding.

Retention, revocation and deletion of Google user data

Request-only data. The Google OpenID identity token, pasted link and open-file marker information are processed only to complete the request; the add-on backend does not persist them. The add-on stores no Google access or refresh token, file content, file name or copy of your presentations or documents.

Account linking. Linking or signing in with Google retains your Google account identifier and e-mail address in the account authentication service for as long as that sign-in method remains linked to your Kaptr.me account. If you also have a password sign-in method, use Settings → Account → Linked Google account on kaptr.me to unlink it. Deleting your Kaptr.me account removes its Google sign-in association. You can also request deletion of Google-linked account data at contact@kaptr.me; we verify the requester's identity and handle privacy requests within the time limits in section 10. We do not retain this Google sign-in association for the general account-data period after account deletion.

Image records and operational logs. The time-limited image-link record identifies the Kaptr.me snapshot and account it serves. Its access expires after 30 minutes; expired image-link records are cleaned up during subsequent exports, and account deletion removes that account's image-link records. Expiry stops access through the link; it does not promise immediate erasure of every technical record. Operational logs are retained for security and troubleshooting under the technical/security-log period in section 9, up to six months. Logs do not contain Google identity tokens, Google e-mail addresses, document content or pasted links. These specific Google-data rules take precedence over general account-data retention elsewhere in this policy.

Your Google file and permissions. Uninstall the add-on in Google Workspace Marketplace → Manage apps, and revoke its authorization at Google Account → Third-party connections. Uninstalling or revoking access prevents further authorized use; it does not delete your linked Kaptr.me account or images already stored in your Google files. Google keeps those images as part of the file under its own terms. Remove them from the file, or delete the file using Google's controls, if you want to remove that copy.

En français : module Kaptr.me pour Google Docs, Sheets et Slides

Cette section concerne le module complémentaire Google Workspace Kaptr.me et son écran de consentement distinct. Il insère et rafraîchit vos snapshots Kaptr.me dans Google Slides et Google Docs, et affiche des aperçus de liens kaptr.me dans Google Docs, Sheets et Slides. Il agit uniquement dans le fichier où vous l'utilisez. Les fonctions facultatives d'export et d'enregistrement vers Google Drive du site et de l'extension utilisent une autre application Google, décrite dans la section précédente.

Données utilisateur Google auxquelles nous accédons

Identité Google (openid, userinfo.email)À chaque requête vers Kaptr.me, le module envoie un jeton d'identité OpenID signé par Google, contenant l'identifiant et l'adresse e-mail de votre compte Google. Kaptr.me le vérifie pour identifier ce compte et retrouver le compte Kaptr.me que vous avez lié. Ce jeton ne donne accès à aucune API Google ; nous ne le conservons ni ne le journalisons.
Fichier ouvert (presentations.currentonly, documents.currentonly)Dans la présentation Slides ou le document Docs où vous utilisez le module, celui-ci lit les marqueurs, les liens des images et les informations de mise en page nécessaires au comptage, à l'insertion et au remplacement des images Kaptr.me. Il peut insérer des images et, pour un Kapboard entier, créer des diapositives ou des titres portant le nom des snapshots. Il ne demande pas accès à vos autres fichiers et n'envoie à Kaptr.me ni texte du document, ni titre du fichier, ni copie du fichier. Seuls les identifiants de snapshots Kaptr.me repérés dans ces marqueurs sont transmis lorsqu'ils sont nécessaires au rafraîchissement.
Liens Kaptr.me collés (workspace.linkpreview)Lorsque vous demandez un aperçu d'un lien kaptr.me dans Docs, Sheets ou Slides, le module transmet ce lien à Kaptr.me pour obtenir son titre, son image et sa date de rafraîchissement, selon vos droits d'accès Kaptr.me. Un Kapboard public peut être prévisualisé sans liaison de compte. Le lien collé sert uniquement à répondre à la demande ; il n'est ni conservé ni journalisé.
Langue (script.locale)Le module utilise la langue de l'application hôte pour afficher le français ou l'anglais. Il ne transmet pas cette information à Kaptr.me et ne la conserve pas sur le serveur.
Requêtes externes (script.external_request)Le module envoie des requêtes HTTPS vers https://kaptr.me pour identifier le compte lié, lister ses Kapboards et snapshots, préparer des liens d'image temporaires, obtenir des aperçus de liens et télécharger les images insérées ou rafraîchies dans Docs. Cette permission permet de communiquer avec Kaptr.me ; elle n'accorde aucun accès supplémentaire à vos fichiers Google. Le manifeste autorise uniquement les requêtes vers https://kaptr.me/.

Utilisation des données utilisateur Google

L'identifiant du compte Google sert à authentifier les requêtes du module et à retrouver le compte Kaptr.me que vous avez choisi de lier. Si le compte n'est pas lié, son adresse e-mail vous est réaffichée pour vous aider à choisir le bon compte. Les marqueurs du fichier ouvert repèrent uniquement les snapshots à rafraîchir. Un lien collé sert uniquement à produire l'aperçu demandé. Ces données servent exclusivement aux fonctions visibles de liaison, de consultation, d'insertion, de rafraîchissement et d'aperçu décrites ici.

Utilisation limitée. L'utilisation et le transfert vers toute autre application, par Kaptr.me, des informations reçues des API Google respectent le Google API Services User Data Policy, y compris les exigences d'utilisation limitée (Limited Use). Les données Google reçues par ce module ne sont pas vendues, ne servent ni à la publicité ni aux décisions de crédit, et ne servent pas à entraîner ou améliorer des modèles d'IA. Les descriptions générales des fonctions d'IA dans cette politique n'autorisent pas ces utilisations des données Google.

Destinataires des données utilisateur Google

Google fournit l'hébergement, l'authentification et le stockage du serveur du module Kaptr.me et traite pour notre compte les données d'identité et de liaison nécessaires au fonctionnement et à la sécurité du service. Les services Google Workspace reçoivent aussi les images de snapshots et les informations d'aperçu nécessaires à leur affichage dans votre fichier. Nous ne transmettons pas les données Google du module à des plateformes publicitaires, des courtiers en données ou des prestataires d'IA. Nous ne les transférons que pour fournir les fonctions demandées, prévenir les abus ou respecter nos obligations légales. Le personnel d'assistance autorisé ne peut consulter des données précises qu'avec votre accord, lorsque la sécurité ou la loi le nécessite, ou sous une forme agrégée et anonymisée.

Les personnes autorisées à consulter votre fichier Google peuvent voir les images qu'il contient, selon ses règles de partage Google. Partager un fichier ne donne pas accès aux identifiants de votre compte Kaptr.me. Un aperçu de Kapboard public contient les informations que vous avez rendues publiques ; retirer le partage public retire l'accès public futur via Kaptr.me. Cela n'efface pas les copies déjà insérées dans un fichier Google ou enregistrées par une autre personne.

Protection des données utilisateur Google

Les échanges sont chiffrés par HTTPS et les données de liaison conservées bénéficient du chiffrement au repos géré par notre hébergeur. Le serveur vérifie la signature, l'émetteur, l'audience et l'expiration du jeton d'identité Google avant son utilisation, puis contrôle le compte Kaptr.me lié et ses droits sur les Kapboards et snapshots privés. Aucun jeton d'accès ou d'actualisation Google n'est transmis ou conservé par le serveur de ce module. Il ne reçoit ni contenu ni titre de fichier Google. Les journaux applicatifs du module contiennent l'identifiant du compte Kaptr.me et des résultats opérationnels, jamais une adresse e-mail, un jeton d'identité Google, un titre de fichier ou un lien collé.

Les liens d'images privées comportent des jetons aléatoires et expirent après 30 minutes ; ils doivent rester privés pendant leur validité. Ces jetons temporaires peuvent apparaître dans les journaux des requêtes du service d'images, car ils font partie de l'URL ; ce ne sont pas des jetons Google. Les images d'aperçu des Kapboards publics utilisent des liens publics sans expiration ni filigrane. Les autres images insérées portent le filigrane Free et Starter, sauf droit de suppression du filigrane ou marque blanche.

Conservation, révocation et suppression des données utilisateur Google

Données propres à une requête. Le jeton d'identité OpenID, le lien collé et les informations de marqueur du fichier sont traités uniquement pour répondre à la requête ; le serveur du module ne les conserve pas. Le module ne conserve aucun jeton d'accès ou d'actualisation Google, contenu ou nom de fichier, ni copie de vos présentations et documents.

Liaison du compte. La liaison ou la connexion Google conserve l'identifiant et l'adresse e-mail de votre compte Google dans le service d'authentification tant que ce moyen de connexion reste lié à votre compte Kaptr.me. Si vous disposez aussi d'une connexion par mot de passe, Settings → Account → Linked Google account, sur kaptr.me, permet de supprimer cette liaison. La suppression du compte Kaptr.me supprime son association de connexion Google. Vous pouvez demander la suppression des données de liaison à contact@kaptr.me ; nous vérifions l'identité du demandeur et traitons les demandes dans les délais indiqués en section 10. Cette association Google n'est pas conservée après la suppression du compte au titre de la durée générale de conservation des comptes.

Liens d'image et journaux opérationnels. L'enregistrement d'un lien temporaire indique le snapshot et le compte Kaptr.me concernés. Son accès expire après 30 minutes ; les enregistrements expirés sont nettoyés lors d'exports ultérieurs, et la suppression du compte retire les enregistrements de liens d'image de ce compte. L'expiration bloque l'accès au lien, sans promettre un effacement immédiat de toute trace technique. Les journaux opérationnels servent à la sécurité et au diagnostic selon la durée prévue pour les journaux techniques en section 9, au maximum six mois. Ils ne contiennent ni jetons d'identité Google, ni adresses e-mail Google, ni contenu de document, ni liens collés. Ces règles propres aux données Google priment sur les durées générales de conservation des comptes indiquées ailleurs.

Votre fichier Google et vos autorisations. Désinstallez le module dans Google Workspace Marketplace → Manage apps (Gérer les applications) et retirez son autorisation dans Compte Google → Connexions tierces. La désinstallation ou la révocation empêche les utilisations autorisées ultérieures ; elle n'efface ni votre compte Kaptr.me lié, ni les images déjà enregistrées dans vos fichiers Google. Google conserve ces images avec le fichier, selon ses conditions. Retirez-les du fichier, ou supprimez le fichier avec les commandes Google, pour enlever cette copie.

4. Why we process information and legal bases

Kaptr.me processes information for purposes that include account creation and authentication, delivering dashboards and saved snapshots, refresh/history functions, sharing, billing, support, fraud and security prevention, service reliability, legal compliance, and product improvement.

ContractAccount, requested product features, saved snapshots, dashboard access, subscriptions and support needed to provide the service.
Legitimate interestsSecurity, fraud prevention, abuse prevention, debugging and service reliability where those interests are not overridden by your rights.
Legal obligationRecords or disclosures that applicable law requires us to keep or provide.
ConsentNon-essential cookies or other processing where consent is legally required.

Remote AI processing needed to return a result you request is distinct from any further use of AI-submitted personal data for training, evaluation or improvement. Where data-protection law requires a separate choice or consent for that further use, Kaptr.me will provide it separately.

5. Captured content and your responsibilities

You are responsible for ensuring that content you capture, store or share can lawfully be used in that way. This includes considering copyright, trademarks, confidentiality, privacy, source-site terms and any permission needed to disclose third-party information.

Kaptr.me does not become the owner of third-party material contained in a snapshot and may remove or restrict content when reasonably necessary to address a valid legal, privacy or rights-holder request.

6. Dashboard visibility and sharing

Private · defaultNew dashboards are private by default.
Shared · invite onlyAccess is limited to invited Kaptr.me accounts. A person not signed in with an invited account cannot view the shared dashboard.
Public · link accessA dashboard can be public. Search-engine indexing is a separate setting, so a public dashboard can remain non-indexed.

When you change visibility, you are responsible for ensuring the people who gain access are permitted to see the information displayed in the dashboard.

Kaptr in ChatGPT (ChatGPT app)

CHATGPT APP

ChatGPT only reaches your Kaptr account after you allow it, and you can disconnect it at any time.

The Kaptr app for ChatGPT lets you find your dashboards and build them from a ChatGPT conversation. It is optional and only starts when you connect it from ChatGPT and click Allow the connection on kaptr.me. Your Kaptr password is never shared with ChatGPT.

What ChatGPT can access. Once you allow it, ChatGPT can identify your Kaptr account (name and e-mail address), read your dashboards, captures and AI results, create dashboards and delete empty ones, run captures (with or without Kaptr AI) of the pages you ask for, import background images from links you give, and change the design of your dashboards (background, texts, shapes, arrows and the layout of captures). AI captures started from ChatGPT use your Kaptr credits, like those started in Kaptr.

What OpenAI receives. The information Kaptr returns to answer your requests (for example dashboard names, capture images and AI results) becomes part of your ChatGPT conversation. OpenAI processes it under its own terms and privacy policy, as an independent service you chose to use; Kaptr does not control how OpenAI uses or keeps your conversations.

Connection data Kaptr keeps. Kaptr stores the authorization you gave (your account, the access granted and its dates). Access tokens last one hour and the authorization 30 days unless it is renewed by use; tokens are stored only as one-way fingerprints, never in readable form.

Disconnecting and deletion. You can disconnect Kaptr in ChatGPT's app settings at any time. Deleting your Kaptr account deletes these authorizations, the requests made from ChatGPT and the background images imported for you. Dashboards and captures created from ChatGPT are ordinary Kaptr content: they stay in your account until you delete them.

7. Service providers, AI processing and international transfers

Kaptr.me uses service providers by function. Google Firebase provides core cloud infrastructure used for account and saved dashboard data; the primary Firebase data layer is configured in Europe. Stripe can process subscription payments. Cloudflare runs Kaptr's AI processing (Cloudflare Workers AI), including the transcription and recap of video recordings when the AI recap is on. Charla is loaded on the Documentation page to provide the help center.

AI PROCESSING

AI features are not local-only processing.

When you deliberately use an AI feature, content supplied to that feature — including material an AI workflow finds and captures before inserting it into your dashboard — may be sent to external AI processing systems. Authorized human reviewers may have access to submitted content, and the content may be used to train, evaluate or improve AI systems.

Optional AI processing or reviewer access can involve processing outside the European Economic Area. Where personal data is transferred internationally, the transfer must use the mechanism and safeguards required for the provider and destination concerned.

Kaptr.me does not sell personal data. Information may be shared with processors only for the service functions described here, or disclosed where law requires it.

CONSENT-BASED SERVICES

Analytics and advertising providers remain disclosed where a Kaptr.me surface enables them.

The currently published Kaptr.me production policy identifies Google Analytics for audience measurement and Google Ads and Meta Pixel for advertising or remarketing, subject to the consent rules that apply to those non-essential technologies. The static marketing template does not intentionally load those trackers, but any Kaptr.me surface that enables them must keep them disabled until the required consent is obtained.

8. Data security

Kaptr.me uses technical and organizational measures appropriate to the service. Saved Firebase data is protected by HTTPS in transit and provider-managed encryption at rest, together with authentication and access-control mechanisms. Dashboards are private by default and sharing requires an explicit visibility choice.

No online service can guarantee absolute security. If you believe an account, dashboard or public link has been compromised, contact contact@kaptr.me.

9. Data retention

Information is retained only for as long as it is needed for the purpose for which it is processed, to operate the account, handle disputes or security incidents, and satisfy applicable legal obligations. Retention can differ by data type.

Account dataFor the life of the account, plus 3 years after deletion where needed for service, legal or contractual purposes.
Saved snapshotsFor the life of the account, followed by up to 30 days after account deletion for the deletion and recovery cycle.
Billing records10 years from the transaction date where required for French accounting and tax records.
Analytics dataUp to 14 months where consent-based Google Analytics is enabled.
Advertising cookiesUp to 13 months where consent-based Google Ads or Meta Pixel technologies are enabled.
Technical/security logsUp to 6 months for security, troubleshooting and performance monitoring.
Support communicationsUp to 2 years after the last interaction where needed for customer service or legal follow-up.

If a more specific retention period is presented for a feature or required by law, that period applies.

10. Your data-protection rights

Where the GDPR applies, you can have rights of access, rectification, erasure, restriction, portability and objection, as well as the right to withdraw consent where processing relies on consent. You can also lodge a complaint with the competent supervisory authority; in France, this is the CNIL.

Send requests to contact@kaptr.me. We may ask for information reasonably necessary to verify identity when there is genuine doubt. Requests are handled without undue delay and, in principle, within one month; that period can be extended by up to two additional months for complex or numerous requests when the person is informed within the first month.

11. Children and age restrictions

The Kaptr.me Chrome extension is intended for users aged 15 or older unless the required parent or legal guardian authorization has been obtained. If we learn that personal data was collected in circumstances that do not satisfy applicable child-data requirements, we may restrict the account and take appropriate steps regarding the data.

12. Third-party websites and services

Kaptr.me can display or capture information originating from third-party websites, and its pages can link to third-party services. Those third parties operate under their own terms and privacy notices. Kaptr.me is not responsible for their independent processing practices.

A video card or a video recording on a dashboard shows a thumbnail or poster image; the provider's player (YouTube through its privacy-enhanced youtube-nocookie.com domain, Vimeo, Loom or Google Drive) loads only when you press play, and the provider then processes your visit under its own privacy notice.

13. Legal disclosures, business changes and no sale of data

Information may be disclosed when required by a valid legal or regulatory request, or when reasonably necessary to protect rights, safety, security or the integrity of the service. If the business or service is reorganized, merged, acquired or transferred, relevant information may form part of that transaction subject to applicable law and notice requirements.

Kaptr.me does not sell personal data to third parties.

14. Changes to this policy

This Privacy Policy can be updated to reflect product, provider, legal or security changes. The current revision date is displayed on the page. Material changes will be communicated through the website, account or email where required by law, and a new consent choice will be requested where the law requires one.

15. Contact

ActivMedia Diffusion
129 Avenue de Genève, Centre Idem 74
74000 Annecy, France
SIRET 914 630 785 00014
contact@kaptr.me