Privacy Policy

This policy covers personal information for which the iSynth operator determines the purposes and means of processing. Third-party websites, source repositories, and independent use of downloaded data are governed by their own practices.

When a submitter provides another author's name, affiliation, email, or ORCID, the submitter must give any required notice and have authority to provide and publish that information.

We may receive information directly from you, from another submitter who identifies you as an author, and automatically when you use the service.

• Account and profile data: email, username, display name, institution, research area, email-verification status, and authentication credentials stored in encrypted or hashed form.
• Submission and research records: data files, metadata, column mappings, author names, affiliations, emails, ORCIDs, corresponding-author designations, access settings, version history, and review comments.
• Interactions and support: upvotes, discussions, feedback, attachments, rights requests, and communications with us.
• Operational and security records: IP address, browser or device identifier, sign-in time, dataset views, coarse country or region information supplied in request headers, audit events, rate-limit events, and error logs.

We process information only to provide, secure, and improve the reaction-data service. We do not use it for targeted advertising unrelated to the platform.

• Create, verify, and protect accounts and maintain sign-in and access permissions.
• Receive, process, review, publish, index, cite, and maintain datasets and versions.
• Send verification codes, security alerts, submission confirmations, review updates, and other necessary transactional notices.
• Produce usage statistics, troubleshoot faults, prevent fraud and abuse, maintain audit records, and comply with legal obligations.

Where applicable law requires a legal basis, processing may be necessary to perform our agreement with you or act at your request, based on your consent, required to comply with law, or necessary for legitimate purposes such as operating a scientific-data platform and protecting systems and users. Where processing relies on consent, you may withdraw it as allowed by law without affecting earlier lawful processing.

Public datasets may be accessed and cited by anyone and used under the license displayed on the dataset page. Their metadata may be indexed by search engines and scholarly discovery services. Password-protected datasets are available only to people with valid access information, although we cannot fully control what an authorized recipient later does.

Author names, affiliations, order, corresponding-author designations, and supplied ORCIDs may be public with the dataset. Every author must provide a valid email, but only corresponding-author emails are displayed publicly. Other author emails are used only for submission, review, notifications, and necessary rights verification.

We use a secure authentication cookie to maintain sessions and browser local or session storage for language guidance, temporary dataset-access tokens, and necessary interface state. We also create aggregate statistics from access records. We currently do not use third-party targeted-advertising cookies. Disabling necessary storage may prevent sign-in, language, or protected-dataset features from working correctly.

Email, hosting, database, object-storage, backup, and security providers may process necessary information under confidentiality and security requirements. We may also disclose information where necessary to comply with law or valid legal process, investigate fraud or security incidents, or protect the lawful rights and safety of users, third parties, or the platform.

The platform and its providers may process or back up information outside your location. Where a transfer is regulated, we will use notices, assessments, contractual safeguards, or other measures required by applicable law and take reasonable steps to maintain protection consistent with this policy.

Account data is generally retained until account closure or the end of the service relationship. Verification codes, sessions, and security logs are retained according to functional, troubleshooting, anti-abuse, and legal needs. Unpublished submissions may be deleted on request where no other retention duty applies. Published datasets, versions, citations, and review provenance may be retained long term to preserve scientific integrity, resolve rights disputes, or meet legal obligations. Backup copies are removed according to backup cycles or kept isolated where necessary.

We use HTTPS, password hashing, session rotation and revocation, role-based access, rate limits, audit records, restricted object storage, backups, and health monitoring. No internet service can promise absolute security. If an incident may affect personal rights, we will investigate, contain its effects, and provide legally required notices.

Depending on applicable law, you may request access, a copy, correction, deletion, or restriction of personal information; withdraw consent; object to certain processing; close an account; or make a complaint. We may verify your relationship to the account, author identity, or submission. Copies already downloaded under an open license may not be recallable. Requests concerning published scientific records are assessed alongside citation integrity, the rights of others, and legal retention duties.

The platform is intended for research and professional users and does not intentionally collect information from minors who cannot independently provide the relevant consent. A minor should use the service only with authorization and guidance from a guardian, school, or research institution.

Send privacy questions, rights requests, or security reports to isynth@ichemdata.com. We may update this policy and will show a new revision date. Material changes will be announced in the service, by email, or through another prominent method; where renewed consent is required by law, we will request it separately.