What ResearchHelp handles
ResearchHelp processes the information needed to provide your research workspace, keep projects attributable to the correct account, preserve revisions and provenance, and protect the service from misuse.
- Account and profile information such as name, email address and verified academic context.
- Research-project information you create or confirm, including topics, framing, methodology plans, writing and structured document content.
- Sources, evidence records and research files that you choose to upload or save.
- Technical and security information needed for authentication, abuse prevention, reliability, diagnostics and operational support.
How the information is used
- Provide authenticated ResearchHelp features and preserve your research workspace across sessions.
- Apply project-bound academic context and institutional specifications where verified.
- Generate bounded research guidance without silently converting guidance into authoritative project state.
- Protect account ownership, cross-user isolation, source privacy, service reliability and security.
- Diagnose failures and improve the service using bounded operational telemetry rather than exposing private research content unnecessarily.
Research files and project privacy
Research projects, source files, evidence, drafts and structured research content are private to the authorised ResearchHelp account unless a future collaboration feature explicitly states otherwise.
ResearchHelp does not treat uploaded research material as public content merely because it is processed by the service.
Service providers
ResearchHelp may rely on infrastructure, authentication, storage, hosting and model providers to operate the service. Access is limited to what is required for the relevant service function and remains subject to ResearchHelp security and authority boundaries.
ResearchHelp does not sell research conversations, project content or account data to advertisers.
Retention, export and deletion
ResearchHelp retains project and provenance records only as required to operate the service, protect academic/research integrity, support revision history, meet security obligations and apply the product's documented retention rules.
Public launch requires a documented account-data export and deletion process. ResearchHelp must not present deletion as instantaneous where retention, security or provenance obligations legitimately require a bounded retention period.
Security and access
- Authenticated server sessions protect private research routes.
- State-changing requests use server-side authorisation and same-origin protections.
- Direct browser access to private database and storage content remains denied unless an explicitly reviewed route authorises it.
- ResearchHelp aims to keep secrets, provider credentials and private storage paths server-only.
Questions and changes
Material privacy-policy changes will be reflected by the last-updated date on this page. ResearchHelp should not silently weaken the privacy commitments stated here during a production release.