ZotLit Privacy Policy
Effective
Scope of this Policy
This policy applies to all services operated by ZotLit. This includes the Obsidian plugin, the Zotero companion, local tools, the documentation website with its blog and Template Workbench, and the community forum along with its sign-in systems.
ZotLit is maintained by AidenLx. If you have questions or requests regarding your personal information, you can reach out to the maintainer using the contact link provided in the interface.
Local Tools and Your Research Data
ZotLit local tools run directly on your computer. They process your selected Zotero library metadata, annotations, files, templates, and notes locally.
If you use the optional Local Bridge, it transfers information only between the web-based Template Workbench and your local desktop application on the same machine.
ZotLit does not operate any cloud synchronization service for your research library. You may choose to submit diagnostic or support information manually when seeking help. Certain linked resources or third-party tools you choose to configure may make independent network requests.
Website and Technical Information
ZotLit and its service providers may process technical and usage data to operate the website and forum, measure performance, and protect the services from abuse.
Cookies and browser local storage are used to maintain your login session, protect against security threats, and remember preferences.
Selected documentation pages load Giscus, a commenting widget powered by GitHub Discussions. Interacting with Giscus is subject to GitHub privacy practices and terms. Discord, Obsidian, and Zotero are independent third-party services with their own policies.
Community Forum and Public Content
When you register or participate in the Discourse community forum, the service stores your account email address, profile details, posts, uploads, support discussions, and connection and security logs to operate the forum, provide support, and manage moderation.
Visitors can read and copy posts made in public forum categories and any profile details you make public. Selected historical public discussions were migrated from GitHub and remain published with attribution.
We may send selected public content to third-party translation providers for language detection and translation. Private messages and account sign-in details are strictly excluded from this translation processing.
Third-party sign-in
You can use GitHub, Microsoft, or Google to sign in to the forum.
When signing in with GitHub, ZotLit requests your public profile and the user:email permission. This allows us to receive your account identifier, username, name and avatar if available, as well as account email addresses including verified email addresses. ZotLit does not request access to your private repositories.
When signing in with Microsoft, ZotLit uses basic identity permissions and Microsoft Graph User.Read to read your signed-in profile. This may include your account identifier, name, and email address when available. ZotLit does not request access to your Microsoft mail or files.
ZotLit uses the information it receives from sign-in providers to authenticate you and create, link, or secure your forum account. The forum may store linked identifiers, available profile information, or tokens returned by the provider for that purpose, and never receives or stores your provider passwords. You may revoke consent at any time from your provider account settings or contact ZotLit to unlink the account or request deletion.
Google sign-in data
For Google sign-in, the forum requests email and profile permissions.
Through these scopes, ZotLit may receive your Google account identifier, email address, email verification status, display name, and profile photo. ZotLit never receives your Google password and does not request or access your Gmail, Google Drive, Google Calendar, or contacts.
This Google user data is used solely to authenticate your identity, create or connect your forum account, display your profile details, secure the service, and assist with account support. The forum stores your linked Google account identifier, available profile information, and authorization credentials, such as tokens returned by Google, to operate the sign-in connection.
Your Google information is never sold and is never used for advertising, marketing, or promotional tracking. It is shared only with hosting and infrastructure providers as necessary to run the sign-in flow and service, or when required by law with appropriate safeguards. All Google user data handling complies with the Google API Services User Data Policy, including its Limited Use requirements.
Data Retention and Your Rights
Information is retained only as long as necessary to provide the services, maintain platform security, resolve disputes, and satisfy legal obligations. Deleted information may persist in operational backups until regular backups are replaced or expire, and public posts that have been quoted or shared by others may remain visible.
Under applicable data protection laws, you may request access to, correction of, or deletion of your personal data, as well as exercise other recognized rights. You can submit requests through the contact link in the service interface.