Privacy policy
Last updated:
This policy covers the DSA Coach website at dsaprep.mealmanagers.online and the DSA Coach browser extension. The service is operated by Aryan Pahariya. Contact: thearyanpahariya@gmail.com.
DSA Coach uses your LeetCode practice history to help plan what to practise next. Extension monitoring starts when you connect your account. Source code capture is optional and off by default. You can pause monitoring, disconnect the extension, and withdraw code-capture permission.
Information we handle
- Account and plan information: your email address, display name, account identifier, a password hash, and the preferences and goals you provide, such as language, timezone, experience, schedule, and target companies or date.
- Practice information: the LeetCode problems attempted, timestamps, programming language, active and excluded time, run and submission counts, outcomes, and capture reliability. We also store attempts and notes you enter manually, practice plans, progress, and generated coaching conclusions.
- Optional solution content: source code and run or submission snapshots when you enable code capture. This can include code from unsuccessful attempts as well as a final solution. Do not put passwords, API keys, or other secrets in captured solutions.
- Connection information: browser/device name, device credentials, web sessions, sync status, and temporary sign-in proofs. The extension stores a device token rather than your website password.
- Operational information: our servers and hosting infrastructure process connection and diagnostic information, such as IP addresses, request paths, browser information, and errors, to deliver and troubleshoot the service.
The extension observes supported LeetCode problem pages. It does not request access to your entire browser history, read personal communications, or track activity on unrelated websites.
How we use information
We use this information to connect your account, record and synchronize practice, estimate progress, schedule practice and reviews, generate coaching feedback, enforce your capture preferences, and maintain service security and reliability. We do not sell user data, use it for advertising, determine creditworthiness, or use it for purposes unrelated to these features.
Optional code capture and AI processing
Code capture requires a separate choice in Settings. You can allow it once, allow ongoing capture, or leave it disabled. The application checks your permission before accepting captured source code. With capture disabled, practice metadata can still be recorded.
When AI coaching is enabled, relevant practice context may be sent to OpenAI through the configured coaching provider. If you have authorized code capture, relevant solution code and snapshots may also be sent to OpenAI for diagnosis or review. This processing supports coaching and is subject to the provider’s applicable terms and data practices. We do not promise that processing occurs only on your device or that an external provider retains no data.
AI-generated notes and conclusions can remain in your practice history after the underlying source code is removed. Deleting stored source code does not by itself delete all derived coaching records.
Storage, security, and sharing
The extension uses local browser storage for its connection settings, device token, sync status, and queued attempts. Temporary sign-in state is kept in browser session storage. The website uses an authentication cookie to keep you signed in. Synced account, practice, and consent records are stored in the service database.
The hosted service runs on Google Cloud infrastructure. Hosting providers process data needed to operate the service; OpenAI processes coaching inputs when its AI features are used. We may also disclose information when necessary to comply with law or protect the service and its users. Authorized access is limited to operating, securing, and supporting these features, including user-authorized troubleshooting.
Hosted API traffic uses HTTPS. Website passwords are stored as hashes, and device connections can be revoked. No system can guarantee absolute security. A separately configured local installation may communicate with a backend on your own computer.
Retention and deletion
Account details, practice records, plans, and coaching feedback are retained to maintain your practice history until deletion is requested and completed. Consent and security records may be retained where needed to document your choices or protect the service.
Code saved under ongoing consent is assigned a 90-day expiry; run and submission snapshots are assigned a 30-day expiry. Expired code is excluded from normal retrieval and is eligible for maintenance cleanup. Physical removal depends on cleanup being run and is not guaranteed to occur at the exact expiry time. These periods do not apply to all account data or derived coaching records.
In Settings, Turn off and delete withdraws code-capture permission and deletes stored source code and snapshots from the application database. Other practice records remain. Existing backups and information already sent to a processing provider are not erased by that action and may persist under the applicable backup or provider retention practices.
To request deletion of your account, practice history, or derived coaching records, email thearyanpahariya@gmail.com from your registered address. We may ask you to verify account ownership. Account-wide deletion is handled by request; there is currently no self-service account deletion button.
Your controls
- Pause monitoring from the extension popup, or disconnect it to stop capture and clear its local connection and queue.
- Revoke a browser connection from website Settings to stop it accessing your account.
- Withdraw optional code-capture consent and remove stored code in Settings.
- Use manual logging without connecting the extension.
- Email the contact above for privacy questions, access, correction, or deletion requests. Never send your password or device token.
Pausing or disconnecting does not delete practice information already synced to the service. Revoking a connection on the website does not remotely erase all data from that browser.
Chrome Web Store Limited Use
Our use of information received through the extension follows the Chrome Web Store User Data Policy, including the Limited Use requirements. We use and transfer this information only to provide or improve the extension’s stated practice-tracking and coaching features, or for other permitted security and legal purposes. We do not sell it, use it for personalized advertising, or use it for lending decisions.
Changes and contact
We will update this page when these practices change and revise the date above. Changes to code-capture consent are presented through the application’s consent flow. For questions or requests, contact thearyanpahariya@gmail.com.