RResearchCode

Legal

Privacy Policy

Last updated: this document describes how ResearchCode handles your information.

What we collect

Account information: name, email, organization, and phone number if you provide it.

Project information: everything you submit through the project form — your methodology description, expected output, existing code and its status, dataset links and metadata (size, format, class count — never the dataset itself), target environment, timeline, and any files or links you add afterward.

Communications: messages exchanged with our team inside a project workspace.

Payment information: Razorpay processes your payment details directly — we never see or store your card, UPI, or bank details. We store only the resulting payment status, amount, and Razorpay’s transaction identifiers.

Technical metadata: IP address and user-agent are recorded against security-relevant events (login, password reset, project status changes) in an audit log, for abuse prevention and incident investigation.

Why we collect it

To review your project’s feasibility, scope it accurately, implement it, and deliver it back to you. To authenticate you and keep your account secure. To process payments and maintain the financial records we’re required to keep. To respond to support requests.

How your project information is protected

Every project is isolated to your account. Our access-control layer verifies both that you’re authenticated and that you own a project before returning any of its data — never by trusting a project ID alone. Directly uploaded files are stored outside any publicly-servable location and are only ever readable through an authenticated, per-request check, never a public link.

Internal review notes an admin writes about your project (distinct from any note or clarification request sent to you) are never included in any response your account can see.

We do not use your submitted methodology, code, or research materials for any project other than yours, and we do not use them to train any model.

Data retention

Project metadata, quotes, payment records, and audit log entries are retained for as long as your account exists, and afterward for as long as we’re required to keep financial and security records. Temporary working files tied to a completed project may be removed after a retention period following completion; core project metadata, payment records, and audit records are not automatically deleted. Contact us if you’d like your account and associated data deleted, subject to the financial/audit records we’re required to retain.

Third-party services

Razorpay (payment processing). MongoDB Atlas or your configured database provider (data storage). An SMTP provider, if configured, for transactional email (verification, password reset). We do not sell your information to anyone.

External datasets and your responsibilities

You’re responsible for what you host on Google Drive, Kaggle, GitHub, or any other external service, and for making sure the sharing permissions you set are the ones you intend. We never ask for your account password on any of these services — only a shareable link.

Your rights

You can review and update your profile information at any time from your dashboard. You can request a copy of your data or its deletion (subject to the retention note above) by contacting us.

Contact

Questions about this policy can be sent through the contact form.