NodeFox

Account Access and Legal Flow

This is the canonical NodeFox end-user flow. Use this page when you need one clear sequence for account setup, legal acceptance, consent/disclaimer handling, safe product usage, and long-term account management.

The recommended posture is to treat onboarding and legal controls as runtime prerequisites, not afterthoughts. Most operational issues happen when teams skip acceptance flow design and try to patch governance later.

Full end-user sequence

Step 1: Create account and establish identity

Start at Sign up or Sign in if the account already exists. During setup, confirm the primary email owner, backup contact routes, and recovery ownership before real workflow usage begins.

If Google sign-in is enabled, keep at least one tested fallback login path. This avoids lockouts when identity-provider sessions expire or team ownership changes.

Each page that can create or finish an account shows one notice next to the button it names:

  • Sign up, above both buttons: "By clicking Continue with Google or Create account, you confirm you are 18 or older, agree to the Terms of Service and acknowledge the Privacy Policy."
  • Sign in, under Continue with Google, because Google creates an account for a new address: "New to NodeFox? Continuing with Google creates an account. By continuing you confirm you are 18 or older, agree to the Terms of Service and acknowledge the Privacy Policy."
  • Set password (invitations), above the button: "By setting a password you confirm you are 18 or older, agree to the Terms of Service and acknowledge the Privacy Policy."

Our server records the acceptance (Terms version, time, the page that showed the notice, browser user agent) only when it can confirm that page showed the notice in your browser moments before you clicked. Anyone it can't confirm, for example an account first opened in the app or a confirmation link opened much later, is asked to accept on the Terms acceptance screen. That takes one checkbox, and it comes before opening the app from your account, starting a checkout or claiming an invite.

Assent covers the Terms of Service and every policy the Terms incorporate, including the Privacy Policy, the Acceptable Use Policy, and the rest of the Legal Center.

Three things follow from that single acceptance, and they are worth reading rather than assuming:

  1. Service terms. The applicable service conditions cover both free and paid plans. See the Disclaimers.
  2. Third-party cost responsibility. AI provider and API fees accrue under your own keys, including on failed, retried, or runaway executions. You are responsible for spend caps, iteration limits, and timeouts.
  3. Conduct rules. The Acceptable Use Policy governs what your Workflows may do, including Autonomous Actions taken without per-action approval.

Where NodeFox materially updates the Terms or an incorporated policy, it provides notice and, where the update requires it, asks for re-acceptance. Accounts that accepted an earlier version see a notice on their account pages and the same acceptance screen. Account › Billing stays available either way, so you can always manage or cancel a subscription. Optional communications (for example marketing updates) are never bundled into this acceptance: they are opted into separately, and you can opt out at any time through the unsubscribe link or by writing to privacy@nodefox.ai.

After legal acceptance, route users through interface disclaimers and consent surfaces relevant to their usage class. This includes security warnings, AI-output caution language, and sensitive-action guidance.

For routing:

  • Consent and opt-out requests: privacy@nodefox.ai
  • General contact and support routing: info@nodefox.ai

Use Contact, Terms, and Privacy for implementation detail and routing.

Step 4: Configure account security before sensitive usage

Before production-sensitive workflows, require users to configure:

  1. Password and reset readiness
  2. Identity-provider multi-factor protection where available
  3. Documented ownership of the account email and recovery path
  4. Credential hygiene basics for integrations and API-key usage

Use Account settings, Sign in, and Reset password for operational detail.

Step 5: Configure billing and subscription controls

If the user moves from free to paid usage, route through clear Stripe-backed billing acceptance with recurring-billing visibility and cancellation expectations. A first paid purchase carries a 30-day money-back window under the Refund Policy.

The practical baseline is:

  1. Confirm payer and billing owner
  2. Confirm renewal timeline
  3. Confirm cancellation authority
  4. Confirm export expectations before plan downgrades or closure

Use Pricing and Account settings.

Step 6: Begin product usage with deterministic controls

Once access, legal, consent, security, and billing controls are in place, users can begin workflow usage across Network, Automate, and Apps views — see the Product overview.

For policy-sensitive workflows, enforce acceptance and consent state checks at runtime branch points, not only at sign-up.

Step 7: Ongoing management and lifecycle operations

Steady-state account management includes:

  1. periodic security verification
  2. policy-update re-acceptance where required
  3. subscription and cancellation handling
  4. ownership transfer procedures
  5. consent/opt-out request handling

The objective is a durable operating flow that remains clear as users, policies, and workflows evolve.