Privacy

Who operates Nodagentry

Wasapile Labs operates Nodagentry. This page explains how information is handled when you browse the site, save a workflow, connect a model, or contact us.

Information the service handles

Signing in provides account information such as your name, email address, profile image and sign-in provider identifier. Authentication uses session information and cookies. When you save a workflow, we store its name, configuration, task text and test cases, which can include prompts and text you add to nodes. Publishing stores a separate version of the graph. Run URL requests store the task, workflow version, run status, result or error, available model and tool step outputs, timing and usage estimates, and request identifiers. Recent event runs are visible to the signed-in account that owns the workflow.

Provider API keys saved to an account are encrypted in the database and decrypted when needed to make authorised provider calls. Temporary keys are associated with a browser session and can be processed or stored server-side; “this browser” does not mean a key never leaves your device. Treat keys and Run URLs as secrets.

How information is used

We use this information to sign you in, save and execute workflows, connect models, show results, operate credit accounting, troubleshoot errors and respond to support requests. Technical request information can also be handled by our hosting and security services.

Model providers and other services

Live runs send the task, relevant prompts, upstream outputs and any included attachment text to the selected model provider. Configured tools may contact other services. Local Ollama requests use the local endpoint you configure; other app features such as account saving still use our servers. Sim produces demonstration outputs and should not be treated as a private storage environment.

Services involved include Vercel for hosting, Web Analytics and Speed Insights, Neon for the hosted database, your chosen sign-in and model providers, and Porkbun-hosted email for correspondence. Where payment flows are used, Stripe handles checkout information and we store customer and payment references, subscription status, credit grants, reservations, charges, model identifiers, token counts and timing. Billing usage records do not include prompts or model responses. These services may process information outside your country, depending on the service and its configuration. Their own privacy terms also apply to information they receive.

Analytics and browser storage

We use Vercel Web Analytics to understand visits and page usage, and Vercel Speed Insights to measure loading speed, responsiveness and visual stability. Our integration removes URL query strings and fragments from analytics events and excludes API and authentication callback paths. Analytics is separate from workflow execution and is not configured to send task text or API keys as custom events.

The browser stores preferences such as theme, onboarding progress and the last selected workflow identifier. Authentication and connected-key sessions use cookies or session storage. Clearing browser storage can remove preferences or sign you out, but does not delete account data stored on our servers.

Storage, access and deletion

Saved account and run records currently have no automatic expiry in the application. Contact us to request access, correction or deletion of your information or to close your account. We may need to verify account ownership. Some records may need to be retained for security, dispute resolution or legal obligations; we will explain relevant limitations when responding.

Exporting a graph makes a copy; it does not delete the saved version. Avoid entering personal, confidential or workplace information that you do not have permission to share with the services your workflow uses.

Questions and complaints

Email contact@nodagentry.com with privacy questions or complaints and enough context for us to investigate. Please do not send passwords or API keys. If you remain dissatisfied, you may contact the privacy regulator relevant to your jurisdiction, including the Office of the Australian Information Commissioner where applicable.

Changes to this page

We will update this page when our handling of information changes and show the revised date above. Check this page before connecting new services or submitting sensitive information.