RawFeed Privacy
Privacy Policy
Last updated: May 7, 2026.
This policy explains how RawFeed collects, uses, stores, shares, and protects information across rawfeed.xyz, RawCapture, SEO/GEO audits, Design Studio, news and cyber dashboards, network diagnostics, support, AI-assisted features, billing, and account functionality.
1. Scope
This Privacy Policy applies to RawFeed websites, dashboards, APIs, SDKs, support tools, account features, RawCapture browser trace monitoring, and related services. The RawFeed Chrome extension has additional extension-specific disclosures at /privacy/rawfeed-extension.
RawFeed includes public information tools and developer/monitoring products. Public news, vulnerability, health content may originate from third-party sources. RawFeed does not control those third parties' privacy practices.
2. Information We Collect
Depending on which features you use, RawFeed may collect these categories of information:
Account and profile data
Preferences and saved workspace data
RawCapture project and telemetry data
RawCapture browser events
Integrations and OAuth data
Billing, plan, and usage data
Usage, security, and diagnostics
News, cyber, and health activity
3. Information You or Your Applications Submit
RawFeed receives information you enter directly, such as account details, support messages, preferences, project settings, alert choices, SEO/GEO test inputs, architecture plans, comments, integration settings, and uploaded or submitted content. RawCapture also receives telemetry that you or your application configure the SDK, API, browser plugin, or VS Code extension to send or fetch.
RawCapture project owners are responsible for deciding what their websites, applications, and authorized extension installations collect. Project owners should avoid sending passwords, authentication tokens, payment card data, government identifiers, health information, children's data, or other sensitive personal data unless they have a lawful basis and appropriate safeguards.
4. Cookies, Local Storage, and Similar Technologies
- RawFeed uses cookies for authentication, session continuity, account security, and required site functions.
- Analytics and reliability tools may use cookies, browser storage, or similar identifiers to understand aggregate usage, troubleshoot errors, and improve service performance.
- Some client-side tools store preferences or temporary diagnostic history in your browser's local storage so the feature can work without sending everything to RawFeed servers.
- Browser settings may let you block or delete cookies, but some authenticated or personalized features may stop working.
5. How We Use Information
- Operate, secure, maintain, debug, and improve RawFeed services.
- Authenticate users, maintain sessions, enforce plans, process onboarding, manage support, and administer accounts.
- Fetch, cache, summarize, geocode, rank, and display news, cyber, vulnerability, and health information.
- Run SEO/GEO audits, save scorecards, compare baselines, monitor search optimization signals, and connect RawCapture telemetry to SEO observability workflows.
- Build, save, share, and review Design Studio architecture plans, production pipelines, AI-search crawl paths, and readiness diagrams.
- Process RawCapture events, apply rate limits, enforce origin restrictions, honor ingestion policies, apply scrub rules, power dashboards, support retention controls, measure traffic, and create external issues when requested.
- Meter authenticated SEO/GEO analysis and paid developer workflows, enforce feature gates, and prevent unconfigured billing metadata from granting paid access.
- Send requested alerts, notifications, support replies, account messages, or operational notices.
- Detect abuse, investigate security events, prevent fraud, enforce terms, and maintain audit records.
- Generate AI-assisted summaries, triage, explanations, headlines, and guidance when a feature uses AI.
6. Legal Bases for Processing
Where privacy laws require a legal basis, RawFeed processes personal data under one or more of the following: contract performance, legitimate interests, consent, and legal obligations. Legitimate interests include providing the service, improving reliability, securing systems, preventing abuse, supporting users, preserving audit trails, and operating developer diagnostics.
7. RawCapture Privacy Controls
RawCapture includes controls intended to reduce unnecessary collection: origin-restricted SDK keys, plugin HMAC authentication, VS Code editor connection tokens, event-type allow lists, sampling, collection pause windows, muted endpoints, server-side regex scrub rules, retention settings, delete workflows, encrypted credentials, project scoping, and admin traffic governance for SDK, plugin, and editor traffic.
The optional DOM outline setting is disabled by default. When enabled by a project owner, RawCapture is designed to attach a text-free, attribute-limited page structure summary to error events. It excludes common sensitive elements such as inputs, textareas, selects, iframes, canvas, media, SVG, contenteditable elements, and elements marked as private or sensitive.
8. AI-Assisted Features
RawFeed may use AI services to summarize public content, draft headlines, explain alerts, support RawCapture triage, review Design Studio plans, generate architecture baselines, answer constrained help questions, or provide operational guidance. Inputs to AI features may include the content, URL, diagram summary, or diagnostic context needed for the requested feature. Do not submit confidential or regulated data to AI-assisted features unless you have authority and have reviewed the applicable risk.
9. Sharing and Processors
RawFeed does not sell personal data. RawFeed may share data with:
- Hosting, database, authentication, storage, analytics, cache, email, AI, logging, and monitoring providers.
- Public news, cyber, vulnerability, health-alert, and geolocation data providers used to operate RawFeed features.
- OAuth and workflow providers, such as GitHub or Jira, when you connect an integration.
- Payment, billing, or metering providers if premium, subscription, or overage features are enabled.
- Legal, security, or compliance recipients when disclosure is required by law or needed to protect users, RawFeed, or others.
RawFeed may also disclose information during a merger, acquisition, financing, reorganization, or asset transfer, subject to reasonable continuity of privacy protections where practical.
10. Retention
Retention depends on the feature and the operational need. Account records, support records, preferences, alerts, SEO/GEO scorecards, Design Studio plans, RawCapture projects, telemetry, comments, audit logs, integration metadata, billing metadata, traffic counters, and usage records may be retained until deleted, expired by configured controls, or no longer needed for service, security, legal, billing, or audit purposes.
Cached public-source content may refresh or expire on operational schedules. Backups, rate-limit records, security logs, and legal records may persist for a limited period after live deletion.
11. Security
RawFeed uses technical and organizational measures such as HTTPS, access controls, credential hashing or encryption where appropriate, scoped keys, rate limits, audit logging, row-level security controls, and monitoring. No system can be guaranteed completely secure. You are responsible for keeping account credentials, API keys, provisioning keys, editor connection tokens, OAuth connections, and extension credentials secure.
12. International Transfers
RawFeed and its providers may process information in the United States and other countries where providers operate. Those countries may have privacy laws different from your location. Where required, RawFeed relies on appropriate transfer mechanisms or lawful exceptions.
13. Your Choices and Rights
- You may update many account preferences in the product.
- You may delete or adjust RawCapture projects, retention settings, scrub rules, plugin instances, editor connections, saved SEO/GEO tests, architecture plans, and alert subscriptions where the product supports it.
- You may request access, correction, deletion, restriction, objection, portability, or consent withdrawal where applicable law provides those rights.
- You may contact RawFeed about privacy, deletion, GDPR-style rights, security, or account requests from the account email associated with the request.
RawFeed may need to verify your identity before fulfilling a request. Some records may be retained when required for security, legal, billing, dispute, fraud-prevention, or audit purposes.
14. Children
RawFeed is not directed to children under 13 and is not intended to collect personal information from children. If you believe a child provided personal information to RawFeed, contact us so we can review and delete it when appropriate.
15. Changes
RawFeed may update this Privacy Policy as the service changes. The updated date at the top of the page shows when this page was last revised. Continued use after an update means the updated policy applies to future use.
16. Contact
For privacy, GDPR-style, deletion, security, or account requests, contact RawFeed through the Contact page or from the email tied to your account. Include enough detail to identify the relevant account, project, extension installation, subscription, or data category.
Related policies: RawFeed Privacy Policy and RawFeed Chrome Extension Privacy Policy.