Trust center

Security built into every layer

Every account, location and customer gets the same core safeguards, from a single location to dozens. Here is how NextUp Walk-in protects your business.

Safeguards
47
Areas of protection
6
Same core protection
Every plan
Security at a glance

Your business, your team and your customers, protected by design

NextUp Walk-in runs the front door of your business, so it holds what matters: your customers' names and numbers, your team's sign-ins and the records of your shop. Connections are encrypted, every request is checked against who may see it, secrets are hashed or encrypted before they are stored, and the changes that matter are recorded. The same core safeguards protect every plan and every location.

What we do not claim. Our information security policy, adopted in November 2026, is modelled on NIST SP 800-53 and the NIST Cybersecurity Framework and reviewed once a year (the first review is due in November 2027). We do not claim compliance with either, and we hold no certification: no SOC 2, no ISO 27001. Company sign-in (single sign-on) is an additional sign-in option on the Pro plan and up.

  • Encrypted on every public connectionHTTPS with TLS 1.2+ on every connection to the site and API, behind Cloudflare's network, with the database on a private network and off the public internet.
  • Only the right people get inOwner, manager, team member and accountant roles, optional two-factor sign-in (strongly recommended, and the owner can require it for everyone in the business; a company sign-in counts as the second step for people who belong only to that business), and accounts that lock after repeated failed attempts.
  • Your data stays yoursPasswords are hashed, secrets and staff PINs are encrypted, and each business's data is kept separate from every other business's.
  • Built to keep runningEncrypted backups every hour, kept off-server and restore-tested, and messages that survive restarts.
On every public connection
TLS 1.2+
Audit records kept
3–7 years
Encrypted backups
Every hour
Monthly uptime target, with credits
99.9%

Answering a security questionnaire for your company? Write to support@nextupwalkin.com and we will send you our answers where we can. This page describes the controls we use today. It is a description, not a warranty, and our Terms of Service govern.

How your data is protected

From a customer's phone to an encrypted backup

  1. A phone or screenEncrypted (TLS 1.2+)Nobody on the Wi-Fi or network in between can read what is sent.
  2. CloudflareShieldedEvery visit passes through Cloudflare's security network before it can reach our server.
  3. The APIChecked every timeEach request is verified on the server, and one business can never see another's data.
  4. The databaseOff the internetOn a private network, so it cannot be reached from the public internet.
  5. BackupsDatabase copy every hourEncrypted, stored away from our servers, and proven by a restore test every month.

Infrastructure

Hardened at the edge, private at the core.

  • Encryption in transit

    Everything sent to and from NextUp Walk-in is encrypted.

    Every connection is served over HTTPS with TLS 1.2 or later, using certificates that are issued and renewed automatically.

  • HTTP Strict Transport Security

    Browsers will only ever connect to us securely.

    Browsers are instructed to refuse unencrypted connections to NextUp Walk-in for a full year, including subdomains.

  • Strict Content Security Policy

    No ad trackers or outside code run on your pages.

    The details

    Scripts are restricted to NextUp Walk-in's own code: no advertising scripts, social trackers or third-party fonts on the website or in the app (some emails load Google Fonts, and the campaign image search shows pictures from Pixabay). The one outside script is Cloudflare Web Analytics' cookieless page-view count on the marketing site, and NextUp Walk-in counts its own page views as daily totals, with no cookies and nothing that identifies anyone. Framing, MIME sniffing and device APIs like the camera are also blocked. The microphone and location are allowed only on NextUp Walk-in's own pages and only after the person allows them: the microphone for voice check-in at the Door Tablet, and location for the optional “how far away are you” estimate on a customer's place in line, where the browser works out the distance, only the minutes are sent and the position is never stored. The browser turns speech into text; NextUp Walk-in never receives the audio and doesn't keep the words.

  • Network isolation

    The database cannot be reached from the internet.

    Application services talk to each other on an isolated private network. The database and its connection pooler publish no ports to the internet at all; only the web server faces the outside world.

  • Flood and slow-attack limits

    Floods of traffic are cut off before they reach the app.

    The web server limits each address to 600 requests a minute, caps the size of a request, and drops connections that send their headers too slowly, so one source cannot tie up the service.

  • No caching of account data

    Private data is never left behind in a browser or proxy cache.

    The details

    API responses that carry account, queue or customer data are marked private and no-store, so that data is not kept in a browser or a shared proxy cache. Only content meant to be public, such as team photos, logos, gallery and catalog pictures and public wait-time pages, is cacheable.

Application security

Defenses built into the product, not bolted on.

  • Rate limiting and abuse protection

    Bots and password guessers are slowed down automatically.

    Per-client limits on sign-in, joining a line, outgoing email and other sensitive endpoints, with IPv6 networks limited as a whole.

  • Hardened session cookies

    Sign-in sessions cannot be read by page scripts or set by other sites.

    Sessions use HttpOnly, Secure, SameSite cookies that page scripts can never read, and sign-in cookies carry the browser-enforced __Host- prefix (the rest __Secure-), so no other site or subdomain can set or replace them.

  • Cross-site request protection

    Other websites are blocked from acting as you while you are signed in.

    Beyond SameSite cookies, every signed-in change must come from our own pages (a checked Origin or Referer, or a custom header), so a page elsewhere, even on a sibling subdomain, cannot submit actions on your behalf.

  • Verified payment events

    Only genuine payment events from Stripe can change your account.

    Every Stripe webhook is signature-checked, and the subscription is confirmed directly with Stripe before access changes.

  • Validated uploads

    Only real images are accepted, nothing disguised as one.

    Logos and team photos are verified by file signature and dimensions. Only PNG, JPEG and WebP are accepted, never SVG.

  • No custom code from accounts

    No account can inject code into a page.

    Branding is structured settings only: no custom HTML or CSS, and colors are checked for readable contrast.

  • Tested before every release

    Thousands of automated tests run before changes reach you.

    Before a batch of changes is promoted toward production, we run a full automated test suite (thousands of integration tests against a real database). An urgent fix may ship after a narrower set of checks.

  • Dependency and code scanning

    Known-vulnerable libraries are caught before a release.

    Every release check scans our server and web dependencies for published vulnerabilities and runs a static code scan, alongside GitHub security alerts on the code.

Data protection

Credentials and secrets are hashed or encrypted before they are stored.

  • Password hashing

    Your password is never stored, only a salted, one-way fingerprint of it.

    Passwords are salted and hashed with PBKDF2 (HMAC-SHA512, 100,000 iterations), the default of the ASP.NET Core Identity library our API uses, and are never stored in a form that can be read back.

  • Leaked passwords refused

    A password already exposed in a data breach cannot be used.

    New passwords need at least 10 characters, cannot be a common password or your own email, and are checked against the Have I Been Pwned breach list using k-anonymity: only the first five characters of a hash ever leave our server, never the password.

  • Encryption at rest for secrets

    The most sensitive secrets are encrypted inside the database and its backups.

    Two-factor secrets and queued messages, including phone numbers and sign-in links, are encrypted in the database and in backups, and so are a company sign-in’s OpenID client secret and the private key of any certificate NextUp Walk-in makes for a SAML sign-in.

  • One-way hashed credentials

    Sign-in links and codes are stored in a form that cannot be read back.

    The details

    Emailed sign-in links (including the link that confirms a first company sign-in), sign-in codes, recovery codes and a company sign-in’s user-sync (SCIM) token are stored only as one-way hashes. A staff PIN is hashed to sign staff in, and kept encrypted so only the owner can read it back.

  • Payments processed by Stripe

    Card numbers never touch our servers.

    Checkout and billing run on Stripe. NextUp Walk-in never sees or stores a card number.

  • Private customer links

    A customer's place in line sits behind an unguessable link.

    Each customer's status link carries an unguessable token, and a strict referrer policy keeps it from leaking to other sites.

Access control

The right people, with exactly the permissions they need.

  • Two-factor authentication

    A stolen password alone cannot get into an account.

    The details

    Authenticator-app codes (TOTP) with one-time recovery codes, strongly recommended and offered to everyone, and the owner can require it for everyone in the business. Once enabled, a code is required on every sign-in method except a passkey, which counts as both factors, and a company sign-in (single sign-on), which counts as the second step because NextUp Walk-in relies on your company’s own multi-factor policy (an owner can turn on a check that the provider reported multi-factor sign-in). A person who also belongs to another business on NextUp Walk-in gives their authenticator code instead, or confirms by an emailed link if they have none. The platform admin area is the exception: it always asks for the authenticator code. Used codes cannot be replayed. Lost the authenticator and the recovery codes? “Can’t use your code?” starts a recovery: an emailed single-use link, then a waiting period (3 days, 7 for owners and managers, which NextUp Walk-in may extend to at most 30 days in all) with notices to the account and the business’s other owners and managers, who can cancel it. If you can no longer open that email, we may also ask for a photo ID and selfie check through Stripe.

  • Passkeys

    Sign in with your face, fingerprint or screen lock: nothing to phish.

    The details

    Owners, managers and team members with an email sign-in can sign in with a passkey (WebAuthn): a fingerprint, face or screen lock instead of a password. Each sign-in needs your device and its verification, only works on our own site, and is single use. Up to 10 per person, removable any time. Passkeys work on the website for now, not inside the Android app yet, and the iPhone app is coming soon.

    How passkeys work
  • Single sign-on and user sync

    Larger teams can sign in with their company login (Pro and up, on request).

    The details

    On the Pro plan and up, turned on for a business on request, the owner can connect the company’s own login over OpenID Connect or SAML 2.0, so people sign in through it. The company’s email domain is proved by a DNS record first, signed tokens and responses are checked and each works once, a NextUp Walk-in platform admin account can never sign in this way, the OpenID client secret is stored encrypted, and every change and sign-in is in the activity log. SCIM 2.0 syncs users and groups: it adds and turns off people, ending their sessions, and the groups it pushes can set the manager or staff role, or give a custom role. A company sign-in counts as the second step, except for a person who also belongs to another business on NextUp Walk-in, who gives their authenticator code or confirms by an emailed link. Unless the owner turns on the optional check that refuses a sign-in the provider does not report as multi-factor, NextUp Walk-in does not check that the provider asked for one, so the company should require multi-factor sign-in at its provider. The provider can sign people out of NextUp Walk-in (OpenID back-channel logout, or a SAML single-logout request the provider sends), and the owner can limit how long a company session lasts. An optional Required mode refuses every other way in for the business’s own team on the company’s addresses, with the business’s owner exempt; someone who is not on the team keeps an ordinary sign-in. The owner can list the groups that mean manager and staff, and the role follows them at each sign-in and when the provider changes a group (an owner is never changed). The owner can also choose that Required applies only to people in chosen groups, list up to five emergency sign-ins that keep a password while Required is on, and allow chosen managers to set company sign-in up (who the identity provider is, the SCIM token, Required, the emergency sign-ins, NextUp Walk-in’s certificates, the session and multi-factor settings, removing a sign-in and anything that would make new people managers stay with the owner). A tile or bookmark in a company app launcher can open the sign-in link. For SAML, the owner can also let the provider’s own tile start a sign-in (off unless turned on, only for people who already belong to the business, fresh and used once, and a session already open in that browser is replaced only after the person confirms), encrypt the sign-in answer to a certificate of NextUp Walk-in’s own, and have the requests NextUp Walk-in sends signed. Custom roles are named sets of the manager permissions, made by the owner. We hold no SOC 2 or other certification.

    How single sign-on works
  • AI assistants: read-only

    AI assistants can see only what is already public.

    The details

    NextUp Walk-in has a public MCP server so assistants like ChatGPT and Claude can look up a business. Every tool is read-only and returns only what the business’s public Check-in Page already shows: its live wait, hours, services with prices and open booking times. There is no sign-in, no customer data, and the assistant cannot join a line or book for anyone.

  • Role-based access control

    Each person sees only what their role needs.

    The details

    Owner, manager, team member and accountant roles (the accountant role is read-only, with exports), and custom roles, which an owner makes as named sets of the four manager permissions. Billing, branding, invitations, roles, the audit trail, deletions, client import, and sending or scheduling email campaigns are restricted to owners, enforced on the server.

  • Tenant isolation

    Each business sees only its own data.

    Each request is checked on the server against business membership, and a request for another business's data returns not found.

  • Limited, recorded support access

    Support steps in only with a stated reason that the owners are emailed, and every step is recorded.

    The details

    To answer a support request, a NextUp Walk-in platform administrator can open a business’s dashboard as its owner, or look up its stored records in a read-only tool that hides passwords, tokens and keys. The administrator must first unlock the admin area with an authenticator code and type why they are opening the dashboard; the business’s owners are emailed that reason. A dashboard session ends by itself after at most 1 hour, and payments, refunds, payouts, team and account actions, marketing sends and deleting data are refused during it. Every session and every lookup is recorded in our admin audit log, and the opening of a session, its reason and what is done in it appear in the business’s activity log as NextUp Walk-in support under the administrator’s name.

  • Brute-force lockouts

    Repeated wrong guesses lock the door automatically.

    The details

    Accounts lock automatically after repeated failed attempts at passwords, emailed codes, authenticator codes and staff PINs, with separate limits and time-limited lockouts per method. A company sign-in’s own failed attempts are counted by the company’s identity provider; an account that NextUp Walk-in has locked is refused on company sign-in too.

  • Instant session revocation

    Change your password and every other device is signed out.

    Changing a password, or choosing "sign out everywhere", ends every other session on its very next request.

  • Location-bound device access

    A front-desk device works for its own location only.

    Front-desk devices sign in with a per-location PIN. The session only works for that location and ends when the PIN changes.

  • Tablet PIN guessing blocked

    Guessing a front-desk PIN is shut down, without locking the shop’s own tablet out.

    Wrong PINs are counted per location and address (and per wider IPv6 network), a location-wide lock stops spread-out guessing while devices the shop already uses keep working, and the owners get an email alert.

  • Detailed audit trail

    See who changed what, when and from where.

    Sign-ins and changes to passwords, PINs, team, company sign-in settings, locations, branding and billing are recorded with who, when and from where, and kept for 3 years (7 years for payments, refunds and other money).

  • Account enumeration resistance

    Probing which email addresses have accounts is made hard.

    A sign-in attempt for an unknown email is made to take about as long as a real one, which makes it harder to probe which addresses have accounts.

Privacy

Privacy by design: collect little, show less, delete on schedule.

  • Minimal data collection

    Customers share a name; anything more is optional unless the business needs it.

    Customers join a line with a first and last name. A mobile number and an email address are optional unless the business requires a number, and there is no account to create or app to install.

  • Discreet public screens

    The lobby TV shows a first name and initial, never contact details.

    The TV and Check-in Pages show only a first name and last initial, never a full name, phone number or email. A photo a customer adds at check-in is shown only to staff at that location, never on the TV, Check-in Page or Door Tablet.

  • Automatic deletion

    Personal data is cleaned up on a schedule.

    Phone numbers leave the live queue after 24 hours, and check-in photos are deleted when the visit ends. Finished visits are removed after 400 days; a client profile stays until the customer asks to be forgotten.

  • Photo metadata stripped on upload

    Photos lose their hidden location and device details.

    GPS location, device details and capture times are removed from logos, team headshots, check-in photos, reference photos and photo IDs before they are stored or shown.

  • Private photo ID and reference photos

    IDs and reference photos stay private and are deleted on schedule.

    The details

    Where a business asks for them, a customer's photo ID and reference photos are stored privately, shown only to that business's staff and never cached. Photo ID is deleted 7 days after the visit and reference photos after 90 days. Photos added to a form and pets’ vaccine photos are stored the same private way, and are deleted with the form or, for a vaccine photo, when it is rejected or its vaccine record is removed. A studio that takes a guardian’s consent for a client under 18 also keeps that guardian’s ID, the minor’s ID and the minor’s date of birth for the days it chooses, 7 by default. NextUp Walk-in is not a medical record system and doesn't sign HIPAA business associate agreements.

  • Phone numbers kept out of logs

    Phone numbers and private links never land in our server logs.

    Our web server request logs replace phone numbers and private link tokens with REDACTED and never record the page a visitor came from.

  • Crash reports without customer details

    Error reports never carry customer contact details.

    Our error monitoring sends no personal data by default, and phone numbers are masked in error events and traces from both the app and the server.

  • Defined retention

    Every kind of record has a set lifetime.

    The details

    Most records have a set lifetime: visit history about 13 months, bills and payments 7 years, audit records 3 years (7 for money), web server logs 90 days, and expired sign-in links one week. Client profiles are the exception: they stay until the customer asks to be forgotten.

  • Take your data with you

    Your data is yours to download at any time.

    The details

    Owners can download one zip of their clients, services, team, visits, appointments, payments summary, gift cards and store credit as spreadsheets and JSON. The emailed link works for 24 hours and each step is logged. Customers can download or delete their own data from their account.

  • Consent-based messaging

    Every marketing email carries an unsubscribe link.

    Email campaigns reach subscribers and an owner-attested list of recent clients, each email with an unsubscribe link.

Reliability

Built so that a restart, a deploy or a provider hiccup does not lose queued messages.

  • Durable delivery for every message

    Queued messages survive restarts and deploys.

    Emails are durably queued, survive restarts and deploys, and retry automatically with backoff.

  • Self-healing service

    If the app stops answering, it restarts itself.

    A health check restarts the API after three failed checks in a row, and the web server holds requests for up to 30 seconds during a restart instead of failing them.

  • Automated backups every hour

    An encrypted copy of the database every hour, restore-tested every month.

    A full database backup runs every hour, is checked for completeness, encrypted and stored off-server; uploaded files and photos are backed up four times a day. We test restoring from these backups every month.

  • 99.9% monthly uptime

    A 99.9% monthly uptime target, backed by service credits.

    The details

    The Terms of Service target 99.9% uptime each calendar month for signing in, joining a line, and running the queue. A month that falls short earns a subscription credit when the business asks for it within 30 days after the month ends. Text and email delivery, a company sign-in that fails because the company’s own identity provider is unavailable or its settings with it are wrong or expired, and the other exclusions in section 14 of the Terms sit outside that target. Uptime is monitored independently, with live status and the last 90 days of uptime at status.nextupwalkin.com.

Exactly where we stand

Transparency is part of security, so here it is in plain terms.

  • We show only what we have earned: no SOC 2 or ISO 27001 certification and no independent penetration test yet, so you will never see a badge here we have not been granted.
  • Customer names, phone numbers, email addresses and photos are protected by strict access control and by keeping each business’s data separate, and every backup is encrypted.
  • Roles stay simple and clear: owner, manager, team member and accountant (read-only), plus custom roles an owner builds from four manager permissions (refunds, team pay, change prices, manage company sign-in).
  • A written incident-response plan: if we confirm a breach affecting your customer data, business owners hear from us within 72 hours of confirming it, as section 11 of the Terms of Service and the Data Processing Addendum commit.
  • Your records stay in your hands: owners can export the activity log, which records the IP address of each request, and a business can stream its company sign-in log to its own collector over TLS as syslog, without IP addresses, tokens or secrets.

Responsible disclosure

If you believe you've found a security vulnerability in NextUp Walk-in, email security@nextupwalkin.com with a description and the steps to reproduce it. Please give us a reasonable opportunity to fix the issue before disclosing it publicly, and avoid accessing data that isn't yours. Please do not use denial-of-service, social engineering or physical attacks, and stop and tell us as soon as you reach another person's data. The same contact is published in our security.txt file.

The same core protection on every plan.

The built-in safeguards on this page are on from the moment you create your account, for one location or fifty. Options you choose, such as two-factor sign-in, passkeys and company sign-in (which comes with the Pro plan and up and is turned on for a business on request), are yours to turn on. There's no security add-on to buy. Security is shared: we run the service and the safeguards on this page, and your business runs its own accounts, devices, staff PINs, API keys and identity provider, including who has access and whether multi-factor sign-in is required.