| Resume upload text (analysis input) | Generate recruiter-style feedback, scoring, and rewrite guidance. | RIYP does not store raw input for anonymous runs. OpenAI may retain API abuse-monitoring logs containing customer content for up to 30 days by default. | Sign in to save your history, or delete your account in Settings. | OpenAI, Supabase |
| Report output + resume preview | So you can open past reports, compare versions, inspect evidence excerpts, and export. | A completed anonymous report output and its evidence excerpts are held for browser recovery for no more than 24 hours; the raw anonymous resume and job description are not stored by RIYP. If you sign in and save, history includes report output, evidence excerpts, a short resume preview, and any job description you add until you delete the report or account. | Anonymous recovery expires automatically. Delete saved reports in History, or delete your account in Settings. | Upstash, Supabase |
| Saved resume profile (default resume) | Job matching and extension workflows. | Stored until you replace it, remove it, or delete your account. Includes raw resume text for matching plus derived skills, seniority signals, embeddings, hash, and preview. | Replace or remove it in Settings > Matching, or delete your account. | Supabase, OpenAI (embeddings) |
| Captured jobs and job descriptions | Save roles from the extension, run role-fit checks, and compare your resume against specific postings. | Stored when you save a job or sync extension captures. Includes job title, company, URL, description text, match signals, and latest report links until you delete the saved job or your account. | Delete saved jobs from Jobs, delete linked reports from Reports, or delete your account in Settings. | Supabase, Chrome local storage, OpenAI when used in a report |
| Account identity (email, name) | Authentication and account access. | Retained while account is active. | Update your profile in Settings, or delete your account. | Supabase |
| Support communications and attachments | Respond to product, account, billing, privacy, and security requests sent to the public support address. | Kept only as long as reasonably needed to resolve the request, preserve security or billing evidence, meet legal obligations, and maintain support continuity. Provider logs follow their configured retention windows. | You choose what to send. You can ask us to delete a support conversation unless we need to retain it for security, fraud prevention, billing, or legal compliance. | Resend, Google (Gmail) |
| Usage, reliability, and abuse-prevention metadata | Free-report eligibility, rate limiting, reliability diagnostics, billing state, and product health. | Signed browser cookies used for anonymous identity and free-report status may remain for up to 365 days, and their browser expiration renews when we set them again. Server-side anonymous eligibility records, including separately salted network hashes, expire within 40 days. Raw network addresses are not stored in the eligibility ledger. Rate-limit and idempotency records are short-lived; other operational records are retained for product and security needs. | Anonymous eligibility records are not attached to an account. Deleting your account removes app-level history. | Supabase, Sentry, Vercel, Upstash |
| Background job events and results | Generate account exports and, when used, PDF files without keeping the request open. | Retained under Inngest's configured event and run-history windows. Completed account exports stored in Supabase expire after seven days. | Background export work starts only when you request it. You can delete your account and its app-level export records in Settings. | Inngest, Supabase |
| Product analytics and conversion telemetry | Measure product quality, onboarding friction, and billing funnel health when analytics is enabled. | Retained under the analytics vendors' configured retention windows. | Respects browser Do Not Track and can be disabled at launch. | Mixpanel, Vercel |
| Billing events and invoices | Charge processing, receipts, purchase restoration, refunds, and dispute handling. | Stripe retains authoritative billing records under its policies. RIYP keeps limited receipt and entitlement metadata for reconciliation, security, and reversal handling. | View receipts and restore purchases from Billing settings. Account deletion removes user-linked app billing records; opaque reversal identifiers may remain to prevent access from being re-granted. | Stripe, Supabase |