Privacy policy

Horus is operated by Iurii Molodtsov. This policy covers horusintel.app and the Horus MCP connection. For privacy questions or requests, contact app@horusintel.app.

We determine how account, security, support, and shared media-research data are used. When an organization uses Horus to manage its own workspace data, that organization determines the purposes of that processing. Contact your workspace administrator about its use of your information; we can help route your request.

• Account and workspace information: your name, email, authentication records, workspace membership, role, invitations, settings, and support or access-request messages.
• Content you provide: clients, websites, competitors, topics, queries, reports, research notes, professional contact details, follows, tags, and bookmarks.
• Media research: publication feeds, article links and text, bylines, public professional profiles, and reporter details from publications, public websites, search services, or workspace submissions. Horus also produces research summaries and inferred reporter interests from this evidence.
• Results and technical records: briefings, AI responses, coverage results, delivery records, connection permissions, token hashes, request and error logs, and diagnostic information. Web requests may include IP addresses, browser information, and timestamps.

Required account details let us authenticate you and provide access. Without them, we cannot create an account. Do not upload sensitive personal information or data you are not authorized to share.

We use information to provide accounts and shared workspaces, retrieve coverage, create briefings and reports, research reporters, measure AI visibility, operate connections, send requested or configured emails, and respond to support requests.

Where data-protection law requires a legal basis, we rely on performing our agreement with you for account and service delivery; legitimate interests for service security, troubleshooting, product analysis, and relevant professional media research; legal obligations where applicable; and consent where required. We weigh those interests against the rights of the people concerned. You can object to processing based on legitimate interests.

AI-generated profiles and scores support research. They can be inaccurate and are not used by Horus to make solely automated decisions with legal or similarly significant effects on people.

Workspace members can see shared records according to their access. Public report links expose the selected report to anyone with the link until sharing is disabled. Workspace-owned sources and private notes are subject to workspace access controls; they are not automatically added to the shared Watcher Archive.

Service providers process information needed to operate Horus: hosting and database infrastructure, Supabase for authentication, Postmark for email delivery, Tally for access-request forms, and Plausible for website analytics. Depending on the feature and configuration, relevant queries and content are sent to OpenAI, Google Gemini, Perplexity, xAI, or SerpAPI to generate answers or retrieve search results. Not every provider is used for every request.

We may access records to handle support, maintain the service, or investigate security issues. We may disclose information when required by law or necessary to protect people, enforce our terms, or address fraud or abuse.

When you approve an OAuth connection, Horus records the connected application and the permissions granted for your workspace. A connected app can send tool requests and receive relevant workspace data, including clients, coverage, briefings, and reporter research. Some tools can change or delete records within your permissions. A bearer API key also authorizes access: keep it private.

Disconnect an OAuth app or revoke a key from the Horus MCP page to stop future access through that connection. Disconnecting does not erase information already received by the other app. That app handles its copies, conversations, and any further processing under its own terms and privacy policy. Horus does not receive your entire chat history merely because you connect it; it receives the information sent in tool requests.

Horus stores application records in its application database and uses Supabase for authentication. Providers may process information outside your country. Where applicable law requires safeguards for an international transfer, those safeguards must be in place, such as an adequacy decision or approved contractual terms. Contact us for information about the providers and safeguards relevant to your data.

We retain account and workspace records for as long as needed to provide the service and maintain the records you save. Deleting an account does not automatically delete shared workspace records needed by other members. Contact us to request account or workspace deletion and to clarify what will remain.

Retention depends on the purpose of each record, whether it is still needed by an active workspace, and security or legal requirements. Deleted information may remain temporarily in rotating backups. Security, support, and diagnostic records may be kept as needed to resolve incidents, meet legal obligations, or establish and defend claims.

Horus uses authentication cookies and browser storage to keep you signed in and remember interface preferences. The public landing page uses Plausible to measure visits. You can control cookies and stored site data in your browser; blocking authentication storage may prevent sign-in.

Depending on applicable law, you may request access, correction, deletion, a portable copy, or restriction of your personal information, and object to certain processing. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. You may also complain to your local data-protection authority.

Email app@horusintel.app with enough detail to locate the relevant account or record. We may need to verify your identity or authority before acting. Reporters and other people whose professional information appears in Horus can also request access or correction, or object to its use, without having an account. We will explain any applicable limits and respond within the period required by law.

Horus is a professional service intended for adults and is not directed at children under 18. Contact us if you believe a child has provided personal information.

We may update this policy as the service changes. We will publish the revised version here, update its date, and provide additional notice of material changes where required.