Privacy Policy

1. Information involved

Depending on the feature, information can include account and professional details; submitted URLs, flyers and documents; extracted text and assessment records; support correspondence; technical usage and security logs; and payment status or transaction references.

Public conference information may include professional names, affiliations and contact details. Public availability does not remove the need for appropriate handling, accuracy and limited disclosure. Avoid submitting unrelated personal or confidential material.

2. Purposes and processing

Information is processed to provide requested features, maintain account and payment records, investigate errors or misuse, handle support and corrections, and meet applicable obligations. Optional communications should have an appropriate choice or unsubscribe route.

Conference research may use public information and appropriately documented submissions. An allegation is distinct from a verified fact. Contributor identities and supporting private documents should not appear in public reports without an appropriate basis.

3. Service providers and international processing

Features can involve providers for hosting, databases, identity, payments, communication, document extraction, web retrieval and AI analysis. Processing may require sending relevant URLs, document content or extracted text to the providers supporting that feature.

The reviewed Supabase project is in the ap-southeast-2 region (Australia). This service must not be understood as India-only data hosting. Other providers may process information in other countries; contractual and institutional requirements must be checked for the particular deployment.

The release notice should identify the active providers and material processing arrangements. Contact [email protected] before submitting restricted institutional or confidential research material.

4. AI processing and model training

Using a model to extract or assess text is different from training a model. This notice does not assert that ScholarVault trains its own models or that every provider has zero retention. Provider settings and contracts must be verified for the actual workflow.

This draft does not authorize training on private manuscripts, institutional documents or contributor evidence. Any proposed training use requires a separate, accurate explanation and an appropriate lawful basis; removing a name alone does not guarantee anonymity.

5. Sharing and visibility

Reports may have sharing or public-reference features. Review the destination and visibility before sharing; a public link can be forwarded. Access to an institutional workspace depends on its configured roles and agreement, rather than a universal promise that only one individual can see it.

Support and operational access, service-provider processing and legally required disclosure may be necessary. Marketing, sale of personal data or publication of contributor evidence is not authorized merely by submitting a conference for assessment.

6. Cookies and analytics

Sites can use session, preference and analytics technologies. The public-site code includes Google Analytics configuration; a blanket statement that no third-party tracking is used would be inaccurate. Browser controls may limit cookies, and non-essential tracking must be handled consistently with applicable requirements.

7. Retention, deletion and security

Retention depends on the record type, service purpose, purchase or institutional terms, backups and legal requirements. A saved report, source document, processing log and backup may have different lifecycles. Do not assume automatic deletion after 24 hours or immediate removal from every backup.

Request access, correction, export or deletion at [email protected]. Identity or authority may need verification. Where information must be retained, the response should explain the reason and relevant limits. Statutory response deadlines take priority.

Reasonable safeguards are required, but no system can promise absolute security. Incident notifications must follow applicable legal and contractual requirements; this draft does not invent a universal notification deadline.

8. Children, questions and updates

The platform is intended for adult users. Under-18 participation requires an appropriate institutional or parental process and any legally required consent; contact support before creating an account or submitting a child's information.

For privacy questions or grievances, email [email protected] with the subject Privacy request. This is a contact route, not a claim that a statutory officer has already been appointed. Applicable rights are preserved. Changes to processing require corresponding notice updates.

Contact support · Version 2026-09-19-review