Privacy

Peerpedia is a public research publishing service. Operator information is on the About page.

Your account

We store your username, email address, verification status, and account settings. Password accounts store a password hash, not the password itself. Your email is not displayed publicly.

Google sign-in

If you choose Google sign-in, Google shares a unique account identifier, your email and its verification status, and basic profile information such as your name. We use this information to create or authenticate your Peerpedia account. We do not request access to Gmail, Drive, contacts, or calendars. Google access and refresh tokens are not retained. You choose your public Peerpedia username.

Existing users must sign in and explicitly connect Google from Account. Google sign-in does not automatically merge accounts with matching email addresses. You can disconnect Google if your account has a Peerpedia password. You can also manage Peerpedia's connection in your Google account settings. Google's use of information is governed by Google's privacy policy.

Research and discussions

Published papers, author information, reviews, comments, ratings, and contribution histories are public. Drafts are available to their owners and authorized operators. Published submissions and revision snapshots form a permanent academic history; deleting an account does not automatically erase this public record.

Cookies and service providers

We use cookies for sign-in sessions and protection against forged requests. The application does not add advertising or analytics trackers. Hosting is on Alibaba Cloud in Hong Kong. Account email is delivered through Resend. DNS and traffic protection services may process connection information when enabled.

Security and retention

Account data, drafts, and published records are stored in the application database and backups. Server logs and rate-limit records may include technical connection information used to operate and protect the site. Access is restricted to authorized operators. Backups may be copied to the operator's Mac for recovery.

Account information is retained while needed to operate your account and the service. For access, correction, or deletion requests, contact the developer. Requests affecting public academic history or backup copies may require separate handling.

Agreements and rights requests

We record your agreement acceptance, its version and time, and licensing declarations to document permissions. Private rights requests include the contact details, affected URL, and explanation you supply. They are stored for authorized operators to assess and respond to the request and retain an appropriate record of its handling.

Contact

For copyright, withdrawal, or privacy matters, use the private rights-request form. For other contact options, see the About page. Do not post passwords, tokens, or private account information in public GitHub issues.