Privacy Policy
How Nodavera collects, uses, stores, and shares personal information, and the choices available to you.
About this policy
This Privacy Policy explains how Nodavera handles personal information when you use nodavera.com and the Nodavera application. Last updated: 12 October 2026.
Information we collect
We process account details such as your name, email address, profile picture, authentication identifiers, and preferences. We also store the workflows, tags, assignments, messages, files, and feedback you submit, together with collaboration permissions and notifications.
When you sign in with Google, Google provides your name, email address, profile picture, and account identifier through Firebase Authentication. This sign-in does not give Nodavera access to your Gmail messages, Google Drive files, contacts, or calendar.
Service requests may generate technical and security information, including IP addresses, browser or device details, timestamps, page paths, recent interaction categories, software release identifiers, errors, and authentication or abuse-prevention events. Error reporting excludes passwords, access tokens, workflow content, and input field values. Feedback includes your account name and email, the submission time and page, and diagnostic context to help investigate your report.
How we use information
We use account and Google profile information to authenticate you, display your identity, manage access, and operate your account. Workflow content and collaboration information enable editing, sharing, assignments, messages, and notifications. Technical information helps us diagnose failures, protect accounts, prevent abuse, and maintain the service.
Storage and security
Account information and application data are stored in Firebase Authentication, Firestore, and Cloud Storage as applicable. The application uses access controls and encrypted network connections. No online service can guarantee absolute security. Infrastructure providers may process information outside your country.
Browser storage and analytics
Browser storage supports sign-in sessions, preferences, and cached application assets. Optional Google Analytics collection is enabled by default and can be disabled in Profile under Privacy preferences. It measures use of general application screens and browser or device information; application event fields exclude workflow identifiers and content. Advertising personalization and Google signals are disabled in the application's analytics configuration. Disabling analytics does not disable information needed for authentication, security, or service operations.
Retention and account deletion
We retain account and workflow information while it is needed to operate your account and the service. Moving a workflow to Trash is different from permanently deleting it.
Account deletion in Profile starts background cleanup: workflows you own are permanently deleted, your access to workflows owned by others is revoked, and your account data, tags, notifications, and authentication account are removed. Deletion may take time to complete. Other users' independent content and copies are not removed by deleting your account. Operational logs and provider-managed backups may remain subject to their retention settings.
Your choices and requests
You can update available profile settings, manage sharing permissions for workflows you own, disable optional analytics, and delete your account. You can revoke Nodavera's Google connection in your Google Account settings; revoking that connection alone does not delete your Nodavera account or stored workflows.
For questions or requests about access, correction, or deletion of your personal information, contact support@nodavera.com. We may need to verify your identity before acting on an account request.
Policy updates
Updates to this policy will be published on this page with a revised date. Read our Terms and Conditions for the contractual rules governing use of the service.