Privacy Policy

Who operates RedRover

Hatchery LLC operates RedRover. This policy describes information handled through RedRover, including signed-in workspaces and link-based customer, support, report, and update pages. Your organization may separately determine how its workspace information is used. Applicable customer and data-processing agreements may provide additional commitments.

Information in RedRover

Information may include names, email addresses, phone numbers, profile details, skills and interests, account roles, and workspace memberships. Workspace content can include goals, requirements, tasks, releases, comments, files, brand assets, support tickets, task order amounts, approvals, time entries, and team check-ins. RedRover also processes activity records, access and invitation status, notification delivery information, AI interactions, and operational diagnostics.

Public marketing and beta requests

When you apply for the RedRover beta, we store your name, email, organization, team size, current tools, intended use, Hatchery customer declaration, Founding Partner interest, and contact preferences. We also store the consent version and the source or campaign you arrived from. Marketing requests are kept separately from workspace content and customer accounts. We use this information to review your request, contact you about access, and arrange onboarding. Optional product news uses a separate opt-in. Applying does not create a subscription or collect payment. A case study requires separate permission. Contact Hatchery to correct or withdraw your request or change your contact preferences.

The public site uses a session cookie for application security and browser session storage for campaign attribution. We do not add advertising trackers through this beta application.

Why information is used

Information supports authentication, collaboration, planning, file access, approvals, reporting, support, notifications, and enabled integrations. Activity, usage, and diagnostic records help operate and troubleshoot the application and investigate misuse. Profile information and work records may be visible to authorized people outside your company when you collaborate in a shared workspace.

Workspace permissions and shared links

Access depends on account and workspace permissions and the sharing feature used. Authorized administrators can manage users and review permitted account information; authorized system operators may access information for administration and support. Certain links allow an intended recipient to view a report or ticket, set a password, or update assigned work without a normal login. Treat these links as private: someone who receives a forwarded valid link may be able to use its access.

Maggie and AI providers

When you use Maggie or AI-assisted prompt features, your question and relevant context may be sent to the configured AI provider, including OpenAI. Questions, answers, and usage records may be retained for authorized administrative review, quality improvement, and troubleshooting. Do not assume an AI conversation is visible only to you. Provider processing is governed by the applicable service configuration and provider terms; this policy does not promise that every provider has the same retention practices.

Storage, integrations, and service providers

RedRover uses service providers for hosting, database and file storage, AI processing, and email or text delivery. Uploaded files use Amazon S3 storage organized by account. Depending on enabled features, data may also pass through SendGrid, Hatchery Connect, Google sign-in, Asana, or Loom. Connecting Asana can import work and synchronize supported updates. Loom recordings remain hosted by Loom; opening an embedded recording connects to Loom and remains subject to its access settings. Information may also be disclosed when required by law or to protect rights and security.

Browser storage and messages

Session cookies support sign-in. Browser storage holds preferences such as theme, navigation, dashboard arrangement, and dismissed guidance; PWA caches support the installed web experience. External integrations may use their own browser storage. Invitations, assignments, check-ins, and support updates may be delivered by email or text according to enabled workflows and preferences. Some service messages are needed to complete actions you or your organization request.

Retention, removal, and your choices

Retention varies by record type, customer agreement, and operational or legal need. Archiving a workspace is different from deleting its records. Exports, backups, audit records, messages already delivered, and copies held by integrated services may persist after a record is removed from the active application. Contact your account administrator about workspace access, corrections, and exports. Contact Hatchery LLC for privacy questions or access, correction, deletion, or other requests available under applicable law. Requests may require identity and authority verification.

Contact and updates

Use Hatchery’s contact page and identify RedRover when making a privacy request. Avoid sending passwords or private access links in an initial inquiry. We may update this policy as the application or its information handling changes; the version date appears above.