Privacy Policy
Last updated · 14 October 2026
This notice explains how the Linkara browser extension and its supporting service process information to assess hyperlinks.
1. Who operates Linkara
Linkara is currently developed and operated by an individual based in Cyprus. For privacy questions or requests, contact privacy@linkara.eu.
2. Information processed
When Linkara analyzes a hyperlink, the extension sends its destination URL to the Linkara API. A URL may contain path segments, query parameters or other information that could be sensitive or identify a person. The service processes destination and redirect information, hostnames, threat-check outcomes, and technical request information needed to provide the assessment.
The service also processes installation identifiers, hashed installation credentials on the server, short-lived access tokens, organization association where applicable, and installation status and usage timestamps. The extension stores its installation credentials, settings and local usage statistics in browser storage. The service may process IP addresses as part of receiving requests and enforcing request limits.
3. Purposes and legal bases
Information is used to provide link-risk assessments, authenticate installations, administer organization access, prevent abuse, troubleshoot errors and maintain service security. The legal basis depends on the activity and relationship involved. Processing needed to deliver an agreed service may rely on contractual necessity where applicable. Security, abuse prevention and service administration may rely on legitimate interests, subject to applicable law and an appropriate balancing assessment. You can contact us to ask about the basis for particular processing.
4. Threat intelligence and external services
Linkara uses Google Web Risk to check submitted URLs for known malware and social-engineering threats. The complete URL submitted for that check is transmitted to Google's Web Risk API. Linkara also contacts link destinations to inspect redirects and technical characteristics. The backend is hosted using Render, and its production database uses Neon PostgreSQL. These providers may process technical data as part of service delivery under their own applicable terms.
5. Logging, caching and retention
Application-level analysis logs are designed to record hostnames and operational outcomes rather than full submitted URLs, query strings or fragments. The service temporarily caches URL-specific Web Risk results in process memory. Installation and organization records persist in the database to support access management and revocation. Hosting-provider logs and backups may have separate retention periods.
Information is kept only for as long as needed for the purposes described above, including service operation, security, access management and applicable legal obligations. The period varies by record type and provider. Installation records may remain while an installation is active and for a limited period afterward where needed for security or administration. You can contact us to request information about retention or deletion of information associated with an installation.
6. Sharing and international processing
Data may be processed by infrastructure and threat-intelligence providers to deliver the functionality described above. Processing may involve transfers outside Cyprus or the European Economic Area. Where required by applicable data protection law, international transfers must be supported by an appropriate transfer mechanism and safeguards. Contact us for information about the arrangements relevant to your data.
7. Your choices and rights
Users may disable Linkara protection, disable it for selected websites, or remove the extension using browser controls. These actions do not necessarily delete server-side installation records. Subject to applicable law, individuals may request access, correction, deletion, restriction, portability or object to processing. They may also lodge a complaint with the Cyprus Commissioner for Personal Data Protection or another competent authority.
8. Security
Linkara uses HTTPS for API communication, short-lived installation access tokens and server-side checks of installation status. No service can guarantee that every harmful link will be detected.
9. Updates
This policy may be updated as Linkara's features, service providers or processing practices change. The current version will be posted on this page.