Privacy Rights Request Guide
Version v2.1-idp · Effective Friday, November 6, 2026
Signing in to a partner service with ResearchCave does not mean that ResearchCave operates that service. This notice explains the distinction when an independently operated third-party website or application uses ResearchCave as its identity provider. It does not describe services operated by ResearchCave itself as independent partners.
ResearchCave's identity-provider role
For this integration, ResearchCave provides account sign-in, authentication and the associated identity information exchange. ResearchCave Technolgy Ltd, at , remains responsible as controller for the purposes and means it determines for its own ResearchCave account administration, authentication, account security and related support. Providing sign-in alone does not make ResearchCave the operator, seller, representative or guarantor of the partner service, or the controller of the partner's independently determined processing.
The partner's service and privacy responsibilities
The partner operates its own service and is responsible for its own products, transactions, payments, refunds, content, moderation, customer support and service security. Where it determines the purposes and means of processing, it is the controller for that processing, including its own customer records, communications, marketing and usage data. It must identify its legal operator and provide its own applicable terms, privacy/KVKK notices and accessible contact and rights-request channels. The ResearchCave notice shown during sign-in covers ResearchCave's processing; it does not replace the partner's notices or constitute acceptance of the partner's terms or blanket consent to its processing.
Information shared for sign-in and separate records
To complete the sign-in you request, ResearchCave may disclose an account identifier and the identity/profile fields permitted for that integration, according to the requested permissions, the information presented to you and the applicable lawful basis. The partner must explain its subsequent use, recipients, retention and any international transfers. Sign-in or acknowledgement of a privacy notice is not by itself consent to optional marketing, advertising or unrelated processing. Closing a ResearchCave account does not by itself delete copies already held by the partner; separate requests and lawful retention duties may apply.
Who to contact when something goes wrong
For ResearchCave account access, authentication security or rights concerning ResearchCave's own processing, contact contact. For the partner's service, transactions or independently controlled data, use the partner's published contact or privacy channel. A partner's failure to respond or provide a contact does not by itself transfer its obligations to ResearchCave. You may report misleading use of ResearchCave's name or notices to contact; ResearchCave will address matters within its own role and any applicable legal duties. This does not promise resolution of a partner dispute or restrict statutory requests, regulator complaints or other remedies.
Actual roles and mandatory liability remain applicable
A ResearchCave sign-in button, logo or integration alone is not an endorsement, compliance certification, agency relationship or guarantee of the partner's conduct. This notice does not exclude ResearchCave's liability for its own acts, omissions, security duties or other obligations that cannot lawfully be excluded. Controller, processor and any joint-controller responsibilities follow the actual processing and applicable law, rather than labels alone; where required, the relevant processing or joint-controller arrangements must be established and disclosed. Consumer and data-protection rights remain available.
ResearchCave Sign-in and Independent Partner Services
This Guide explains how to exercise privacy rights across ResearchCave services.
Submitting a request
Use an authenticated privacy dashboard when available or contact contact. State the service, account identifier, request type, country or state of residence, and enough detail to locate relevant data; do not send passwords or unnecessary identity documents.
Verification and authorised agents
We match information already held, use authenticated account steps, or request limited additional evidence according to the risk of the request. An authorised agent may need proof of authority, and we may confirm the request directly with the individual where permitted.
Handling and exceptions
Requests are logged, routed to data-owning services, and answered within the applicable period. A response may explain lawful retention, competing rights, manifestly unfounded or excessive requests, or data that cannot be connected to a verified individual.
Appeals and complaints
Where an appeal right applies, reply through the stated channel and explain why you disagree. You may also complain to the competent privacy regulator or seek another remedy provided by law.