Privacy Policy
Data Role Ready is a beta interview-preparation workspace for data engineers. This policy explains what data the service handles and how it is used to generate practice kits, run exercises, operate accounts, and keep the platform reliable.
Last Updated
May 31, 2026.
Information We Collect
- Account details such as email address, authentication provider, verification status, profile settings, and administrator role.
- Resume text, job descriptions, generated interview kits, question attempts, drafts, submissions, and coach interactions.
- Usage and security signals such as login events, rate-limit events, job-processing status, AI usage, errors, and operational logs.
- Billing identifiers from Stripe, including customer ID, subscription tier, subscription status, and webhook event IDs. Data Role Ready does not store card numbers.
- Email delivery information for verification, password reset, and transactional messages when production email is enabled.
How Resume And Job Data Is Used
Data Role Ready uses uploaded resumes and job descriptions to create tailored SQL, Python, system-design, and behavioral interview practice. New resume uploads are scrubbed for common personal identifiers before AI parsing, and the application stores the scrubbed text rather than the original extracted text.
AI-powered features send relevant prompt content to Azure OpenAI for interview-prep generation and coaching. The service is configured for application use, not model training. Users should still avoid uploading unnecessary sensitive information.
Infrastructure And Processors
Data Role Ready runs on Microsoft Azure infrastructure. Application data may be stored or processed with Azure PostgreSQL, Azure Blob Storage, Azure Key Vault, Azure Container Apps, Azure OpenAI, Azure Monitor, and Application Insights. Stripe is used for billing when paid plans are enabled. Transactional email may use Azure Communication Services or another configured production email provider.
Security Controls
- Runtime secrets are stored in Azure Key Vault.
- Application database access uses a least-privilege runtime user where enabled.
- Private networking and restricted administration are used for the DEV stack as currently accepted.
- Rate limits and AI budget controls protect authentication, email, and AI usage paths.
- Operational alerts monitor revision failures, HTTP errors, job failures, database health, and abnormal usage.
Your Choices
You can delete resumes, job descriptions, prep kits, and your own account from the authenticated app. Account deletion removes your profile, sign-in methods, owned prep data, and stored resume files. For export requests, billing questions, or privacy questions, contact the Data Role Ready operator through the support channel provided with your account.