Does PivotXP hold a SOC 2 or ISO 27001 certification?

No. PivotXP is a small in-house team and does not hold SOC 2 or ISO 27001 certification. Instead we publish a one-page security and operations posture covering data ownership, encryption, retention, remote access, AI use, support, and the procurement documents available on request, and we complete client security questionnaires directly. Procurement teams at national brands and their agencies have accepted this at our project size.

Where is guest data stored?

In PivotXP's United States cloud environment, encrypted in transit and at rest, with access limited to the PivotXP team working the program and the client contacts you authorize. Personal information is purged after the program closes and the final export is delivered unless a longer retention period is written into the SOW.

What happens if a kiosk fails during the event?

Every unit is burned in on the real program before it ships, carries a hardware watchdog that restarts a hung app on its own, and is reachable remotely by PivotXP engineers. Multi-unit footprints travel with a spare. For first live days, multi-unit footprints, or programs where the client is in the room, a PivotXP tech is on site.

For brand security reviews and agency procurement

Security + Operations Posture

The page we attach to every enterprise quote. It answers what a brand's security team and an agency's procurement group ask before a program: who can see guest data, how it is protected and for how long, how we reach a unit in the field, and what paperwork is ready. We do not hold a SOC 2; this is what we do instead, and it is written so a reviewer can check it line by line.

Request the Vendor Packet Data, Privacy + AI Statement

Data

Who owns guest data, and who can see it

Guest data belongs to the brand, or to the agency acting for the brand. PivotXP processes it on your behalf and never markets to guests, sells lists, or reuses guest content without written permission.

Access is limited to the PivotXP team members working the program and the client contacts you authorize. Admin roles are scoped per program, admin actions are logged, and access is removed when the program closes.

We do not run facial recognition and do not build profiles across programs. Each activation is its own dataset.

Encryption

In transit and at rest

Every guest-facing page, kiosk, dashboard, and export moves over HTTPS/TLS. Data is stored encrypted at rest in PivotXP's United States cloud environment, and vendor integrations run through secure, scoped endpoints rather than shared credentials.

Text and email delivery goes only to guests who requested it, from a sender identified with the brand, with the opt-in recorded and exportable.

Retention

How long we keep it

Personal information is purged after the program closes and the final export is delivered, unless you ask us to hold it for a set period, such as a season lease or a sweepstakes with a fulfillment window. Aggregate counts stay in the reporting dashboard so year-over-year comparisons still work.

A written retention and deletion policy is available for procurement reviews, and the retention period for a specific program is written into the SOW.

Remote access

How we reach a unit in the field

Every kiosk and build is reachable by our engineers over an authenticated, encrypted remote-access channel, so most issues are fixed from our desk while the event keeps running. Access is limited to PivotXP staff and is logged.

Kiosks run locked down: guests cannot leave the experience or reach the desktop, and a unit can be restarted remotely if a tour manager needs a hand.

Where AI is used, and where it is not

When a program uses AI (trading cards, themed portraits, background replacement), we say so in the proposal, name the processing provider on request, and document the data flow: what is sent, what comes back, what is retained.

Guest photos are used to generate that guest's output and are not used by PivotXP to train models. Programs that do not use AI simply do not: capture, delivery, and printing run entirely on PivotXP systems.

Support

Support windows and escalation

A support line during setup and show hours is included with every program, staffed by the engineers who built it rather than a ticket queue. For programs where the client is in the room, a multi-unit footprint, or a first live day, a PivotXP tech is on site.

Custom builds include a remote support window after the event. Programs that keep running, such as permanent installs and season leases, carry a hosting and support subscription with a written SLA.

Operations

What happens before a unit ships, and while it runs.

Reliability is a process, not a promise. These are the checks every build goes through and the tools that keep it running on show day. Results per program are on the case-study pages.

Security + Operations Results by Program

Burn-in before it ships

Every unit runs the real program for days before it goes on a truck, in direct sun when the footprint is outdoors, so the first guest is never the first test.

Hardware watchdogs

A watchdog on the unit restarts a hung screen or app on its own, before a tour manager has to notice.

Reachable from anywhere

Every kiosk and build is reachable by our engineers, so most issues are fixed from our desk while the line keeps moving.

Offline first

Capture, scoring, and printing keep working when venue internet drops. Data syncs when the connection returns, with nothing lost.

Health dashboard during show hours

Each unit reports its status to one dashboard, so we see a problem forming before your producer does.

A spare on large deployments

Multi-unit footprints travel with a spare, and a tech on site swaps it in minutes.

Procurement paperwork

Ready on request.

Vendor onboarding at a national brand asks for the same five things every time. We keep them current so a first program with a new account does not wait on paperwork.

Email for the Packet (704) 284-7155

W-9 and certificate of insurance

Sent with the first quote on request. Coverage details and additional-insured wording are confirmed per program.

Data-flow statement

A one-page diagram of what is captured, where it goes, who can see it, and when it is deleted, specific to your program.

Retention and deletion policy

The written policy behind the retention section above, in the format procurement reviews expect.

Master services agreement

We work on your paper or ours. Mutual indemnity, content clauses, and payment terms are negotiated once per account, not per event.

Vendor onboarding

Supplier portals, security questionnaires, and accessibility statements completed by the people who run the systems, usually within a week.

Certifications

We do not hold a SOC 2, and we say so.

PivotXP is a small team of in-house developers and field technicians. We have not pursued SOC 2 or ISO 27001, and we will not claim a badge we do not have. What we offer instead is this page, the data-flow statement for your specific program, direct answers on your security questionnaire from the people who run the systems, and a retention period written into the SOW. Procurement teams at national brands and their agencies have accepted this at our project size. If your program requires a certified processor for a specific data category, tell us at the scoping call and we will structure the data flow so that category never reaches our systems.