# Data Processing: Roles, Retention, Deletion | NextUp Walk-in

Source: https://nextupwalkin.com/data-processing

> For compliance reviews: your business controls customer data and NextUp Walk-in processes it for you. Our commitments, subprocessors, retention and deletion.

# Data processing

Last updated November 18, 2026

For a business's compliance or procurement review: how NextUp LLC handles data, who is responsible for the data in NextUp Walk-in, what is stored, where it goes and when it's deleted. Our [Terms of Service](https://nextupwalkin.com/terms-of-service) (in particular sections 11, 12 and 19) and the addendum below are part of the binding agreement between your business and NextUp LLC, together with the other documents listed in section 21 of the Terms.

## Data Processing Addendum

**Version 2026-11-04 · Effective November 18, 2026**

This page is NextUp LLC's standard Data Processing Addendum (DPA). Together with our Terms of Service, it describes the terms on which NextUp Walk-in processes your customers' personal data on your behalf, and the information about your team members that it handles for you when you use company sign-in. You can save or print a copy for your records with the button below.

This addendum applies automatically to every business that accepts our Terms of Service, from the day it does, and needs no signature. It is not legal advice for your business. If your organization requires a signed copy, you may email [support@nextupwalkin.com](mailto:support@nextupwalkin.com); we may, at our choice, countersign this standard addendum unchanged, and we do not sign other forms.

This addendum is part of our Terms of Service and applies to your use of NextUp Walk-in under them, and is subject to them, including the limits of liability in section 17 and the dispute rules in section 20; it adds no separate liability. If it conflicts with the Terms about how we process your customers' personal data or the company sign-in records it describes, this addendum applies to that; otherwise the Terms apply. We may update this addendum under the in-app review and acceptance process in section 22 of the Terms.

## Roles

**Your business controls your customers' data, and NextUp Walk-in processes it on your behalf**, only to provide the service. You decide much of what's kept: whether customers can add a photo, what your intake questions and forms ask, and what your team writes on a client's profile. You're responsible for having a lawful basis and giving customers any notice they need from you.

**Your team's company sign-in data.** If you turn on company sign-in (single sign-on), the identity information described under "What we process" for it (your team members' work email addresses, names, provider IDs, groups and roles) is also processed by NextUp Walk-in on your behalf, as your service provider, and this addendum applies to it as it does to customer data, except that the breach notice for it is the one stated under "Our commitments". The same applies to the other records you keep about your team on the service (schedules, hours, pay records, photos and roles): you decide what to record and why, and we process them on your behalf, only to provide the service. We also use a team member's name, email address and IP address ourselves to run, secure and audit the service, as the Privacy Policy describes. NextUp LLC is the controller of the rest of the information in your NextUp Walk-in account (for example your own name, email address, sign-in and billing records), which the [Privacy Policy](https://nextupwalkin.com/privacy) describes.

**Protected health information is outside this service.** NextUp Walk-in is not a medical or patient record system, doesn't file insurance claims and doesn't sign business associate agreements. If your business is a HIPAA covered entity or business associate, don't put protected health information in it (Terms section 9); keep charts and treatment notes in a system built for them. Health answers a business asks for to run a visit safely, such as allergies or an injury, are customer data like any other under this addendum. If we learn that protected health information has been put in it, we tell the business and may remove it.

## Details of the processing

**Purpose and instructions.** We process this data only to provide, secure, support and improve the service for you, and to meet legal duties. You disclose personal information to us only for the limited and specified business purposes in this addendum. Your instructions to us are this addendum, the Terms, and how you use the service's settings and features, and we process customer data only on them. If we believe an instruction would break the law, we will tell you.

**Who and what.** The subject matter is running your line, bookings, client records, messages, payment records, team management and company sign-in. The people are your customers and prospects, callers and website visitors, your team members and people you invite, and anyone you add to your records. The kinds of data are listed under "What we process". We process it for as long as you use the service, and then as "Retention" says, by storing, showing, sending, deleting and backing it up.

**Same protection.** We comply with the California Consumer Privacy Act as it applies to us as your service provider, and with the other United States state privacy laws that apply to us as your processor, and give the personal information the same level of privacy protection they require of you.

**De-identified data.** Where we make aggregated, de-identified data as Terms section 11 allows, we take reasonable measures so it cannot be linked to a person, and we do not try to re-identify it.

**Where this applies.** NextUp Walk-in is for businesses in the United States (Terms section 9) and our servers are in the United States. This addendum is written for United States privacy law, including the California Consumer Privacy Act as amended. We do not offer the transfer terms used for data about people in the European Economic Area, the United Kingdom or Switzerland.

## What we process

- **Visits:** the name a customer gives and, only if they choose, their mobile number, email address and photo; whether they agreed to texts; their answers to your intake questions; what they asked for; and when they joined, were called and were served. A number is kept whether or not the customer agreed to texts, unless they chose "Don't keep my details"; it is texted only with their consent. Text messages with a customer are kept with their visit.
- **Client profiles:** when a customer joins with a mobile number, or your team adds them, your business gets a profile with their name, number, email if given (for a team-added customer, only if your team saves it), visit counts, and anything your team adds, such as notes, tags, a photo, birthdays, pets and dated records like vaccinations. No profile is kept when a customer chooses "Don't keep my details" or asks your team not to keep them. Client records you add by hand or import are profiles too; only an owner can import them, and they are for your team's records only.
- **Email audience:** your email campaigns and rebooking reminders go to the email addresses on your customers' visits (check-ins, visits your team adds and appointments), except customers who unticked "Stay in the loop" (it starts ticked) or said no on a later visit; campaigns also go to members who left the membership emails box ticked, and to the clients on the email list the owner imported (see below). A record you added or imported on the Clients page isn't in campaigns until that person has a visit with that address. Your unsubscribe list is always skipped, every email has an unsubscribe link, and a campaign can't be sent or scheduled without your postal address. The only list of addresses that can be uploaded to email is the business's one-time import of its own clients seen in the last 12 months, which the owner signs for; each person gets a welcome email with an unsubscribe link first. No list of numbers can be uploaded to text.
- **Bookings and extras** you turn on: appointments, signed forms and waivers, loyalty stamps, gift cards, packages and memberships, and private ratings after a visit. For a house call, we process the service address and any pin set for it. If the customer chooses device location to look up the address, we receive the coordinates and may use a rounded position with the lookup provider. A team member can use coordinates for trip directions. If they turn on customer-facing sharing, we keep the most recent point for the booking view and prune old points using a three-hour age threshold.
- **Reference photos and photo ID**, if you turn them on for a location: up to 3 reference photos and one photo ID a customer sends with a place in line or a booking (a photo ID only after the customer ticks that they agree to share it), with the body area, size and note a tattoo customer picks. Stored privately with location and device details removed, shown only to your staff, never to other customers or on public screens. We don't read or verify IDs.
- **Clients under 18**, if you turn on guardian consent for a location (tattoo and piercing studios): the client's date of birth; the guardian's name, relationship and one phone number (no guardian email is kept); a photo of the guardian's ID and of the client's ID or proof of age (sent only after a tick that they agree to share it); the consent wording shown and the typed signature, time and IP address; and who confirmed or overrode the check at the door, and why. An adult's date of birth is checked and not kept. Stored privately, shown only to your staff. We don't verify age, identity or guardianship.
- **Records and photos by trade**, if you use them: client records for hair, nail, lash, tattoo, massage, pet, vehicle and device details (including a pet's breed, temperament and birthday, and a vehicle's plate, VIN and mileage; never a device passcode), job tickets and estimates with their photos, photos added to forms, pets' vaccine photos waiting for your review, documents-needed lists, and member pass links with the plates a plan covers. Cascades with the client.
- **Emails we send for you** to your customers' addresses: estimate and follow-up reminders, pick-up notices, waiver and form links (also to a signed guardian), missing-document and tax-date reminders, pet birthdays, vehicle service due, and member messages. Marketing-type ones follow the same consent and unsubscribe rules as your campaigns. Eligible members who leave the membership emails box checked may receive marketing emails. We keep that choice with the wording, time, IP address and browser details.
- **Events you send out:** if you set up webhooks or Zapier, the events for visits, appointments and job tickets (a ticket event has the ticket number, trade, stage, status and the customer's first name; no phone, email or link) go to the addresses you choose. Our delivery log keeps them for 30 days.
- **Door-tablet appointment lookups:** if you turn on "I have an appointment", a customer's typed number is matched exactly against upcoming appointments, and only a first name, the time and the service are returned.
- **Your website**, if you publish one: its pages and pictures, and what visitors send through its forms (the name and email address they give, their message, the page, the time, and for a newsletter sign-up the consent wording they ticked), which we also email to you. Page views are counted as daily totals per page, with no cookie, IP address or visitor ID kept.
- **Payments:** card details are entered with and held by Stripe. NextUp Walk-in never sees or stores a full card number; for a saved card it keeps only the brand, the last four digits and the expiry date. With Amazon Pay, Cash App Pay, bank debit (ACH), pay-over-time plans or stablecoin, the customer signs in, links their bank or pays from a wallet with Stripe and the provider; we never see a bank account number, a sign-in or a wallet's keys, only the method used, and a bank payment stays "processing" until Stripe confirms it. Venmo, Zelle and PayPal payments your team records are a method and an amount only; we exchange no data with Venmo, Zelle or PayPal.
- **Your account:** your team's names, emails, photos and roles (including custom roles), their schedules, hours and pay records, your locations, settings, catalog and branding, and the activity log.
- **Company sign-in (single sign-on)**, if you turn it on: for each connection, your identity provider's settings (addresses and public certificates; an OpenID client secret and any private key for a certificate we make for you are stored encrypted, and a user-sync (SCIM) token only as a one-way hash), the email domains you proved and the DNS proof, the ID your provider uses for each person linked to their account, the groups it reports for them at their last sign-in and sends through user sync, the record user sync keeps for each person, the groups you set to give custom roles, the emergency sign-ins you list and the people removed from your team (so company sign-in does not add them back), single-use confirmation links we email (kept as one-way hashes), the connection and provider's session tags that let the provider sign a person out, short-lived ids of provider responses (hashed) and of sign-out messages already used (so a replay does nothing), the log collectors you name (an address, a port and an optional public certificate), and reminder records for expiring certificates and secrets. Sign-ins and changes are in the activity log, which you can download, pull, or have sent to a log collector you name. Each event sent carries the person's work email address and the outcome, never an IP address, token or secret; the collector is yours, not our subprocessor. We do not keep the tokens your provider sends. You, not NextUp, decide who may sign in this way and what your provider tells us; the people are your team, and your provider is yours, not our subprocessor. The commitments below apply to this information in the same way as to customer data, except that the breach notice for it is the one stated in the last commitment.

## Our commitments

- Use customer data only to provide, secure, support and improve the service (without building profiles of your customers for anyone else), and as the law requires.
- Never sell it, and never use customers' numbers or texting consent for NextUp's own marketing.
- Protect it with reasonable administrative, technical and physical safeguards suited to the risk, of the kinds described on our [Security page](https://nextupwalkin.com/security), such as encryption in transit, optional two-factor sign-in, role-based access, an audit trail and encrypted off-server backups.
- Limit access to the people and service providers who need it to run the service, including time-limited support sessions that are recorded (see the Security page).
- Never sell or share it, keep, use or disclose it outside our direct business relationship with you, or combine it with data from other sources, except as the California Consumer Privacy Act allows. We understand these restrictions, will comply with the CCPA obligations that apply to us as your service provider, and will give the same level of privacy protection as the CCPA requires. We will tell you if we can no longer meet these obligations.
- Give you, on reasonable request, the information you need to show that your customer data is handled as this addendum says, and answer reasonable security questionnaires to the extent we are able to. Once in any 12 months, you or an independent assessor you choose who is not a competitor of NextUp, under a confidentiality agreement, may review our written security documents and ask us questions by email or video call, during business hours and at your cost. This does not include access to our systems, source code or premises, to other customers' data, or to our providers' systems or audit reports, which we share only as the provider allows.
- Help you, with information we have, with any data protection or risk assessment the law asks you to do about the service.
- If you tell us customer data is being used in a way this addendum doesn't allow, let you take reasonable steps to stop it and fix it, and work with you to do so.
- Keep everyone who handles it for us bound to confidentiality, and use only subprocessors that handle customer data under written terms (for a large platform such as Google, Microsoft, Apple or Meta, its standard terms) that limit its use of that data to providing its service and require it to protect the data. We email business owners at least 15 days before a new subprocessor starts handling customer data; if you object and we cannot resolve it, you can end your subscription and we refund the unused prepaid period.
- Help you answer your customers' requests to access, correct or delete their information. If a customer sends us a request about data we hold for you, we pass it to you and do not answer it ourselves unless you have authorized us to carry it out.
- Delete it on the schedule below, when your business is deleted, and when you ask us to at the end of your service, unless the law requires us to keep it; you can export it first (see "Deletion and export").
- Tell you within 72 hours of confirming a security breach affecting your customer data, with what happened, the data involved and what we are doing, and as the law requires. For a breach affecting your team's company sign-in data, we tell you without undue delay after we confirm it. A security breach means unauthorized access to, or acquisition, loss or disclosure of, data held by us or by a subprocessor for us. It does not include unsuccessful attempts (such as scans, pings or blocked sign-in attempts) or authorized access. Using a valid credential, device, API key, staff PIN or identity provider does not by itself establish authorization. A notice is not an admission of fault or liability. Where the law sets a different deadline for us, we meet that one.

## Subprocessors and location

NextUp Walk-in's servers and database are in the United States. The outside services that handle data, what each one gets and where, are listed on our [subprocessors](https://nextupwalkin.com/subprocessors) page, which we update when that list changes.

## Retention

### The mobile number on a visit

Kept for

Removed from the line entry 24 hours after the customer joins; kept on the business's client list unless the customer chose "Don't keep my details"

### The mobile number on a booking

Kept for

Deleted 24 hours after the appointment time

### The photo a customer adds at check-in

Kept for

Deleted when their visit ends, and never kept longer than 24 hours after they join

### A photo ID sent with a visit or booking

Kept for

Deleted 7 days after the visit or appointment, or sooner when removed

### Reference photos sent with a visit or booking

Kept for

Deleted 90 days after the visit or appointment, or sooner when removed

### Guardian consent for a client under 18: ID photos and date of birth

Kept for

The days the business chose for the location (7 by default, at most a year) after the visit, or sooner when removed or the client is deleted

### Guardian consent for a client under 18: the signed consent

Kept for

With the client’s signed forms, until the client is deleted

### Photos added to a form, and pets’ vaccine photos

Kept for

A form photo: with the form it came with. A vaccine photo: until the business rejects it, or, once approved, with the pet’s vaccine record until that record is replaced or removed. Both sooner when the client or business is deleted

### Webhook delivery log

Kept for

30 days

### Membership email consent (when and how the member agreed, and the wording they saw)

Kept for

While the person is a member and for 3 years after the membership ends, then deleted; sooner if the member asks to erase their details or the business closes its account

### Membership renewal agreement (plan, price, wording, time, IP address, browser)

Kept for

While the person is a member and for 3 years after the membership ends, then deleted; sooner if the member asks to erase their details or the business closes its account

### A line entry nobody closed out

Kept for

Expired after 12 hours

### Proof of text and call consent (including marketing opt-ins and withdrawals)

Kept for

At least 5 years after the last message to that number or the withdrawal, whichever is later, kept in minimal form even after a client, location or business is deleted

### A business that has been inactive (Free or ended trial, never paid)

Kept for

May be deleted with its data after 11 months with no sign-in, session, dashboard change, visit or booking, one warning email to its owners and 30 more days without a sign-in or any use. A paid business is never deleted this way

### Message records

Kept for

The text of a message: 13 months. Its time, delivery status and consent reference: 5 years. A do-not-text entry: as long as we use that sending number. An unconfirmed offers tick: 30 days. A Do Not Call Registry answer: 31 days

### Instagram and Facebook messages (AI front desk)

Kept for

90 days

### Support emails (the body of each message)

Kept for

365 days, then the text is blanked; the sender and date stay

### Contact form messages (name, email, business, topic and message, including the answers on a single sign-on request)

Kept for

3 years, or sooner if you ask us to delete them; the submitter’s IP address is scrubbed after 30 days

### Downloadable copies of your data

Kept for

7 days

### Call transcripts (AI phone receptionist; no audio is recorded)

Kept for

90 days, unless needed for a dispute, a legal hold or a regulator

### Finished visits (name, email if given, what they asked for, times)

Kept for

400 days (about 13 months), for busy-time insights

### A pet business’s visit timeline (the pet’s name, who had the pet when, calls and hand-offs, times, and the sedation and brought-in-by answers)

Kept for

3 years from the visit, as the business’s record of the pet’s care, or sooner when the business is deleted. When the client’s details are deleted, it is kept without their name

### Client profiles (including imported records), with their mobile number, and what your team adds

Kept for

Until the customer asks to be forgotten, or the business is deleted. A profile photo, saved by your team or by a customer who chose "Remember me", stays until it is removed, the customer uses "Forget me", or the profile is deleted

### Appointments

Kept for

While the business exists (the number is removed 24 hours after the appointment time; a deleted client’s appointments are kept as "Deleted client")

### Bills, payments and refunds (no customer name once the visit is deleted)

Kept for

7 years, for tax records

### Record that you accepted the Terms (version, time, IP address, browser)

Kept for

While the account exists; deleted with it

### Activity log

Kept for

3 years (activity about payments, refunds and other money: 7 years), or until the business is deleted, which deletes its activity log

### Sign-in attempt records (time, email typed, how the person signed in, outcome, IP address, browser, country, network)

Kept for

3 years. They belong to the person signing in, not to a business, so deleting a business does not delete them

### Signed-in session records (time, how the person signed in, IP address, browser)

Kept for

45 days after the session ends or was last used

### Company sign-in (single sign-on) records: provider settings, linked provider IDs, groups, user-sync records, the groups that give custom roles, the emergency sign-in list, provider session tags, used-response ids and reminder records

Kept for

While the company sign-in exists; deleted when the owner deletes it, when the person’s account is deleted, or when the business is deleted. Used-response ids and sign-out ids are kept for up to two hours and removed the next time one is recorded after they expire, or when the connection is deleted; a provider session tag is removed with its session record, 45 days after the session ends or was last used. Its activity log entries follow the activity log above

### People taken off your team (the list that stops company sign-in adding them back)

Kept for

While the business exists, until the person joins the team again, or until the person’s account is deleted; it is not deleted when the owner deletes a company sign-in

### Custom roles, and who holds one

Kept for

While the business exists; a role is deleted by the owner or with the business, and a person’s role ends when they stop being a manager or leave the team

### Log collector settings (host name, port and optional public certificate)

Kept for

Until the owner removes them, or the business is deleted

### Company sign-in steps under way, and emailed confirmation records

Kept for

A sign-in under way lasts 10 minutes (5 for a provider-started sign-in waiting for the person to continue) and a confirmation link 30 minutes. An expired sign-in record is removed within about an hour, and a confirmation record about a day after its link expires

### Email unsubscribe list (address, how and when)

Kept for

While the business exists, so an unsubscribe is always honored

### Sign-in links and email verification tokens

Kept for

7 days

### Business account data (locations, team, branding, catalog, settings)

Kept for

While the business exists; deleted with it

### Your website (pages, versions, pictures)

Kept for

While the site exists, including while it shows its holding page; deleted with the business

### Messages and sign-ups from your website’s forms

Kept for

400 days (about 13 months), or sooner when the business is deleted or the person’s details are deleted

### Shared inbox threads (number, name if given, message text)

Kept for

400 days (about 13 months), or sooner when the business is deleted or the client’s details are deleted

### Giveaway entries (name, number or email, age confirmation, email offers tick)

Kept for

400 days after the giveaway ends (a winner’s or alternate’s: 3 years), or sooner when the business is deleted or the person’s details are deleted

### Slow-day text log (number and date)

Kept for

90 days, or sooner when the business is deleted or the client’s details are deleted

### Email bounce and spam-complaint records (address, kind, date)

Kept for

3 years, or sooner when the business is deleted or the person’s details are deleted at that business

Backups normally follow a 30-day removal schedule. We may keep recovery copies and their dependencies longer to preserve a usable backup, including when uploads or cleanup are delayed. Copies of receipts, invoices and pay statements in backups are kept for 7 years, because tax records require it. To stop the free trial being reused, we keep one-way hashes of identifiers (email address, phone number, business name and city, Google place ID and card fingerprint) of a business that has used one, even after the account is deleted.

## Deletion and export

An owner can delete the business from the dashboard at any time, which deletes the data stored for it, including its client profiles, imported records, email unsubscribe list and its own bills, payments and pay records, except what we must or may keep: consent records for texts (at least 5 years, Terms section 12), NextUp's own billing records for the business's subscription (kept by Stripe and in our accounts), copies in backups for the periods stated under Retention, and the trial-reuse hashes described there. Export what the business needs for its own books and taxes before deleting it. The owner can delete a client from the dashboard; a customer can delete their own details with "Delete my details" on their visit's page or in their NextUp Walk-in account, or ask us by email. Their visits and payments stay as "Deleted client", without their name, number or email. Visit history, insights, the activity log, payments and team pay, the catalog and your email audience can be exported from the dashboard; for anything else, email us before deleting and we'll give reasonable help.

## Questions and requests

Security questionnaires, data requests and questions about this page: [support@nextupwalkin.com](mailto:support@nextupwalkin.com).
