Last updated October 19, 2026

Privacy

Next Gen Workflows is run by John Burrell, doing business as Next Gen Workflows, in Ohio. This page explains what this portal and the apps we host for customers store, why, and for how long.

This portal

The portal stores account email addresses and display names, password hashes, business memberships, app access grants, session records, login attempts, and audit events with IP addresses and times. A separate sign-in history stores only time and success. Single-use account links are stored as hashes; pending email delivery contains the message until it is sent.

If you use the contact form, it also stores your name, email address, message, IP address, and the time you sent it. It saves the message for the owner to read and can email a notification when enabled.

Client apps keep their own data separately. The portal does not store their passwords. It uses a session cookie for sign-in and form protection. It can email invitations, password reset links and account change notices through the configured mail service.

Cookies and homepage click totals

The portal uses one warm design for everyone. It no longer sets theme, variant or last-view-day cookies. Old theme and experiment cookies are ignored; the homepage experiment is retired.

The portal keeps anonymous aggregate click counts by UTC day and call to action, including valid contact form submissions. New clicks use the warm design label and are separate from historical experiment comparisons. Historical experiment totals remain available to administrators. No IP address, browser user agent, account identity or individual visit record is stored in these totals. There are no third-party analytics, external fonts or trackers.

When your browser sends Global Privacy Control (Sec-GPC: 1) or Do Not Track (DNT: 1), clicks are not counted. The old theme links and click routes use temporary keyed rate-limit entries to limit abuse; the IP address itself is not stored by that limiter. Sign-in security records and contact messages still use the separate storage described above.

Customer business data

Each customer's app keeps that business's records (such as items, sales and photos) in its own separate database. That data belongs to the customer. We use it only to run, support, back up and fix their app, or when they ask us to. We do not sell personal information or business data, and we do not use it for advertising.

Service providers

Cloudflare carries traffic to our servers and protects them from abuse. Brevo delivers account and notification emails. They handle data only to provide those services. Apps run on servers we operate in Ohio, United States. Backups are kept on our own storage, and an encrypted copy is kept off-site.

How long we keep data

• Customer business data: when a customer stops using the service, we offer a full export and then remove their active records. We don't yet have an automatic deletion schedule.
• Backups: kept so we can recover from mistakes or equipment failure. Removing active records doesn't immediately remove them from backups; data can stay in backup copies for about six months, sometimes longer, until we clear old copies.
• Security records (sign-ins and admin actions): kept for about one year in the live system, and they can also remain in backups as described above.
• Contact messages and account records: kept while needed to answer you or provide the service.

Your choices

You can ask to see, correct, export or delete your information. Customer staff should contact their business owner first, since the business controls its app's records. This service is meant for businesses and is not directed to children under 13.

Contact

Email [email protected] with any questions.