Privacy

## How CoverCraft handles data.

This policy explains what CoverCraft reads, stores, transmits, and syncs when users work from a live job page.

Last updated: April 8, 2026 Domain: cover-craft.app

### Overview

CoverCraft is a Chrome extension that helps users generate job-application materials from live job pages. It can extract job context, create tailored cover letters, support follow-up questions, prepare resume-related output, and optionally sync reusable sessions and profile data when the user signs in.

### Information CoverCraft Handles

- Website content: job posting text, page context, and page URL needed to understand the current role.
- Profile data: name, email, phone, website, skills, work history, achievements, and related portfolio details entered or imported by the user.
- User-generated content: generated cover letters, question-and-answer outputs, saved sessions, research summaries, and resume-related artifacts.
- Authentication data: Google sign-in and Firebase authentication state used for optional account access and sync.
- Local runtime settings: model selection, workflow preferences, and user-entered API keys for OpenRouter, Groq, and Tavily.

### How CoverCraft Uses Information

- To extract role, company, and page context from a live job page.
- To generate job-specific cover letters, answers, and resume-related outputs requested by the user.
- To save reusable sessions and reconnect users with earlier work.
- To keep the active profile available across letters, exports, and account surfaces.
- To support optional sign-in and cloud sync for sessions and profile state.

### Third-Party Services

CoverCraft may send user-requested data to external services only when needed to provide a feature the user explicitly invokes.

- OpenRouter or Groq: for AI generation requested by the user.
- Tavily: for company research requested by the user.
- Google and Firebase: for optional sign-in and optional cloud sync.

### What Stays Local

User-entered OpenRouter, Groq, and Tavily API keys are stored locally in extension storage for runtime use. CoverCraft does not sync those provider API keys to Google or Firebase cloud storage.

### Cloud Sync

If the user signs in and enables cloud sync, CoverCraft may store sessions, research summaries, generated outputs, and active profile data in the developer-managed Firebase backend. If cloud sync is disabled, that data remains local-first in the extension.

### Data Sharing

CoverCraft does not sell user data and does not share user data for advertising. Data is only transmitted to the service providers required to perform generation, research, sign-in, or sync functionality requested by the user.

### User Controls

- Users can edit or replace their active profile.
- Users can delete local sessions and stored outputs.
- Users can choose whether to enable cloud sync.
- Users can sign out of Google-backed sync at any time.
- Users can remove the extension to stop further local use.

### Security

CoverCraft transmits data over HTTPS to supported providers and cloud services. Access to synced cloud data is intended to be scoped to the signed-in user account through the configured backend rules.

### Contact

For privacy or security questions about CoverCraft, contact tirth.shah@tamu.edu.