Privacy policy
This policy explains what happens to the information you provide when you use BibVera. It applies to the public tool pages and to the optional workspace.
Effective date: 2026-11-20
Information we collect
When you sign in and use a tool page, your input (a DOI, URL, ISBN or title) is used to look up candidate metadata. A signed-in account and an active Pro subscription are required to generate and copy citations.
If you create an account, we store your email address, a salted password hash derived from your password, and the references and projects you choose to save. Passwords are never stored in plain text.
Technical data such as the pages you request may be processed by the hosting platform to keep the service secure and available.
How we use information
To look up source metadata, format citations, save your references, provide account access and respond to support requests.
We do not sell your personal information, and we do not use saved references to train advertising profiles.
Third-party services
Source lookups may involve scholarly metadata services such as public scholarly sources, publisher records or the web page you submitted. Only the identifier or URL needed for the lookup is sent.
If payments are enabled, a payment provider processes subscription transactions and sends a signed event to our service. We do not store full card details.
The demonstration deployment runs with DRY_RUN and mock flags enabled by default: external lookups, email and payments do not make live third-party requests until those flags are explicitly turned off in a production configuration.
Cookies and local storage
The tool pages do not need advertising or tracking cookies. An authenticated session is kept in a secure, HTTP-only cookie when you sign in.
Your browser may keep the language preference and draft form values locally so a page reload does not discard your work.
Retention and deletion
References and projects are kept while your account is active. You can remove individual references, or ask us to delete your account and the data associated with it.
Technical logs are kept only as long as needed for security and troubleshooting, then removed or aggregated.
Security
Access to saved data requires authentication, and subscription state is checked on the server rather than inferred from the browser. Secrets and API keys are kept in the deployment environment, never in the published site files.
No online service can promise absolute security. If you believe your account has been compromised, contact us using the address on the About page.
Children's privacy
BibVera is a general research tool and is not directed at children under 13. We do not knowingly collect personal information from them. If you believe a child has provided personal information, contact us so we can remove it.
Changes to this policy
When this policy changes, the date below is updated and the revised text is published on this page. Material changes that affect saved data will be explained clearly.
Contact and requests
To access, correct or delete your information, write to support@bibvera.com from the address associated with your account. We may need to verify ownership before acting on a request.