Privacy Policy

1. Who this policy covers

This policy applies to visitors, prospective and active clients, engineer applicants and network members, and authorized users of OUTSEED workspaces. OUTSEED acts as the controller of information collected through this website unless a separate client agreement states otherwise.

2. Information we collect

We collect information you provide directly, including:

• Client account details such as name, business email, organization, authentication settings, and workspace activity.
• Project-request details such as objectives, technologies, coverage needs, budget context, messages, approvals, tasks, and recorded delivery time.
• Engineer application details such as identity and contact information, professional history, skills, certifications, availability, location or timezone, screening responses, and engagement activity.
• Communications, support requests, and feedback sent to OUTSEED.
• Account-free inquiries, voluntarily supplied referral/source information, supporting documents, quote decisions, follow-up messages and notification-delivery records.

We also process limited technical information needed to run and secure the service, such as IP address, device and browser information, sign-in events, security audit records, and session identifiers.

3. How we use information

We use information to review and respond to project requests, vet and match engineers, arrange approved introductions, prepare plans and commercial proposals, provide and monitor services, maintain account security, prevent misuse, support users, meet contractual and legal obligations, and improve the reliability of the platform.

We do not sell personal information. We do not use project-request or engineer-application information for unrelated advertising.

4. Engineer identity and controlled introductions

Clients initially see capability-based profiles without private identity details. OUTSEED may share an engineer's identity and direct professional details only after the engineer accepts an assignment and OUTSEED approves the introduction, or another lawful basis applies. Engineers should not include client-confidential information in profile fields.

5. Project and security data

Project requests are reviewed by OUTSEED and relevant assigned engineers. Do not place passwords, private keys, access tokens, production datasets, patient records, payment-card data, or other secrets in a request form. Sensitive delivery information should be exchanged only through an approved channel and under the applicable client agreement.

6. Service providers and disclosures

We may disclose information to vetted engineers and subcontractors who need it for an approved engagement, and to providers that support hosting, authentication, communications, security, and business operations. These recipients are limited to the information reasonably needed for their role. We may also disclose information when required by law, to protect rights or safety, or as part of a business reorganization subject to appropriate safeguards.

7. International processing

OUTSEED supports remote cross-border delivery, so information may be processed outside your country. Where required, we use contractual or other recognized safeguards for international transfers. A client agreement may impose additional residency or access restrictions for project data.

8. Retention

OUTSEED AI uses Cloudflare Workers AI. Questions and evidence from the resources you select are sent to Cloudflare for inference through authorized MCP tools. Collected evidence may be used while a connector is offline and is identified by its observation time. Fresh reads require the connector online. AI execution context and answers follow the temporary execution and explicit-save periods described below. Model/tool progress and source references are account-scoped. Free-usage accounting stores the UTC day, account/feature scope, conservative reserved compute units and request time, without question or evidence text, for 30 days. The application shares a conservative daily budget across its Workers AI features; Cloudflare’s free allocation is account-wide and is also affected by independent applications in the same Cloudflare account.

Standard read-only monitoring is provisioned automatically when an End user connector reports supported infrastructure connections. You can pause automatic coverage, exclude individual checks, and separately enable email alerts. The infrastructure dashboard keeps the latest bounded, encrypted inventory and diagnostic snapshot per connection and resource category for up to 30 days after collection. Snapshots include selected inventory fields, diagnostic findings and bounded output from fixed read-only commands; they can contain hostnames and infrastructure identifiers. They are accessible only within the owning End user account. Partial discovery and stale evidence are marked. These snapshots are separate from temporary interactive requests and explicitly saved AI conversations.

The Windows collector keeps infrastructure credentials locally; an Ubuntu collector is Coming soon. After an authorized infrastructure connection is synchronized, OUTSEED automatically queues every advertised read category and saves normalized, encrypted owner/profile/category evidence for30days. Collection status records category progress, attempts, timestamps, partial coverage and bounded error codes. Source paging and permission limits remain explicit. Saved evidence remains available for authorized AI queries while the collector is offline. Pausing automatic coverage or excluding checks stops the corresponding automatic work.

The optional local Grype scanner downloads a public vulnerability database to the Windows collector and matches observed Linux package metadata locally. Approved Trivy MCP endpoints receive only their locally configured image/project target; namespaced Trivy Operator reads use the configured cluster credentials and scope. Model requests cannot supply a process command, filesystem target or credential override.

Supported security assessments run initially and daily while automatic coverage is enabled; you may exclude each connection or pause collection. Normalized security findings, product/package versions, source references, freshness and coverage metadata are encrypted and retained privately for up to30days. Up to1,000prioritized findings are retained. Partial, stale, failed or unavailable scans do not clear earlier retained findings. Critical findings can create in-app incidents and email notices when alerts are enabled. Public OSV enrichment sends only an advisory identifier already observed for your selected profile, not your private package inventory. Scanner/source-provided KEV or EPSS values are context, not proof of exploitation.

New free trials start once at the first successfully saved infrastructure connection accepted by OUTSEED; prior trial and paid records retain their original dates. Crypto renewal is manual, with no automatic wallet or service-credit debit. Immutable quotes, verified on-chain receipts and credit events retain their actual original values for financial audit. Verified-email transactional access reminders use expiry-stage delivery records. Visa/Mastercard checkout is not active while Whish integration is coming soon.

End user access is a separate role under your existing login. Monitoring runs while your browser is closed, using the Windows connector for read-only collection. Monitoring samples store check outcomes and numeric measurements rather than raw evidence; the separate encrypted inventory snapshots described above support diagnostic drill-downs. Samples and resolved incidents expire after 30 days. Active incidents remain until resolved, and their retention is refreshed while active. Excluding an automatic check stops collection without recreating it on the next heartbeat. Removing a custom monitor removes its samples; incident history expires separately. Alerts go to your verified account email through our email provider and appear in your workspace. Delivery retries are bounded; email acceptance does not establish inbox receipt.

OUTSEED Connect retains account-linked activity summaries for 30 days from the activity date. Full AI conversations are not saved automatically: a completed question and answer remain temporarily available for 15 minutes after completion, during which you may explicitly save them. Saved conversations are encrypted, can be opened, exported or deleted in History, and expire 30 days from the original activity date. Intermediate tool messages and raw infrastructure evidence are not copied into saved conversations. Expired temporary content and history are removed by scheduled cleanup every 15 minutes.

OUTSEED AI chat keeps account-owned conversation metadata, category-based or user-edited titles, selected connection scope and run states for30days from chat creation. Unsaved prompt text is encrypted and temporarily available for15minutes; completion makes the answer available for15minutes. Follow-ups use a bounded portion of available prior turns, excluding prior resource scopes no longer selected. Explicit Save chat creates an encrypted transcript snapshot containing the available questions, answers and source references, expiring30days from the original chat creation. Later messages require another explicit save. Saved snapshots can be exported or deleted; deleting a chat cancels its active linked reads and clears its chat/temporary run content. Downloaded exports remain under your control.

Optional vendor MCP connections are configured on the Windows connector using their own endpoint tokens and local target/project scope. Approved read requests and results pass through those vendor servers. The optional normal-user vendor host is separately launched, uses authenticated HTTPS loopback, and starts only a locally configured pinned runtime; the connector service and AI requests cannot supply a process command or download vendor runtimes. Vendor credentials remain local and their respective software/privacy terms apply. Operational evidence is normalized before it is sent to OUTSEED.

The Windows connector caches only the latest 50 activity summaries in its protected local service store, with a last-sync marker for offline viewing. It does not cache saved conversations. Expired summaries are pruned during service refreshes and history reads, and the cache clears on sign-out or account adoption. A stopped service prunes expired records when it next runs. Deleting history does not cancel a running job or remove its temporary execution data.

MCP downloads are logged with package/version, time, source IP and approximate country/region/city when supplied by our edge provider. Deduplicated download starts do not prove completion or installation. Hosted MCP connections record account, client/connector origins, heartbeat, tool names and security/admin actions. Platform credentials remain on the customer-controlled connector. Arguments and evidence pass through a temporary queue and are deleted after delivery or expiry, with scheduled expiry cleanup. Your chosen AI client/provider may receive tool evidence.

MCP raw IP and detailed activity are retained for 30 days; non-identifying aggregate download statistics and administrative/security configuration audit for 365 days. Administrator access to raw network metadata is restricted, identity-confirmed and audited. Independent downloaded MCPs have no hidden OUTSEED telemetry or remote kill switch. Hosted revocation blocks access/reconnection to OUTSEED, not independent local software. See MCP data and connection details.

We retain account, application, project, security, and commercial records only for as long as reasonably needed for the purposes described here, to provide an active service, resolve disputes, preserve audit history, and meet legal or contractual requirements. Retention periods may differ by record type and client agreement. Information is deleted or de-identified when it is no longer required.

9. Cookies and browser storage

Account-free inquiry access uses a necessary, HttpOnly, same-site browser cookie for up to seven days. The inquiry reference alone does not grant access. Inquiry records are retained separately from cookie expiry for review, delivery and commercial history. Initial inquiries and documents are visible to authorized OUTSEED administration; client workspace membership is established separately.

The platform uses strictly necessary session technologies to keep signed-in users authenticated and protect accounts. The project-request experience may use browser-local storage so an unfinished request can continue after sign-up or sign-in. OUTSEED also uses Google Analytics to understand aggregate website use; Google Analytics may use cookies or similar device information for measurement. OUTSEED does not use project-request or engineer-application information for advertising.

You can limit analytics through your browser's cookie or privacy settings, use any consent choices presented on the website, or use Google's Analytics opt-out browser add-on. Blocking optional storage may reduce measurement but should not prevent access to public pages.

10. Security

Windows infrastructure/API, vendor MCP and local AI connections validate HTTPS certificates by default. An explicit per-connection Trust any certificate setting disables certificate identity verification for that saved endpoint while retaining HTTPS encryption. Company CA and verified-certificate modes remain available. These local choices do not change OUTSEED account/lease HTTPS validation or SSH host-key checks.

We apply administrative and technical safeguards designed to protect information, including access controls, authentication protections, encrypted transport, security headers, audit records, and role-based workspace access. No internet service can guarantee absolute security. Please report suspected unauthorized access promptly.

11. Your choices and rights

Depending on your location, you may have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent. You may also have a right to complain to a local data-protection authority. We may need to verify your identity and retain information where required by law or an active agreement.

12. Children

OUTSEED is a business service and is not directed to children. We do not knowingly collect personal information from anyone under 18 through the client or engineer workflows.

13. Changes and contact

We may update this policy as the service or legal requirements change. The effective date above identifies the current version. Questions and privacy requests may be sent to contact@outseed.me.