Data Processing Agreement
For sites whose guests are in the EEA, the UK or anywhere with similar rules. In effect from 17 November 2026.
This agreement is between the site using vFound (the controller) and Naltyx Data and Marketing Consulting (the processor), and applies where we process personal data on your behalf under the UK GDPR, the EU GDPR, Canadian privacy law or comparable legislation.
Contents
1. Subject matter and roles
You decide why and how personal data about your guests and claimants is processed. We process it only to provide vFound to you. For your own account, staff sign-in and billing data we act as a controller. The site still controls its ownership claim and release decision. That is covered by our Privacy Policy, not by this agreement.
Optional Google Analytics on the public marketing website is separate controller processing described in our Privacy Policy. It does not receive site records, signed-in workspace activity or private guest workflows and is not a sub-processor of the site records under this agreement.
2. Details of the processing
- Subject matter: providing lost-and-found software: publishing found items, receiving and managing ownership claims and lost-item reports, alerts, pickups and returns, messaging between your team and a guest and, within an authorised customer group, sending found items between sites; and, if you switch on vFound Parcels, logging parcels your site receives for people and handing them over; and, if you switch on vFound Checkroom, checking guests' coats, bags and luggage in, recording stations and events, preparing them from an exit queue, recording optional fees and handing them back and, if you turn them on, taking advance luggage reservations for time windows you set and linking event ticket or wristband codes to checkroom tickets, and receiving a parent or guardian's under-18 form for a guest; and, if you switch on vFound Equipment, recording assets, reservations, multi-item and kiosk checkouts, borrower requests, maintenance and stock-takes, stock and consumables handed out by count, suppliers and purchase orders (a record only: vFound sends no order and makes no payment), taking equipment back, recording fees, deposits, payments you took and invoices, quotes and payment requests, delivery addresses and times, equipment rented in from a supplier, team notes on items, custom fields on borrowers and bookings and, within an authorised customer group, recording transfers between sites; and, if you switch on vFound Visitors, registering and approving visitors, creating multi-day passes, signing them in and out at a desk or paired kiosk, telling and receiving short replies from the people they came to see, importing verified calendar invitations, running roll calls, printing badges and recording couriers; and, if you switch on vFound Queue, giving people a number from their own phone or a paired kiosk, calling them from a counter and, where you turn them on, taking booked times, exchanging short messages, asking a short survey, recognising returning visitors who ask to be remembered and alerting your team to long waits; and, where your site uses it, keeping a minimal private hotel stay reference current for found items and parcels, including, on vFound Enterprise, through a customer-controlled, read-only Cloudbeds connection; giving a customer that owns several sites group-wide Network settings, with aggregate counts, group and regional access and explicit per-site policy application and, when it opts in, named versioned operating policies, local exceptions, acknowledgements and aggregate service-level monitoring; keeping your people list current from a CSV link or automatic provisioning; and giving each person a signed page for their own linked records.
- Duration: for as long as your plan is active, plus the retention period in section 9.
- Nature and purpose: hosting, storage, display, transmission by email, backup, security monitoring and deletion, including the scheduled report emails, with a CSV file attached, that your owner or manager sets for members of your team; transmission of an optional browser alert at the person’s request, from 25 October 2026 or sooner where you have agreed to the push services (see the notice below); AI suggestions and translation where you keep vFound AI switched on (section 4); looking up the approximate city, region and country of the IP address a claim or a lost-item report sent from your lost and found page came from; and sending data to services you connect yourself, such as Slack, Microsoft Teams, Google Chat, the calendar apps your team adds a private calendar link to, a reporting tool such as Power BI that reads a report data feed link your owner or manager makes, a directory or CSV source you choose, a hotel property or coworking member system you authorise, your own systems through our API and webhooks, or an AI assistant your owner or manager connects by signing in, which are yours to choose and instruct and not our sub-processors. An assistant you connect reaches only the tools its permissions allow, for the products you have open, and stops at once when you disconnect it; you pay for it and are responsible for your agreement with its provider.
- Types of personal data: claimant name, email address, optional phone number, description of the lost item, place and date of loss, answers to verification questions, photographs uploaded as proof, messages with your team, submitting IP address and the approximate city and region derived from it; for a lost-item report or alert, the guest’s name, email, optional phone, what they lost, any item-location link they add and any photo of the item they add to a report, and for a report sent from your lost and found page its submitting IP address and the approximate city, region and country derived from it; for a found-item message a member of the public sends to your site, the photo, the item description, the place and date it was found and where it is now, and an optional name, email and phone; for a return, a shipping address or the name and signature given at pickup, a booked pickup time and any feedback; for vFound Parcels, the name, email, room or apartment and any reference of each person on your parcel list, and for each parcel a photo of its label, the carrier, tracking number and sender, where it is kept, handling instructions, reminder snooze or hold date, desk arrival, delegate name and email, the notices sent, and the name, optional pickup photo and any signature of whoever collected it; for outgoing parcels and delivery rounds, the destination, courier or recipient and handover signature; for vFound Checkroom, a photo of what a guest handed in (shown on that guest's own private ticket page while the things are here, where you turn that on), its number and, where given, the guest's name, email, room and ticket language, its station, event and storage location, each piece's letter, type, storage location and hand-back state, a request to have it ready, any fee, currency and whether it was recorded as cash or an external POS or card payment, and who collected each piece, with a signature for a lost ticket, and, only where you turn on the matching Checkroom storage and queue choice, where things have been with the team member who moved them, when and from where, which team member checked a collector’s ID and when (never the document or its number), the pickup time a guest chose, To store and To fetch tasks with who took, was given or finished them, team members’ queue status (deleted when the To fetch list is turned off), and requests asking the ticket holder to approve someone else collecting (emailed only to the address given at check-in, kept as a keyed hash, with the collector’s name, the team member who asked, a partly hidden address, the answer and its time), and, whatever you choose, whether a hand-back compared the guest’s photo or scanned the tag, the team member who marked things missing or out for a while or reminded a guest about things left, and when, and the team member who blocked a hook number or opened extra ticket numbers; if you turn them on, each payment, deposit, tip or late fee recorded with its type, amount, method, kind of item, the team member who recorded it and any void, your team members' shifts with the cash they counted, the terms a guest accepted and any value declared, the reminders and disposal date for things left at closing and a note of any disposal, a guest's separate choice to receive offers and a survey answer; for vFound Equipment, each borrower's name and, where given, email, ID or reference and email language, what they borrowed and when it is due, the notices sent, any signature, reservations and their dates, approval state, extension requests and problem reports, and how each item came back with any note and photo; where you turn the options on or your staff use them, the terms text a borrower accepted with its fingerprint and time, a photo and note as each item goes out, the place, department, project or job it went to, who collected it and why, the trainings a person holds with their dates and an optional proof scan, borrower types, holds on borrowing with their reason, hand-over requests between borrowers, clearance certificates, directory group membership used for trainings, and returns made at a paired kiosk; where the reservation options are on, waiting-list places (name, email, times and a note), answers to a risk-assessment form with who approved a booking, the pickup and drop-off places chosen, items a borrower saved and a borrower's private calendar address; stock handed out to a person (the item, how many, the place and batch it came from, who handed it out, when it is due back, any terms accepted, and how many came back or were written off), and for suppliers the name, email, phone and address of a contact person; where you record fees for Equipment, each entry's amount, currency, tax, billing code, what it is for, status, waiver or void reason and the team member who recorded it, deposits, payments you took with the method and reference your team types, and numbered invoices; equipment asset fields, which can include a serial number, value, purchase and warranty dates and site-defined fields, an owner’s or manager’s purchase price, supplier, fund or cost centre, depreciation, insurance and disposal details, and licences kept for the equipment (never a licence key), a hazardous-substances register with optional safety data sheet files as entered by owners and managers, plus maintenance, work order (with the team member or outside technician, supplier, cost, fund or cost centre, parts and tools used and, for a request from a borrower, their name) and stock-take records; where the site turns them on, the place (rounded to about 100 metres unless the site chooses exact) where a team member who agreed counted an item in a stock-take or scanned its label from a workspace screen other than the Equipment desk, or handed out or took back items at the Equipment desk (the main Equipment screen, where items are checked out and back in; other Equipment pages are workspace screens), with the item and time, the team member's record of agreeing and which wording they agreed to (an agreement to the earlier wording, which named only equipment labels, does not cover the desk), and a borrower's answer, during a stock-take, that they have or do not have an item; equipment status changes and their times for utilization reports, team members’ warranty, insurance, licence and safety review reminder choices per site and delivery attempt records linked to the item, licence or substance, its date and team member, deleted with the site or, for item-linked records, with the item; for a found item sent between sites of a customer group, both sites, where it was kept and where it goes, an optional note, status, times and the team members who sent, received or took it back; and, for a group equipment transfer, the owning, source, destination, service and custody sites, source and destination locations and codes, status, times, operational notes and the team members who performed its steps; for vFound Visitors, who they came to see and when they arrived and left, and, where given, their email, company, reason for visiting, expected time, valid dates, recurrence and email language, their visitor type and answers to your questions, the invitation sent, approval state, host reply, roll-call status (safe, needs help or not yet accounted for) and a copy of your visitor terms, that they agreed and any signature; where you enable them, a private visitor photo and the staff member and time of a visual check of a physical photo ID, but no image or number from that ID; where you turn on Remember me, the details a visitor asks to be remembered on their own phone (their name, email address and company, encrypted, and a fingerprint and date of each version of your visitor terms they agreed to) and a hash of the random key their phone holds; for calendar intake, organizer and attendee names and addresses, meeting identifier, sequence and times, with no meeting description; for paired kiosks, the device name, random token, permitted actions and last-seen time; AI suggestions about items, claims, parcel labels and equipment you add; meeting invites your team pastes or forwards to vFound Visitors (a forwarded invite is kept up to 30 days); for email to inventory, each photo your team emails to the site’s private address, with the sender’s email address, the subject and the first 500 characters of the message (kept up to 30 days); the requests your team makes in Ask vFound and the actions it suggests; the questions your team asks the Ask vFound help panel and its answers (kept 30 days, then deleted); and the questions it could not answer, with names, email addresses, phone numbers and street addresses removed (kept 30 days); for each email vFound sends, whether it was delivered, bounced or marked as spam, the provider’s reason with any email or IP address removed, the recipient’s domain and a one-way hash of the address, but not the address itself (kept 90 days); and, when a person turns on browser alerts, the browser push address, public encryption key, authentication token, expiry and delivery result linked to their account, pass, ticket or signed service-email record; and for a connected people directory, its encrypted CSV link, source identifier, active status and sync results; for a connected hotel property system, its encrypted credential and settings, connection state, sync cursor, timestamps, counts and bounded error history; for a connected OfficeRnD, Microsoft Entra, LDAP or Active Directory, or Google Workspace directory, its encrypted application credential, bind account or service account key and source settings, connection state, sync cursor, timestamps, counts and bounded error history, and only the source ID, name, email and active status used in the people list; for a connected Microsoft Intune or Jamf Pro, its encrypted credential and settings and, on each linked equipment item, the device record number, name, serial number, maker and model (a device name can contain a person's name); for a connected learning platform (LTI 1.3), its issuer and identifiers, the tool's signing key (the private half encrypted), each course's identifier and title, and, only while a roster is read, the learners' names, emails and references, used to match the people list and not kept for anyone who does not match; for a connected Jira, Zendesk or ServiceNow, its encrypted credential and settings and each ticket's text (the item details (name, label code, asset tag, serial number, category and location), the team's note and the borrower's own description of a problem as written), link, status and errors, kept until 13 months after it closed or, while it has not closed, 13 months after it was sent (or raised, if it never was); for a student information system (OneRoster) import, the teachers and staff the file lists, and its students only when the site ticks that option, each as a people-list entry with source ID, name, email and active status, and, only if the site asks, each class name as a borrower type with the people enrolled in it (parents, guardians and relatives are never imported); for borrowers opening a site's Equipment catalogue through the site's own identity provider, the email that provider confirms and a record of each sign-in or refusal in the site's audit log; and for a hotel stay, its manual, CSV, API or property-system source, stable stay reference, optional stable guest reference, guest name, arrival, departure, source timezone, current room, state, source update time, sync time and the room recorded when a linked item or parcel entered vFound. The hotel stay context does not include room rate, payment or card data, loyalty status, passport or ID data, guest preferences or unrelated reservation notes. For a customer group, the data also includes its name, site and region mappings, members and roles, policy templates, named operating-policy versions and targets, site assignments, local exception reasons and expiry dates, acknowledgements, aggregate site and service-level counts, alert notification times and group audit history. Aggregate summaries and escalation emails do not contain operational record details. The separate open-work lists include item titles and claim status, parcel recipient names and units, checkroom ticket numbers and guest names, equipment and borrower names, and visitor and host names for authorised sites. They omit email and phone fields.
- Where you turn the options on or your staff use them, vFound Equipment also keeps: help desk tickets and notes, until 13 months after the ticket is resolved; document custody records and signature images, until 13 months after delivery or, if never delivered, after their last change; household members: a first name or nickname the site chose to record for a member of a borrower's household, with the site's optional item limit and the loans handed out for that member, deleted when the member or the borrower is removed and with the site; never included in webhook, API or integration payloads, which carry an opaque member number only; a library card number stored on a person for card sign-in (in beta, on vFound Enterprise), kept with the person; fixed RFID reader reads (the tag, the matched item, the reader and the time, never a person), kept 90 days; the carrier, tracking number, tracking link and posting day of equipment posted back; start and end days and a fee note on a borrower type, booking credits as a count, a member card's random value and a hash of its code, a membership type and valid-until date, and volunteer marks and the names on shift places, which are deleted 13 months after the shift ended, none of which carries a payment; devices read from a connected Kandji (name, serial number, model and platform); staff names and email addresses from a connected OneRoster service (students only if the site chooses) and, for the school office, pupils' names, classes and the system's own IDs, never parents or guardians; and the in-house hotel guest a team member picks at check-out, whose name and room are copied onto the loan. A Google Calendar you connect receives the item's name and the booking time for each approved booking, never the borrower, and a ticket receiver you connect receives the ticket text described above. The library system a site names for card sign-in is the site's own system and is not a vFound sub-processor. The card number is processed for the site; the PIN is relayed to that system and not kept. Where the Controller turns on Equipment access control (in beta), the Processor sends the borrower's name, email address and reference if there is one, the item's name and the door or area name to the Controller's own door or access system when an item is handed over, and a message to take that access away when the loan ends. When a person is removed, the Processor first asks that system to take their access away and, if that cannot be confirmed after five tries, removes the person anyway and records the access as not confirmed, so the Controller must remove it there. Records of access for ended loans are deleted 30 days after the access was taken away, and records that could not be confirmed 180 days after they were closed.
- Enterprise custom attributes contain the field definitions and values your staff enter. Workflow checklists keep step labels, answers, notes, staff identity and completion time; Equipment checklists (checking out and taking back) are on every plan, the others on vFound Enterprise. Values follow the product record retention period; orphaned completions are removed nightly. Claim guest erasure also removes its completed checklists. Site definitions go with site deletion; group definitions are removed 24 months after group closure. Enterprise expiry removes none of these records and stops every network checklist, for every product including Equipment, and the other products' site checklists; a site's own Equipment checklists keep working.
For vFound Queue: each ticket's number, line, service, counter and the times it was taken, called, served or ended, its history of calls, its priority and the team member who served it; and, as your line or your team records them, the person's name or initials, party size, email address, answers to your questions and a note your team adds. When a person joins from their own phone or a kiosk your line decides whether they give a name, only initials or neither, and whether it asks for a party size, an email address and answers; a team member at the desk, or a system you connect through vFound's API, can add a name, party size and note whatever the line asks. The data also includes the link to their ticket, a browser alert address and, if you set up your own SMS or WhatsApp provider on vFound Enterprise and they choose it, their number (stored encrypted) with their choice and the time they gave it; the email address, answers and link are stored encrypted. If you turn them on, booked times keep the name or initials, party size, time, email address, answers, a private link and a coded form of the email address (the email address, answers and link are stored encrypted); messages keep the short text exchanged (encrypted); a survey keeps a rating with the ticket, and, once the ticket's details are cleared, without anything that names the person, and an optional comment (encrypted); a returning-visitor record keeps a coded form of the email address made with a key that is different for each site, the number of days visited and the last two visits; and a team member's private calendar link of booked times is kept encrypted. If you turn the matching features on, Queue also keeps for the people in your lines: the email address and name a person leaves on a booking page's waiting list; the consent boxes they tick, with the words shown and the time; answers of the kinds email address, phone number, number and several choices; a note that they are on their way or running late; and the stored code of a view-only share link they make. The team can put coloured labels, an outcome and a quoted wait on a ticket; only the team sees them. It also keeps, for your team, a block list entry (a coded form of a phone number or email address, made with a key that is different for each site, and a short label), the names of team members people can book with, and a team member's first name on a waiting-room screen where you turn that on for a counter. A test key writes labelled test tickets with no email address. If you turn on showing team messages in a guest's language, the team's own words in a message are sent to Amazon Bedrock to be translated.
Categories of data subject: people who claim items from your site, report a lost item or set an alert, people who tell your site they found something, people your site receives parcels for, guests who use your checkroom, guests who reserve luggage space ahead, people who borrow your equipment, visitors to your site and the people they come to see, people who take a number or book a time in your lines, hotel guests whose minimal stay context your site links to an item or parcel, coworking members on a connected people list, contacts at your suppliers whose details your team records, and members of your team and the staff who sign in for work at your site. - Special category data: not requested and not required. You must not publish identity documents, payment card details or sensitive personal data found in or on an item.
A site can group visits under an event name and preview a CSV invitation list. If an owner or manager enables a backup host, that person receives the site and host name when an arrival remains unanswered, but no visitor details or private pass. Replies to that email go to the site.
At your instruction, the optional visitor-delegation feature records host/delegate relationships, creation and revocation timestamps and revocation attribution using the people already on your site’s list. Delegates can see only supported hosts’ approved, confirmed expected or signed-in visit names, host names, times and arrival replies and can send the existing arrival replies; they cannot approve entry. Reply attribution identifies the delegate in the visit history. Optional arrival escalation records the configured delay, backup-person reference and reception follow-up actor and time. Delegate and escalation email attempts use arrival, grant and recipient references and attempt statuses for duplicate prevention; the messages contain the minimal host/site details described in the Privacy Policy. Both site settings begin off.
At your instruction, when you turn on the optional workplace features of vFound Visitors we process the following, as the Privacy Policy describes. For staff sign-in: the name of each person on your staff list, the working day, whether they were in the office or remote, sign-in and sign-out times, the method and the device, team member or key that recorded it, and whether the sign-out was automatic. For catering requests: the visitor’s name and company, the host’s name, the visit time, the options you list that were chosen and the number of people, emailed to the one inbox you choose. For appointment pages: the name, email address and company a person gives when they book a time. For desk, room and parking booking: the person’s name and email address, the space, the times, the number of people, the booking’s status, how it was made, and whether the person checked in or it was released. For reception, signage and room displays: first names with a last initial, times and the messages you write, shown on screens you pair. The purposes are recording working time at your site, arranging catering, taking appointments, and booking and releasing desks, rooms and parking. Each feature is off until an owner or manager turns it on. You choose who is on the staff list, how long staff attendance is kept (30 to 1,095 days, 365 by default), the catering inbox and options, and what your screens say. You are responsible for the lawful basis and the notice to your staff for staff attendance, and for who can see a screen in your premises. We do not collect or use location.
Optional visitor preregistration, event signup and written induction acknowledgement process visitor names, email addresses, company names, answers to controller-configured visitor questions, requested visitor photos, event and visit associations, visitor-terms agreement text and time, preregistration completion time, and induction version, acknowledgement time and expiry. The purposes are advance preparation for a visit, managing event registration capacity, and recording acknowledgement of the controller's visitor instructions. The controller chooses whether to enable each feature and sets its questions, instructions, event parameters and acknowledgement validity. Acknowledgement evidence does not certify understanding or determine admission. Private pass and invite-only event URLs act as transferable bearer credentials. Where the Controller enables them, the Processor also processes up to five pre-arrival documents per visit (PDF, JPEG or PNG files with their original file names, stored encrypted), signatures given before arrival, and event waitlist positions; documents are available to the Controller’s owners, managers and staff, not view only members, each opening is logged, and they are deleted with the visit.
Optional Visitors invitation and host features, each off until the Controller turns it on, process: the Controller’s invitation wording, directions, parking and Wi-Fi text and reminder days; who approved an invitation or visit (a team member, or the host deciding from their private My vFound page on a walk-in the visitor started themselves); up to eight additional arrival recipients and notification rules by visitor type, weekday and time, whose email addresses the Controller chooses and which receive the visitor’s name, the host’s name, the sign-in time and, as the Controller chooses, the visit type, expected time and a note, never the visitor’s company, reason, answers or contact details; a notice to the host when the visitor signs out, optionally with a private link that opens the visitor photo for 2 days to anyone holding the email, ending sooner when the setting is turned off, the visit is deleted or the host’s My vFound link ends (the photo is never attached); the Controller’s own emails to the visitor after sign-in and sign-out, with a link the Controller chooses; messages written between the visitor, the host and the desk about one visit, stored encrypted, never copied into notice emails and closed to the visitor once the visit is cancelled or not approved; and, for an invitation made for several sites of an Enterprise network, a separate copy of the visitor’s details at each chosen site under that site’s settings.
Optional visitor agreement documents, inductions, contractor records and permits to work process, for the controller, the PDF it uploads and a picture of each page; the signer’s name, email address (if given), the time, the version signed, how it was signed and a signed-copy PDF that holds the pages and any drawn signature; induction name, version, score and time, and for seven days a one-way code of the person’s name and email with each try’s score, and counts of failed tries kept against one-way codes of the person’s email, or name and company, and of the browser session for a day, and of the kiosk and the network address for an hour; videos the controller uploads; contractor company contact names and email addresses, worker names and email addresses, uploaded documents, their review status, reviewer, dates and expiry dates, the portal link an upload came through, one-way codes of workers’ sign-in codes, and portal links kept as one-way codes; and permits, their approvers’ decisions and notes. The purposes are collecting the controller’s visitors’ agreement to its documents, recording induction results, checking contractor compliance and reminding contractors, and recording permit approvals. Files are kept in the controller’s private uploaded files on the hosting and backups listed in this agreement, and are never publicly listed. If the controller connects a webhook it receives the signer’s name and email address and a link to the signed copy that works for seven days. Where the controller keeps AI assistance on, the lines of a contractor PDF’s text that hold an expiry word, and the line after one that holds only a date (at most thirty lines in all), are processed by the AI sub-processor below to suggest an expiry date that a person confirms. A line that holds a word for a date of birth is not sent, but a date of birth printed without such a word can still be sent if it sits on a line with an expiry word; a sent line holds whatever else is printed on it, such as a name, a licence or policy number or an address. A picture or scan is never sent to an AI provider. Signatures, signed copies and induction records follow the visit’s retention and are deleted with it, after the controller’s visitor retention period. Induction tries are deleted after seven days. A contractor document that a newer approved one replaces, or that the controller turns down, is deleted after 30 days, and a portal link 30 days after it ends. A contractor’s documents and the company’s are deleted when the controller removes them or deletes its site account. Permits are deleted 400 days after they end, and backups follow the retention described above.
Optional vFound Visitors features for cards, fast-track codes, things handed over, location checks, ID dates and school imports are each off until the Controller turns them on, and process the following. For an RFID card: the card number, the visit, who gave it, when it was given and when and why it ended; the full number is kept only while the card is live, and afterwards only its last four characters. For a fast-track code: a one-way code of the token and an encrypted copy that only the visitor’s own pass page shows, its expiry date, how many times and when it was last used and who gave it, for up to 365 days after the visit. For a location check: only whether the visitor’s phone was near the site, not near it or not checked, and never the position itself. For a physical photo ID: only the expiry date a team member typed and whether it was already past, and never an image or number from the ID. For things handed over: what was handed over, an optional tag, who gave it and when it was given and returned. For a school import from OneRoster files: the pupil’s name, class and the school system’s own id, and nothing else from the files; a pupil the school system marks to be deleted is deleted, and one marked as not enabled is made inactive and kept until the Controller deletes them. The card, fast-track code, things handed over, ID date and location result are deleted with the visit, after the Controller’s visitor retention period, and also when the visit is erased or anonymised. Backups follow the retention described above.
When the Controller enables the school office in vFound Visitors, the Processor stores pupil names, year or class and school reference, collector names, relationships and phone numbers, the Controller’s own custody alert list, late arrival and early leave records with reasons and times, volunteer applications and hours, and staff sign-in times, only for that site and readable only by its owners, managers and staff. The Controller decides which pupils to record and is responsible for its own lawful basis and for informing families. The Processor does not check outside registries and does not send these records to an AI provider. Movements, volunteer hours, staff sign-in times and declined volunteer applications are deleted after the Controller’s retention period (7 to 365 days); pupil, collector and approved volunteer records are kept until the Controller removes them, and an owner can delete the whole school office at once.
When the Controller enables the building features in vFound Visitors, the Processor stores tenants, the people from the Controller’s people list assigned to each tenant, tenant admin names and email addresses, and a blocklist of names, email addresses and notes (encrypted when stored). Tenant admins reach only their own tenant; a tenant’s own blocklist entries and notes are shown only on that tenant’s page. Blocklist entries end on their set date and are deleted by the nightly clean-up; with the leavers option on, a person switched off or removed by the Controller’s directory sync is blocklisted for up to a year or until switched on again. When the Controller enables visiting limits, the Processor stores which people are residents of which ward, for the Controller’s owners, managers and staff only, and no clinical information.
When the Controller connects its own account at Cisco Meraki or Eventbrite (beta), the Processor stores the Controller’s keys encrypted and, at the Controller’s instruction, sends Meraki the visitor’s name and the email address given (or a made-up one) while the visitor is signed in to make a guest Wi-Fi login that ends at the end of that day, removes it when they leave and retries until Meraki confirms it, and reads Eventbrite attendee names, email addresses and companies for the Controller to check. Those providers are the Controller’s own processors, not the Processor’s sub-processors. A guest Wi-Fi login and password are stored encrypted and deleted when the login is taken away; the record of the credential is kept 30 days after. The Controller can instead connect its own Aruba ClearPass server for guest Wi-Fi (in beta): the Processor then sends it the visitor’s name, and their email address if they gave one, while the visitor is signed in, to make a guest login that ends at the end of that day, removes it when they leave and retries until the server confirms it; that login and password are stored, deleted and kept in the same way.
At the Controller's instruction, the Processor sends a visitor's name, and their email address where the door system takes one, to the Controller's own door system (Kisi, Brivo, Avigilon Alta or a signed webhook, each in beta) to make a pass while the visit is signed in and approved. If the door system does not answer, the Processor records the pass as unknown and removes it when the visit ends. Where the Controller's keys have been changed, the Processor cannot confirm removal, and the Controller removes the pass in the door system. If the Controller sends its visitor emails through its own mail server, those emails and the recipient address pass through that server. Staff, host, emergency, sign-in and account emails do not. The server's user name and password are stored encrypted and are never shown again.
Where the Controller turns on the presence feed (off by default), its own badge reader, time clock, Wi-Fi or identity system can send in and out times for people on its staff list, kept as ordinary attendance records under the Controller's attendance retention, and muster events that mark a person safe on a running roll call; the Processor reads no position, device list or sign-in log itself. Where the Controller turns on offline sign-in for a visitor kiosk, walk-in sign-ins taken without a connection are kept in that tablet's browser storage, encrypted with a key kept in the same storage, and deleted once sent or after 12 hours.
Where the Controller turns on Vaccination record, a visitor may choose to send one before a visit. It is health information and is optional; at the site only its owners, managers and staff can open it; the Processor does not read it, a photo goes only through the picture safety check on the Processor's own servers, and nothing is sent to an outside service; it is deleted on the day fixed when it was sent, 1 to 30 days after, as the Controller chose (7 by default).
Where the Controller connects its own Salesforce (in beta), the Processor sends it the name, email address, company, host and sign-in day of each visitor who signs in with an email address and, if the Controller also adds Checkroom guests, the name and phone number of a guest who agreed on their ticket page to the Controller keeping them in its own customer system. The Controller's own Salesforce, Google Calendar, Kandji, OneRoster service, ticket receiver, door system, guest Wi-Fi system, access system, library system and mail server are the Controller's own providers, not the Processor's sub-processors; the Processor reaches them only with the details the Controller saved, at the Controller's instruction.
When the Controller enables Checkroom phone notices for an Enterprise site, the Processor records a guest's explicit, ticket-specific SMS and/or WhatsApp choice and processes the encrypted alert number, its keyed fingerprint, channel choices, language, consent wording version and consent and withdrawal times. Notices use the Controller's existing messaging connection and customer-owned provider account. The recipient number, site name, short ticket status and private ticket link are sent to that provider; guest names, email addresses, rooms, item descriptions and photos are excluded from these notice payloads. The Controller is responsible for its provider arrangement, fees, approved WhatsApp templates, recipient coverage and provider-side retention. Existing signed preference withdrawal and authenticated inbound STOP handling apply; already-started or accepted messages cannot be recalled. Stopping both channels clears the live alert number and keyed fingerprint. Consent records follow the associated Checkroom ticket's retention, are erased at once if the ticket's guest email address is corrected, and orphan consent records are removed during nightly cleanup. Existing site erasure and backup schedules continue to apply. This feature adds no vFound-owned messaging account.
When the Controller turns on the Checkroom choices about money, shifts, terms, things left behind and offers, the Processor records, for each payment the Controller's team records, its type, amount, method, kind of item, the team member and time, and any void with its reason; for each shift, the team member, a device name they type, a keyed fingerprint of a random name that device's browser keeps, the cash counted and the totals; for each ticket, the exact words of the terms the guest accepted and the liability limit and prices shown beside them, with a fingerprint of all of these, the time and place of acceptance and any value declared, the reminders planned and whether each was sent, the disposal date fixed when the things were left, a note of any disposal the Controller records, and a short note if the Controller marks the ticket disputed. A reminder is emailed to the guest's email address. If the Controller turns on offers, the Processor records the guest's choice to receive them, separate from alert choices (the encrypted number, its keyed fingerprint, the time and the wording version), and queues one text through the Controller's own provider after the things are handed back in full, with the site name, the Controller's offer line, any coupon code, a prompt for the survey if on and the private ticket link. An offer is sent only to a guest who made that choice, and only where the Controller has saved the secret for its provider's STOP replies; a STOP reply or the guest's settings link withdraws it, and the choice is checked again just before sending. The Controller is responsible for each guest's consent under the laws that apply, for its provider arrangement and for the content of its texts. A survey answer is a rating and an optional comment shown to the Controller's team. The Controller's team can also queue one short text, such as the closing time, to guests whose things are still there and who chose text updates (never to a guest who only chose offers); the Processor keeps the words the team typed for 30 days, beside the delivery records. The Controller can also schedule an offers text to guests who chose offers and whose things were collected, aimed only by the number of tickets on which a phone number was given and the date of the latest, and, if it turns them on, have the Processor queue a reminder once to a guest who chose text updates after their things have been there the hours the Controller sets, and a follow-up once to a guest who chose offers the days it sets after collection. Each is sent once for each phone number or ticket, only through the Controller's own provider, and the choice is checked again just before sending; the Processor keeps the words and the rule of a campaign for 30 days. If the Controller turns it on, a guest who chose text updates can ask for their things by replying READY on the Controller's own number: the Processor reads the reply only to find that guest's ticket from the number they gave, does not keep it and sends nothing back. The Controller can print a receipt for the payments recorded on a ticket or on several tickets of one guest, with no guest details; its QR address holds a keyed fingerprint of the payments and opens a page that shows the site name, a receipt number and the total only while the receipt matches the records the Processor holds. The Processor deletes these records with the ticket they belong to; a shift and its cash drops are deleted 12 months after the shift was opened. The list of tickets left at closing that the Controller can print for a lost-property office shows ticket numbers, items, places and dates and no guest names or contact details. The Processor never disposes of anything.
When the Controller offers Visitors host alerts by phone for an Enterprise site, a host on the Controller’s people list may choose SMS and/or WhatsApp on their private My vFound page with their own number. The Processor sends one confirmation code to that number through the Controller’s provider and sends no alert until the host enters it; it keeps only a keyed hash of the code, valid for 15 minutes. It processes the encrypted number, its keyed fingerprint, channel choices, language, consent wording version and consent, confirmation and withdrawal times. The number, site name, a line that a visitor arrived or, where the Controller enables sign-out notices, left, and a link that opens only the host’s alert settings are sent to that provider; visitor names and details are excluded, and the link never opens My vFound. The host’s stop, an inbound STOP where the Controller’s provider passes replies on, a reset of the host’s My vFound link, a change of their email address and their removal or deactivation each end the alerts and every link sent by phone and clear the stored number; a number not confirmed within one day is cleared. Delivery-attempt records are deleted after 30 days. The Controller is responsible for its provider arrangement, fees, approved WhatsApp templates and provider-side retention.
At your instruction, the optional Visitors safety features process the following. Blocklist: the names, email addresses and companies you enter, your reasons (encrypted), their last days and who shares them with your network; matches between a visitor and an entry or, where you turn it on, a name on the US Consolidated Screening List, with the team member who decided. The Processor downloads that public list once a day and compares it with visitor names and companies on its own server; no visitor data is sent to the list’s publisher. A match is a possible match, not proof, and you decide what it means. Answers to your questions that ask a team member to decide or stop self sign-in are processed the same way. Visitor directory: notes about a person (encrypted), merges of records, the list of people signed in at the same time as one person, and anonymising a person or a single visit, which removes the visitor’s name, email address, company, mobile number, answers, reason for visiting, notes, photos, signatures, feedback, saved Remember me details, calendar copy and pass links, the logged webhook deliveries about those visits, and the other records the site holds about them (uploaded documents, signed agreement copies with the signer’s name and email, messages between the visitor, their host and the desk, guest Wi-Fi logins, catering requests, appointments, invitation delivery records, induction records, a courier’s name and company, a contractor worker’s record and documents, a screening match made by an answer to a question, forwarded invitation emails that contain the visitor’s email address, and what they wrote in an emergency roll call). A screening match against a list entry stays as the Controller’s security record, with the matched entry, the name as typed and the time. Emergency roll calls: the people on them (visitors, contractors, people on your people list and people your team adds), whether each is safe, needs help or is not accounted for, any short lines they write back (encrypted, up to 30 for one roll call, with your team’s replies), the muster points and zones, the timeline and the messages you send, among them a hazard alert your team writes and sends to a group it chooses (the Processor reads no weather, news or threat feed, so nothing is sent unless your team sends it). A visitor’s optional mobile number for emergencies (encrypted) is used only to send an emergency message. Emails and browser alerts go through the providers below; SMS and WhatsApp messages go through your own provider account, which receives the number, your site name, the words your team wrote and a private link, and which is yours to arrange, pay and keep. Your team’s help alerts and drill reminders go to your chosen team members only. Messages already accepted by a provider cannot be recalled, and the Processor does not replace your emergency procedures or the emergency services.
Where enabled by the controller, Lost & Found processing includes email control verification before a claim is created and optional journey context supplied with a lost-item report: flight or route, service date/time, seat/gate, event and station/seating area. Journey context and its earlier report versions are processed under the agreement's existing access, retention, erasure, backup and sub-processor terms. We keep site-scoped hashes of the address, code and challenge token, with an expiry time, and explicitly clean up expired challenges and remove them when the site's data is deleted. Verification confirms control of an email address, not identity or ownership; journey context does not authorise cross-site disclosure.
Your authorised team may record a lost-item report for a person by telephone or in person. A name and contact details may be omitted. Staff record how they helped and that they explained the use of the details. This is a privacy explanation, not marketing consent or proof of ownership. Private location or journey details may include a room, route, vehicle, seat, gate, lift, run, lodge or locker reference where you chose those fields, and your team can record the same kind of private details on a found item. Passwords, payment information and identity documents must not be provided or recorded.
Messages about a lost report and private found items: your team can write to the guest about a lost-item report. vFound keeps your team’s messages and the guest’s answers with the report, emails each message from your team to the address on the report with a link to the guest’s private report page, and shows the conversation there. A reply to that email goes to your guest reply address. The messages are plain text, are not sent to vFound AI and are deleted with the report’s guest details, under your record retention and when your site is deleted. If you choose to keep your found items private, none of them, their photographs or possible matches are shown on your guest page, item pages or a group’s organisation page, and no automatic email tells a guest about a match; an item your team chooses to share with one guest, for example by starting a claim from their report, is shown to that guest only.
Group intake: An explicitly published organisation page routes one report to the chosen receiving site, or its stated intake site when the location is unknown. Publication does not enable matching across sites. A group’s owner can also choose to list, on that page, the found items its selected sites already show on their own pages, with each site’s public label and a link to claim the item on that site’s page. This is off unless the group turns it on. Group review and exports follow current membership, region, product and explicit review settings. A report sent from an organisation page is handled like one sent from your lost and found page. Matching across a group’s sites is off unless the group’s owner switches it on; while it is on, open lost reports are compared with found items at the group’s other sites and shown, without the reporter’s contact details, address or photos, to people in the group who have a role at both sites. While matching across sites is on, a guest with an open report may be told about a found item at another site of the group, never at a site that keeps its found items private; the report’s contact details are not passed between sites. Each guest page listed on a published organisation page shows the group’s name and links to its other locations, and may search the found items those sites already show.
Customer-configured CRM destinations: Selected webhook events may be sent to systems you choose, such as your CRM. Extra report contacts are sent only after a separate explicit choice, and the source record and transport are checked again before each send.
Where you enable the private Equipment borrower catalogue, your instructions also include showing your equipment names, categories and photographs to holders of current site-scoped My vFound links and recording grouped Equipment requests against the borrower's existing name, email address, reference and language. The catalogue adds no new borrower identity field, attachment upload or application-level browsing-history record. Where the controller enables equipment specifications, staff-written borrower-visible technical descriptions are published through the private catalogue; they must not contain personal information or internal asset details. Where the controller separately enables reservation history and change requests, we process the existing borrower/reservation association, proposed booking dates, equipment quantities, optional text notes of up to 1,000 characters, request and decision timestamps, the deciding staff identifier and recorded reservation status changes. The purposes are to let the borrower inspect their booking and ask for changes, let authorised site staff review requests, recheck allocation on acceptance, and send the borrower and site staff a request or decision notice. Notes are encrypted in storage and are not included in these notices. The existing service-email provider receives the recipient address, site name, request/decision status and a private My vFound link or staff workspace link as applicable. No attachments, new identity document collection, additional messaging provider or AI processing of these notes is introduced. Existing support, hosting, sub-processor and international-transfer arrangements apply. Grouped requests follow the retention and deletion controls for Equipment reservations in section 9.
Parcel recipient-correction reporting is on unless the Controller turns it off; an existing saved off choice is preserved. When a recipient confirms a report, we process the parcel recipient-correction report, its report and resolution times and activity records. Where the Controller enables parcel notice hours, we process scheduled parcel notice times and delivery-attempt states. Delivery guards also process notice delivery-attempt states when needed to prevent stale or duplicate notices. These records are linked to the parcel, site and applicable staff actor, with hashed forms of recipient addresses and pickup codes for stale-notice and duplicate checks. The purpose is to correct parcel assignments and deliver collection notices during configured desk hours.
Where the Controller enables Checkroom event guest lists, the Processor imports and keeps a guest list for an event the Controller chooses, from a CSV the Controller supplies or a one-time pull using the Controller's own Eventbrite private token, which is used for that request only and is not stored. For each guest it keeps the name and email address encrypted, an order reference, a ticket type and, for a ticket barcode, only a keyed hash. Access follows site membership permissions. The list is deleted 14 days after the event ends, when the Controller clears it and with the site, and backup schedules continue to apply. The Processor writes nothing back to the ticketing system. A guest list also keeps any seat or table label from the file or pull.
Where the Controller turns on the Checkroom choices for hotels and events, the Processor keeps, for the Controller's team only: for a vehicle, the number plate, where the key is kept, photos of the vehicle, its key or its plate and damage marks with a kind, a short note, who made them and when (the guest sees the marks and notes on their own ticket page, never the plate or key; the team also sees the marks on earlier tickets of the same site with the same plate while those tickets are kept); the number of a tamper seal on a bag, any mismatch or a reason it was broken or missing, and the seal number a guest types where the Controller records seals for guests' own bags; a carrier and tracking number and a long-term storage date; for a bell desk delivery, the room, the name of the person who received it, who took it and when and whether the runner reported reading the room from a label; and, where the Controller also turns on guest history, the guest's earlier tickets at the same site with the team's notes on them. None of it is sent to an AI provider. Where the Controller turns on its under-18 form, the Processor keeps a young person's name and date of birth and a guardian's name and contact, encrypted, with the form number, and sends no email about them. Where the Controller turns on event RSVPs, the Processor keeps the name, email address, answer and party size that a person sends through an event's private link, encrypted, and sends no email about them. Where the Controller turns on its member list, the Processor keeps its members' names, email addresses, membership type and optional expiry date, encrypted. The Processor sells no membership and takes no payment. Access follows site membership permissions; a manager can delete a form, an answer or a member, and erasing a member also deletes the RSVP answers given with the same email; a ticket already made keeps the name and email that were filled in until the ticket is deleted.
Where the Controller turns on Remembered guests, the Processor keeps, for the Controller, a guest's phone number (encrypted), a visit count and any points total after the guest proves the number with a text code sent through the Controller's own text provider, and deletes them when the guest asks, at the end of the retention the Controller chose (3 to 24 months after the last visit), 30 days after the Controller turns the choice off or its plan ends, or with the site. Where the Controller asks its optional question, the Processor keeps each answer against its ticket for 30 days and then only a count for each day, kept 13 months.
Optional Checkroom ticket conversations process guest and desk message text, sender side, sending timestamps, and links to the existing site and ticket record to exchange questions and replies about that ticket. No staff author identifier is stored with a message. Access follows site membership permissions and possession of the private ticket link, subject to existing support and sub-processor arrangements. Message bodies are encrypted in the application database, excluded from displayed conversations after 30 days and deleted by routine pruning; deleting the ticket or site also deletes its messages. Backup copies follow the existing backup deletion schedule. Requested reply notifications use the existing email provider and contain no conversation text. Notification records include the message reference and a hash of the recipient email address; these follow the existing notification-record lifecycle rather than the message-body retention period. No additional provider is introduced.
Unless the Controller turns accepted-terms copies off, the accepted-terms copy displays the agreement text and acceptance time already held with a visit, with a SHA-256 digest, through the current eligible private visitor pass. An existing saved off choice is preserved. Optional visit feedback records one 1–5 rating, an optional comment of up to 1000 characters, its submission time, the visit's feedback opt-out, active email-choice and invitation-attempt times, and the active choice's email/pass fingerprint. The purposes are allowing visitors to retain their accepted terms and optionally report their experience to the site after sign-out, including between recurring sessions. Feedback does not determine admission or approval. Authorised site members with visit-read access may review it, subject to the existing platform support and sub-processor arrangements. Private pass links are transferable bearer credentials. Invitation email uses the existing visit email address and email provider only after the visitor requests it and the Controller enables the relevant settings; it includes the site name and private feedback/preferences link, not the response. The active choice is bound to that address and pass token and is cleared if either changes. Accepted-terms copies are on unless turned off, with existing saved off choices preserved. Visit feedback and feedback invitation emails begin off.
On your instructions, vFound processes optional finder name, email, phone, affiliation and unclaimed-notice preference, receiving staff identity and time, and staff-started owner-contact claims. Authorised site members can read these records; platform administrators may access them to support your site. Finder details are not published. Staff initiate finder receipt and unclaimed-item emails; owner-contact invitations use the existing private claim link. Owners and managers can erase finder contact details and the notice preference without retaining their values in item history. Finder details otherwise remain until their item or site data is deleted, with existing protected-backup retention. Staff-started claims use the existing claimant retention and erasure controls. Optional handover identification type and a note of up to 120 characters are recorded without an identification-document upload field; staff are instructed not to type identification numbers. The note is erased with the claimant’s personal details and is omitted from release receipts. When an item moves between sites of one authorised customer group, its finder details move with it and are then processed for the receiving site under the same terms, including erasure by its owners and managers and its retention. Erasure of finder or claimant personal details also invalidates the site’s stored retry responses, including ID-check notes. Staff-contact and finder emails share limits of 50 per site and 3 per recipient per site-day, including confirmed resends. To keep deletion from resetting those limits, coded recipient, date and count records remain until site data is deleted; the counts contain no email address. Unclaimed-item notices are rechecked before sending and stale notices are dropped. Queued staff-contact and finder emails are dropped if their reserved site-day has ended.
3. Our obligations
We will:
- process personal data only on your documented instructions, your use of the product, and this agreement, are those instructions, unless the law requires otherwise, in which case we will tell you first unless that law prohibits it;
- ensure people authorised to process the data are bound by confidentiality;
- implement the security measures described in section 6;
- not sell the data, use it for our own marketing, or use it to train AI models;
- tell you if in our opinion an instruction infringes data protection law.
4. Sub-processors
You give general authorisation for the sub-processors below. We remain liable for their performance of these obligations.
- OVHcloud: application, database and file hosting in Singapore, including our own mail server, which receives the photos your team emails to vFound.
- Resend (Plus Five Five, Inc.): sends vFound’s service email from 7 October 2026. It receives each email’s recipient address, subject and content, and tells us whether the email was delivered, bounced or marked as spam. It processes data in the United States, where it sends through Amazon Web Services, under its data processing addendum , which includes the EU Standard Contractual Clauses.
- Cloudflare: bot protection on public forms.
- Google Analytics: only where you enter your own measurement id for the Queue join page and ticket page. A guest's own browser contacts Google, and only after the guest allows it; vFound's servers send Google nothing, and the address of the page carries no join key and no ticket link.
- ipapi.co: IP-to-approximate-city lookup used to help you assess a claim or a lost-item report.
- Amazon Web Services (Amazon Web Services Canada, Inc.): Amazon Bedrock, which runs Claude, an AI model made by Anthropic, for sites that keep AI assistance switched on: suggesting item details and search words from item photos; reading a parcel's label photo to suggest who it is for, the carrier and the tracking number; ranking possible matches for a guest's description, search photo (used once, not kept by vFound) or the photo a guest adds to a lost report (kept privately with the report and deleted with it); checking a claim against the item record (including its private description and internal notes) and proof photos as a suggestion for staff, who make every decision; translating messages between guests and staff (in Queue, only the team's own words in a message to a person in line, when you turn that on) and drafting staff replies; drafting, only when an owner asks, a translation of the agreement text, questions, answer choices and kiosk screen wording the site wrote for its visitors (only that text is sent, never a visitor's answers or details); structuring a guest's lost item chat, which never asks for contact details; suggesting a name for equipment from its photo; comparing the photo taken when equipment went out with the photo taken when it came back, reading a serial number from a photo of its label, drafting a check list from an item's name and kind, and reading a photo of a supplier's invoice into a draft purchase order, each only when staff ask (a person who is visible in a photo is to be ignored and the answer is thrown away; vFound does not detect people itself); turning a team member's typed request in Ask vFound into a suggested action (phone numbers removed first; the records found are never sent); answering a team member's question in the Ask vFound help panel from vFound's own guides to the products the site has and the site's settings, plan, open products and the person's role, with phone numbers and email addresses removed first (guest, claim, lost report and item records, source code and secrets are never sent); and, every night, grouping the questions it could not answer, with names and contact details removed, to improve vFound's guide; telling whether a workspace camera photo shows a found item or a parcel label (codes are read on the device); reading meeting invites you paste or forward into suggested visits (links, passcodes, phone numbers and place lines removed first); comparing the description your team types of a checkroom item (email addresses, links and phone numbers removed) with that night's item photos and item types (never ticket notes, or the name, email address or room on a ticket); and cutting a photo that shows several items into one photo per item; comparing a newly logged item's photo and description with up to three earlier items to flag a possible duplicate; wording the daily summary on the workspace home page and the checkroom's end of night summary from counts only. When a site uses Match columns with AI to import a spreadsheet, we send the AI the spreadsheet's column headings only when they are common column words such as Name, Email or Room; any other heading, and every example cell, is sent only as its shape (capital letters, small letters and digits marked as such), never what it says. A spreadsheet without a first row of column names is not sent. Nothing is imported until the site's team confirms it. When a site's owner uses Describe your site, the words they type are sent to the AI with the names of what the site has already set up, and nothing is created until they choose it. The weekly read is written from the counts, rates, times, item categories and places that the site's reports show for each product the site has, never a person's name or contact details. That weekly read is shown on the dashboard and emailed every Monday to your owners and managers unless you switch the email off. When a team member asks for a drafted message, the AI writes it without the recipient's name, contact details or amounts, which we fill in from the site's records; nothing is sent until a person at the site reads, changes and sends it. The claim check is also given what the claimant wrote on the claim: their description, where and when they lost it, their answers to verification questions (except those described below) and the last 10 messages in the claim conversation, which are also what a drafted reply is written from. Nothing vFound AI suggests is applied to a record until a person at the site confirms it. When AI assistance is on, it helps choose which found items a guest is told may match their report; a person at the site decides every claim. Photos of items already flagged as showing personal details are not sent again, and an answer to a verification question that asks for a passcode, password, PIN, phone number, address, date of birth or full name is not sent. Proof photos a claimant uploads are sent as supplied when AI is on for your site. Amazon Web Services processes each request in Sydney and Melbourne, Australia, and returns the answer. Anthropic never receives it, and Amazon keeps no copy, except that an image Amazon's automatic check flags as possible child abuse material may be kept so it can be reviewed.
- The house rules a site saves for its AI helpers are sent to the AI provider with each request a team member types into Ask vFound and each message vFound AI drafts for that site; they are not sent with questions to the Ask vFound help panel.
- Google (Google Workspace): our support mailbox, where messages about your site’s data may arrive.
When you pay by card, Stripe validates the card and handles the payment for a vFound subscription; an invoiced account has no card payment. If you record a Checkroom fee, deposit, tip or late fee collected in cash or through your own external POS or card terminal, that provider is yours to choose; vFound receives no such Checkroom payment or card details. The same applies to Equipment: fees, deposits and payments you record are only your records, you collect any money yourself, and vFound receives no such payment or card details.
We aim to give 30 days’ notice before adding or replacing a sub-processor. When a provider has to be replaced at once to keep the service working, for example when email stops arriving, we make the change first and tell you at the time, on this page and in the owner email. If you reasonably object on data-protection grounds within 30 days of the notice, we will work with you in good faith on an alternative; if none is workable, you may terminate the affected subscription and receive a pro-rata refund of fees paid for the unused period.
5. International transfers
We host the data in Singapore, keep an encrypted copy of our backups in Canada, our AI provider processes it in Australia, and our email delivery and support email providers may process it in the United States. Where personal data is transferred out of the EEA or the UK, we rely on an adequacy decision where one applies (Canada holds one from the European Commission) and otherwise on the EU Standard Contractual Clauses, with the UK International Data Transfer Addendum where relevant, together with appropriate supplementary safeguards. Those clauses are incorporated here by reference, with the details in section 2 filling their annexes.
6. Security measures
Taking account of the state of the art, cost and the risks involved, we maintain: encryption of data in transit (HTTPS with HSTS); passwords stored only as salted hashes, with rate-limited sign-in; Checkroom and Queue counter sign-in (when a site turns it on) with a staff number and a PIN or QR badge kept only as one-way hashes, a lock after five wrong PINs, counter devices that an owner or manager registers and can remove, and counter session records (person, device, product, method, start and end) deleted 90 days after the session ends; one-time sign-in links by email that work once, for 15 minutes, checked against a one-way hash; browser push addresses and keys encrypted in the database; directory links encrypted in the database, public HTTPS checks on every redirect and a 10 MB download limit; pending calendar invitation details encrypted in the database; paired kiosk tokens stored only as a hash on the server, revocable by an owner or manager, and never used as a staff identity; kiosks that never list the people at a site and reset entered details after 60 seconds; role-based access control, with every request checked against the person’s site or group membership, regional group roles restricted to matching site regions, group summaries containing no operational record details and open-work lists restricted to authorised sites without email or phone fields, policy effect previews tied to the actor, version, selected sites, their current settings and active exceptions before explicit assignment, every record query limited to an authorised site, and automated tests of cross-site and cross-region denial; signed, expiring links for claimant access, lost-item reports and My vFound pages, and an owner or manager can also reset a My vFound link; people-list email addresses shown in full only to owners and managers; a content security policy and bot protection on public forms; rate limiting; an audit log of security-relevant actions, kept 24 months; daily backups kept 30 days on our server with access limited to administrators, an encrypted copy kept off the server, and rehearsed restores; and least-privilege access for our own staff. Encrypted copies of the daily backups are also kept in OVHcloud’s Beauharnois region in Canada, encrypted before they leave the server and kept 30 days, while the application, database and files stay hosted by OVHcloud in Singapore. We review these measures as the service changes.
Offline mode starts off for every site and an owner or manager turns it on. While it is on, a team member’s equipment, visitor, Checkroom desk and Queue desk actions recorded without a connection (including the names of people added to a Queue line) are kept in that browser’s own storage, encrypted with a key the browser makes and cannot export, for that person and that site only; the person and the site are stored only as codes made with another key the browser cannot export, so only each action’s id, time and state are readable. They are deleted when sent, when the person signs out (after they are told about any that are waiting and choose to), when a different person signs in on that browser and, if never sent, once they are 72 hours old, the next time vFound is opened in that browser; the workspace's service worker stores no page or server answer (a paired visitor kiosk with offline sign-in has its own, which keeps only the kiosk's start page and files). Each action carries a device-made operation id, so it is saved at most once, even when an error follows the save. It is dated at the moment the person acted only when that moment is after a time vFound signed for that person and site, after the site turned offline mode on, and no more than 12 hours before it arrived, and otherwise when it arrived; an action the device says was recorded more than 12 hours before it was sent is not saved and waits on that person’s Offline desk. Its history and the site’s audit log record that it was recorded offline, with both times. We keep for 30 days only the kind of action, the record it was about, when it was recorded and how it ended, with the reason if it could not be saved; these rows go with site deletion. An action that conflicts with a change made meanwhile is never applied over it and waits on that person’s Offline desk.
Optional enterprise identity adds encrypted provider client secrets, DNS domain-ownership proofs and provider subject/email links to staff logins. The identity provider is chosen and controlled by you under your agreement with it, rather than a vFound-supplied provider. We validate signatures, issuer, audience, expiry, browser state, nonce where applicable and replay. Provisioning starts off and creates staff only within configured sites. Authenticator secrets are encrypted, recovery codes fingerprinted and single use, and challenges deleted after 24 hours past expiry. Site settings and provider links go with site deletion. Group settings follow its 24-month closure retention, with provider access disabled and its client secret removed on closure. Settings and sign-in changes are audited for 24 months.
7. Helping you meet your duties
Taking into account the nature of the processing, we will give you reasonable assistance with requests from data subjects (access, correction, deletion, portability, objection), with data protection impact assessments, and with consultations with a supervisory authority. In the product your owners and managers can read claim records, correct a guest’s name, email and phone, export every claim with its messages as a spreadsheet file, and delete a guest’s personal details from a finished claim, which keeps only an anonymous record of the item’s outcome, delete a guest’s personal details from a lost report that never became a claim, which leaves an anonymous record of the report (its category and when it was reported), and export the people list. Your owners and managers can also export your site’s audit record for the period it is kept, up to 20,000 events in one file. In a customer group, a group owner, manager or regional manager can find the lost reports, claims and finder details that hold one person’s email address or phone number (with or without its country code) at the sites where they are an owner or manager and Lost & Found is open (a regional role, only its region), and open each record in its site to delete the details there in the same way. Each search is recorded in the group’s activity without the address or number. If a data subject contacts us about your site’s data, we will refer them to you rather than respond on your behalf.
8. Personal data breaches
We will notify you without undue delay after becoming aware of a personal data breach affecting data we process for you, with the information we hold about what happened, the categories and approximate numbers affected, the likely consequences and the steps taken, supplementing it as we learn more. Notifying regulators and affected individuals where you are the controller remains your decision and duty.
9. Return and deletion
You can export your items, claims, parcels, visits, equipment checkouts, equipment fees, checkroom tickets, queue tickets, hotel stays and people list at any time while your subscription is active. Some records have no export: equipment booking credits, household members, help desk tickets, document custody records, volunteer marks and shift places, door or area access records, return shipping details, borrower type membership dates and notes, and remembered Checkroom guests (one guest’s data can be downloaded on its own). For any of these, ask us before the account is deleted and we will provide a copy. If your account is closed, your owners and managers can still sign in for 90 days to export your items, claims, parcels, visits, equipment checkouts, equipment fees, checkroom tickets, queue tickets (with their booked times, messages, survey answers and returning visitor records), hotel stays and people list (lost-item reports and alerts, equipment transfers and checkroom stations have no download once an account is closed), or you can ask us to reopen it; after that we permanently delete the personal data we process for you, except where the law requires us to keep it, except the reserved site code and the sign-in of an owner who still has another site (which goes when that site is deleted), and except copies in backups, which are deleted within 30 days as those backups age out (archives from our September 2026 server move are deleted once that move is confirmed complete). Data in backups remains protected by this agreement until it is deleted. Parcel records, their label photos, pickup photos and signatures are deleted 12 months after a parcel is collected or returned; finished outgoing parcels follow the same period. Expired delegate codes and served desk-arrival rows are deleted after 30 days. Checkroom tickets, their piece and hand-back records, photos and signatures are deleted 90 days after all the things are handed back, or 12 months after they were left at closing; the payments recorded for a ticket, the terms accepted, reminders, a disposal note and a survey answer go with it. Team shifts and their cash drops are deleted 12 months after they were opened. Unclaimed self check-ins are deleted after two days. Checkroom movement records, tasks, pickup times, the keyed hash of the email given at check-in and pickup approval requests are deleted with their ticket; team members’ queue status remains until it changes, the To fetch list is turned off or the site account is deleted. A vehicle's plate, key note, photos and damage marks, a shipping note, a bell desk task and a ticket's seal are deleted with their ticket; a finished or cancelled bell desk task, and a seal with no ticket, are also deleted 90 days after they ended. Event RSVP answers are deleted 14 days after the event ends. A member of the member list is deleted 13 months after they were last added, changed or checked in at the desk, or when the Controller erases them. Under-18 forms a site’s guests send, if the site turns them on, are encrypted and deleted 30 days after they are sent. Checkroom events are deleted 12 months after they end once no ticket refers to them; station records remain until the site deletes them or its account. Luggage reservations are deleted 30 days after their reserved time window ends; time windows nobody reserved are deleted 30 days after they end. An event ticket or wristband code linked to a checkroom ticket is kept only as a keyed hash, cleared when the link ends and deleted with the ticket. Queue ticket details (name or initials, email address, answers, note, phone consent, and the messages and survey comment on the ticket) are deleted the number of days after the ticket ends that you choose, from 1 to 365 (30 unless you change it), and a copy of the ticket or booking sent to a webhook you connect is removed from the delivery log at the same time (the log keeps nothing longer than 30 days); a browser alert is deleted when the ticket ends, or for a no-show when the site's day ends; ticket numbers, lines, services, counters, times, party size, priority, the team member who served, the ticket history and survey ratings are deleted 13 months after it ends. A booked time's details (including the coded form of the email address) are cleared the same number of days after the booked time and its record is deleted 13 months after it; a private calendar link of booked times that no calendar has read for 180 days is deleted; a returning-visitor record is deleted the same number of days after the last visit, and at once if you turn the feature off; records of cleared wait alerts are deleted 13 months after they clear. A ticket's ticked consent boxes and the stored code of its share link are cleared with its other details. A block list entry (its coded contact and its label) is deleted when its days end. A reminder record is deleted with the booked time it belongs to, a waiting-list entry (email address, name and link) two days after the day it was for, and a block of time 30 days after it ends. An invitation link is deleted 30 days after it is used, cancelled or past its end date. A test key's test tickets are deleted after seven days and with the key. Each nightly deletion is checked after it runs. Equipment records, their return photos and signatures are deleted 13 months after the item comes back or is marked lost. Collected or cancelled equipment reservations and completed stock-takes, with borrowers' answers given for them, are deleted after 13 months. Saved scan positions are deleted after 90 days, and a team member's record of agreeing to them 13 months after they withdraw it or leave the site. A person's Equipment fees entries in one currency are deleted together 13 months after the last change to any of them, once none is still owed, unused or held; an invoice is deleted once it is 13 months old and none of that person's entries in its currency remain. Completed equipment-transfer records, including site, custody, location, status and note history, are deleted after 24 months. A stock hand-out is deleted 13 months after the last of it is back or written off; one still out stays. The stock history and finished or cancelled purchase orders are deleted after 24 months. Equipment asset, licence and maintenance records, stock items and suppliers with their contact details remain until the site changes them or its account is deleted. A hotel stay is deleted 13 months after its last known date (departure, then arrival, then last update) when no item or parcel still links to it, whether or not the source ever marked it departed or cancelled; linked stay context remains until those parent records no longer require it. A site chooses a visitor retention period from 7 to 365 days, with 365 days as the default, and may set a different period for a visitor type; a type without its own period follows the site’s. After that period, a finished visit, its optional visitor photo, staff visual-check record, sessions, roll-call entries, courier link and any signature are deleted. Its pre-arrival documents, its event waitlist position and the messages written about it are deleted with it. Messages between a visitor, their host and the desk are deleted 30 days after they are written, or with the visit if that is sooner. Remember me details are deleted after the site’s visitor retention period, or the shortest period one of its visitor types sets, up to 365 days from the visitor’s last sign-in with Remember me ticked, and sooner when the visitor or your team deletes them or you turn Remember me off. A blocklist entry is deleted the night after its last day, and a visit’s matches and mobile number go with the visit. A note about a person is deleted when they have no visit left. An ended emergency roll call, with its people, timeline, messages and sweeps, is deleted 12 months after it ended. Staff attendance records are deleted after the retention period you set, 30 to 1,095 days with 365 as the default, counted from their working day, and sooner when your owner or manager deletes them, the person is removed from your people list or the account is deleted. A catering request and the booked time of an appointment are deleted with their visit. A desk, room or parking booking is deleted 13 months after it ends or is cancelled. Calendar invitation details with no visit are deleted after 30 days. Found-item messages are deleted 30 days after they arrive if your team does not deal with them, 7 days after your team declines one, and 30 days after your team logs the item; a message’s own copy of the photo is deleted as soon as it is logged or declined. What vFound AI wrote for your team (item descriptions and search words, match verdicts for lost reports and weekly insights) is deleted 13 months after it was written, and the wording of the daily summary after 30 days; a claim check is kept with its claim and deleted when the guest’s details on that claim or the site’s data are deleted. A note a team member adds to a reminder and sends is kept word for word in that record's history, with the name of the team member who sent it, and is deleted with the record's history: parcels 12 months after collection or return, checkroom tickets 90 days after they are handed back or 12 months after the closing they were left at, and equipment loans 13 months after return. Ask vFound help panel conversations and the redacted log of unanswered questions are deleted 30 days after they were written, or when the site’s data is deleted. Photos emailed to a site’s address for email to inventory are deleted with their sender, subject and note 30 days after they arrive, logged or not (the photo file goes as soon as the draft is logged or discarded). Paired kiosk records are deleted with the site account, and can be revoked sooner. Background tasks that could not finish, with the details they were working on, are deleted after 30 days. The record of an AI assistant connection is deleted 90 days after it is disconnected. Error reports, which record faults in vFound itself with email addresses, numbers, codes and quoted text removed, are deleted 90 days after the error was last seen. The daily count of how each kind of email link ended, which holds no address, token or person, is deleted after 90 days. Browser push addresses are deleted when the person turns them off, the browser expires them, or the related account or record is deleted, and a host’s are also deleted when their My vFound link is reset, their email changes, or they are deactivated (including by a directory sync) or removed; an address whose deliveries keep failing is deleted after 30 days. The record of whether an email was delivered is deleted after 90 days. Current site and product access is checked again before every alert. Deactivated people cannot be selected for new work. Their open operational records remain site-scoped and follow the product retention periods above while authorised staff resolve them. People-list entries and their encrypted directory setting are deleted with the site account. A signed My vFound link expires after 60 days. Removing or deactivating a person, changing their email or resetting their link invalidates their earlier links at once.
Equipment reservation change requests and recorded status history are deleted with their reservation, including deletion of collected or cancelled reservations after 13 months without an update. They are deleted sooner when the borrower is removed from the site’s people list or the site’s data is deleted. Configuration remains until site deletion; turning a setting off does not erase retained records. Backup copies remain protected and age out under this agreement’s existing 30-day backup retention.
A report whose chosen contact method is email receives a queued acknowledgement email through the site’s normal private report journey. Phone messages require separate report-specific consent and the site’s configured provider; staff may instead call and record whether they reached the person. A report without contact details receives no outbound acknowledgement. Its reference alone does not grant private access. Authorised staff may verify a new mailbox with a report-bound code valid for 15 minutes and up to five attempts, then attach the address and send the ordinary signed private link. Those links are bearer credentials. The pending address is encrypted, and the code and challenge token are kept only as one-way hashes. This verification state is removed on replacement, completion, expiry cleanup, or when the report is erased or your data is deleted. Matches across sites are deleted when matching is switched off, the report is erased or either site is deleted, and with the group’s records 24 months after the group closes.
External copies: Customer systems and their retained copies are separate from vFound’s deletion boundary: deleting vFound’s copy does not prove external copies were deleted. Backups retain their existing boundaries.
Customer-group activity records are deleted after 24 months. Closing a group removes its group access immediately; the remaining membership, site-region, policy-template, operating-policy version, assignment, exception, acknowledgement alert and completed equipment-transfer records are deleted 24 months after closure. A site’s own owner can take their site out of a group at any time, which ends group access to it at once. Removing a site stops its assignments, exceptions and open alerts. Removing a site from a group or closing the group does not delete the site or any of its operational records, which continue under the site's own account and the periods above.
CSV invitation previews and results are deleted after seven days. Authorised invitation delivery continues from visit IDs and delivery state, kept with the visit. Event names and backup-host settings remain until the site account is deleted.
Visitor-delegation relationships and revocation records are retained until the host or delegate is removed from the people list or the workspace is deleted; the workspace shows ended relationships for only 30 days without deleting the underlying records. Arrival follow-up records, notice references and attempt statuses, and historical delegate reply attribution follow the visit’s retention and are deleted with it. Revocation ends delegated access without erasing attribution on a retained visit. Existing backup retention applies.
Preregistration records, event associations and induction acknowledgement evidence are deleted with their related visit under the controller's existing visitor retention setting. Expiry of an acknowledgement is a validity boundary, not a deletion trigger. Event signup configuration and induction versions remain until site account deletion. Turning an optional feature off does not erase retained records. Site account deletion removes the added configuration and evidence; protected backups continue under the backup deletion periods above.
These parcel-correction, notice-scheduling and attempt records follow their parcel's retention: while waiting and for 12 months after collection or return, then deletion with the parcel, or earlier with site deletion. Settings remain until site deletion; backup copies follow the backup retention already stated in this agreement.
The feedback response, active email/pass fingerprint and preference and invitation-attempt times follow the related visit's existing retention and are deleted with that visit or site erasure. A visitor's feedback opt-out clears the live rating, comment, submission time and active email choice including its fingerprint, while the opt-out and any invitation-attempt time remain until visit deletion. Disabling a setting ends access without shortening retention. Expected and signed-in visits use the existing preparation expiry, including recurring passes returned to expected between sessions. Visits marked signed out permit private follow-up access for less than 30 days after recorded departure. Access may end earlier through settings withdrawal, cancellation, approval withdrawal, token revocation, site or product unavailability, or deletion. Existing protected-backup, application-log, delivery-record and failed-task retention continues to apply. Encrypted queued invitation references and recipient/pass fingerprints are checked against the current visit before transport; a deleted visit cannot generate a later invitation. Already-started email and visitor-saved or printed copies cannot be recalled by live erasure.
10. Audits
On reasonable written request, and no more than once a year unless a regulator requires otherwise, we will provide the information reasonably necessary to demonstrate compliance with this agreement. Any on-site audit must be at a mutually agreed time, under confidentiality, and must not compromise the security or data of other customers.
11. General
If this agreement conflicts with the Terms of service on the processing of personal data, this agreement prevails. The liability limits in the Terms of service apply to this agreement, except where data protection law does not permit them. It is governed by the laws of Ontario, Canada, except where mandatory data protection law requires otherwise.
Questions, or a countersigned copy: armaan@vfound.io.
Version history
The 17 November 2026 version also adds to section 2 what the newer Equipment, Visitors and Checkroom choices keep, among them the place recorded at the Equipment desk, household members, library card sign-in, help desk tickets, document custody records, access control, door systems, guest Wi-Fi through Aruba ClearPass, the presence feed, vaccination records, remembered guests and the optional question, and that a customer's own connected systems are not sub-processors; to section 4 that a site's house rules for its AI helpers, and the visitor text it asks vFound AI to translate, are sent to the AI provider; to section 6 what an offline visitor kiosk keeps; and to section 9 which records can be exported and which cannot.
The 16 November 2026 version adds to section 2 what vFound Queue keeps about the people who take a number or book a time, and to section 9 how long each is kept. Queue's booked times, messages, survey and returning-visitor records are off until you turn them on.
The 17 November 2026 version also adds to section 2 what Queue keeps when you turn on booked-time reminders and the waiting list, consent boxes, the new kinds of answer, share links, the block list and staff first names on the waiting-room screen, and to section 9 how long each is kept. It names Google Analytics, only where you enter your own measurement id for the Queue join and ticket pages, and says that Amazon Bedrock translates the team's words in a Queue message when you turn that on. It also says that a closed account can download Queue's booked times, messages, survey answers and returning visitor records, what is sent to the AI when a site uses Match columns with AI, Describe your site or a drafted message, how the weekly read is written, and how long a note sent with a reminder is kept.
The 16 November 2026 version also says in section 6 that counter sign-in and the optional offline mode now cover the Queue desk as well: the product is kept in each counter session record, and the names of people added to a Queue line while offline stay encrypted on the device until sent.
The 13 November 2026 version adds to section 2 what Equipment keeps when a site lets borrowers open its catalogue through its own identity provider, imports a student information system file or connects an LDAP, Active Directory or Google Workspace directory, and what it keeps for quotes, payment requests, equipment rented in, deliveries, team notes and fields on borrowers and bookings; what the optional Visitors RFID cards, fast-track codes, ID expiry dates, things handed over and location checks keep; and what the optional Checkroom text PINs, guest photos on the ticket page, offers and reminder texts, replies of READY and validations keep, and the Checkroom counter sign-in records described in the security measures in section 6; and to section 9 how long each is kept. Each is off until you turn it on or your staff use it. Ask vFound now answers from vFound’s own guides to the products a site has.
The 13 November 2026 version adds to section 2 what Equipment keeps when a site uses its maintenance and lifecycle records (purchase, supplier, fund, depreciation, insurance, disposal, licences, hazardous substances with data sheet files, work orders, requests and a desk rota) and connects its own learning platform, ticketing system, Intune or Jamf, and the photos and words sent to the AI provider when staff ask for an Equipment suggestion; and to section 9 how long each is kept.
The 12 November 2026 version also describes in sections 2 and 6 the optional offline mode (what a team member's browser keeps while the connection is down and when it is deleted, and the 30-day record kept of each action), the scheduled report emails with a CSV file attached and the report data feed links an owner or manager can make, and a site changing the words of its SMS messages. Each is off until a site turns it on.
The 12 November 2026 version adds to section 2 what Equipment keeps when you turn on its newer options or your staff use them: waiting-list places, risk-assessment answers, saved items and a borrower's calendar address, stock handed out and supplier contacts, fees entries, deposits, payments you took and invoices, saved scan positions and borrowers' stock-take answers; what the Checkroom storage and queue choices a site can turn on keep (where things have been, ID checks at hand-back, pickup times, To store and To fetch tasks, team members’ queue status and pickup approval requests) and the Checkroom records kept whatever a site chooses (photo and tag checks at hand-back, who marked things missing or out for a while or reminded a guest, and who blocked a hook number or opened extra ticket numbers); and to section 9 how long each is kept. vFound records fees and payments you took yourself and never processes a payment. The previous version was dated 7 November 2026.
On 13 November 2026 sections 2 and 9 began to list what the optional Checkroom hotel and event choices keep and how long each is kept: vehicle plates, key notes, photos and damage marks, tamper seals, shipping notes, bell desk deliveries, guest history, the under-18 form, event RSVPs and a member list. Each is off until you turn it on.
On 12 November 2026 sections 2 and 9 began to list what the optional Visitors workplace features process and how long it is kept: staff sign-in, catering requests, appointment pages, desk, room and parking booking and reception, signage and room displays. Each is off until you turn it on.
On 12 November 2026 sections 2 and 9 also began to list what the optional Visitors invitation, document, contractor, school, building, visiting-limit and connector features process and how long each is kept: invitation wording and reminders, documents uploaded and signatures given before arrival, event waitlists, host alerts by phone and messages between a visitor, their host and the desk, documents to sign, inductions with a quiz, contractor companies and their documents, permits to work, the school office, building tenants, wards and residents, and Cisco Meraki and Eventbrite connections. Each is off until you turn it on.
On 11 November 2026 section 2 began to list what the new Equipment options keep when you turn them on or your staff use them (accepted terms, checkout photos, trainings and their proof, borrower types, holds, hand-overs, clearance certificates, directory groups for trainings and kiosk returns), and to say that Equipment checklists are on every plan. Nothing you agreed to changed, so the version date stays 7 November 2026.
The 12 November 2026 version describes in section 2 the Visitors blocklist, the optional check against the US Consolidated Screening List, the visitor directory, anonymising a person, and emergency roll calls with their messages and mobile number, and in section 9 how long each is kept. It no longer says that vFound runs no watchlist screening. Nothing about a visitor is sent to the list’s publisher, and SMS and WhatsApp use your own provider account, so it adds no sub-processor.
The 7 November 2026 version says in section 4 that Stripe is used when you pay by card, and that an invoiced account has no card payment. Also from this version, the word “venue” is replaced by “site” throughout, with “guest page” and “guest website” for the public page; no obligation changes.
The 4 November 2026 version describes the Ask vFound help panel in sections 2 and 4 and how long its conversations are kept in section 9, and says in section 4 that vFound AI helps choose which found items a guest is told may match their report.
The 3 November 2026 version replaces OpenRouter and the model providers it used with Amazon Web Services (Amazon Bedrock, which runs Anthropic's Claude) in Sydney and Melbourne, Australia, as the sub-processor for vFound AI (section 4), says what the claim check is given in that section, and section 5 now says AI requests are processed in Australia.
The 3 November version also calls the group's command centre Network settings in section 2.
The 2 November version changes no processing terms. Its date moved with the Privacy Policy, which now says how "Check my claim or report" works on a group’s organisation page.
The 31 October version adds to section 2 that, while matching across venues is on, a guest with an open report may be told about a found item at another venue of the group (never one that keeps its found items private), and that a venue page listed on a published organisation page shows the group’s name and links to its other locations.
The 30 October version adds to section 2 messages between your team and a guest about a lost report, and the choice to keep your found items private.
The 25 October version adds to section 7 that your owners and managers can delete a guest’s personal details from a lost report that never became a claim, which leaves an anonymous record of the report (its category and when it was reported). It also adds to section 2 that an organisation page can list found items that its venues already publish, off unless the group turns it on, and to section 7 that your owners and managers can export your venue’s audit record. Section 2 now says that an item moving between venues of one authorised customer group takes its finder details with it. Section 7 now says that a group owner, manager or regional manager can find one person’s records by email address or phone number at the venues they manage with Lost & Found open, to delete the details in each venue.
The 24 October version describes in section 2 lost-item reports your team records for a person by telephone or in person, which are on unless you turn them off, the private location or journey details you can choose to collect, organisation pages a group can publish to route a report to one of its venues, matching across a group’s venues, and selected webhook events you can send to systems you choose. Section 9 says how acknowledgements, phone messages and mailbox verification work for those reports, how long matches across venues are kept, and that customer systems sit outside vFound’s deletion boundary.
The 23 October version describes Visitors delegates and unanswered-arrival escalation, both off unless you turn them on, in section 2 and their retention in section 9. Sections 2 and 9 also describe the Equipment catalogue and Parcels desk notice hours, which remain off unless the venue turns them on. Parcels wrong-recipient reporting is on unless the venue turns it off; an existing saved off choice is preserved. Venues can now let guests reserve luggage space ahead, and link an event ticket or wristband code to a checkroom ticket. Both are off unless the venue turns them on. Connections to Cloudbeds, OfficeRnD Flex and Microsoft Entra ID are part of vFound Enterprise; a venue can still pause or remove an existing connection at any time. This version also describes optional claim email verification and journey details, Checkroom phone alerts, and visitor preregistration, event signup and induction acknowledgements. This version also describes optional Checkroom ticket conversations, Equipment specifications and reservation change requests, and Visitors accepted-terms copies and feedback, with their access and retention limits. Claim privacy guidance, search-ended email, Checkroom collection receipts, Visitors accepted-terms copies and Parcels wrong-recipient reporting are now on unless the venue turns them off; existing saved off choices are preserved. The 22 October version adds equipment status history and optional staff warranty reminder records in section 2, and CSV invitation previews, event names and optional backup-host notices in section 2 with their retention in section 9. It also adds in section 2 found-item messages that members of the public send to your venue, when you turn them on, and their retention in section 9. The 19 October version adds in section 2 the internet (IP) address a lost-item report sent from your lost and found page comes from and the approximate city, region and country derived from it, which your owners and managers see in full and your other team members as the place only, and in section 4 that the location lookup also serves those reports. The 17 October version changed nothing in this agreement: its date moved with the Privacy Policy, which now describes vFound support records. On 16 October it removed the optional service through which a guest could pay vFound to post an item back, which was never switched on for any venue, so Easyship is no longer one of our providers (section 4) and no shipping details were ever sent to it from a venue. It also adds scoped open-work lists, Enterprise custom attributes and workflow checklist records (sections 2, 6 and 9). On 15 October it added in section 2 sending found items between venues of an authorised customer group and the record kept of each move. On 8 October it added in section 6 that encrypted copies of the daily backups are also kept in OVHcloud’s Beauharnois region in Canada. It also removed the stopped server that held archives from before our September 2026 move, which has been deleted (sections 4 and 5). On 7 October it named Resend, which now sends vFound’s service email, as a sub-processor in section 4, and added in section 2 the record of whether each email was delivered, kept 90 days without the address (section 9). On 6 October it added one-time sign-in links by email to the security measures in section 6. On 5 October it stopped describing spoken requests in Ask vFound, which no longer takes them, and added how long background tasks that could not finish, disconnected AI assistant connections and error reports are kept. On 4 October it added email to inventory, the weekly insights and their Monday email, photo splitting and duplicate checks, what is withheld from the AI, how long what the AI wrote is kept, and what stays after an account is closed, and it clarified the closed-account exports and when a hotel stay is deleted, a venue owner’s right to take their venue out of a customer group, and that a platform administrator’s reads and refused changes of customer records are logged, and that describing a lost checkroom ticket to the AI sends no ticket notes. On 3 October it added the private, minimal hotel stay context used by Lost & Found and Parcels, with manual, CSV and API input, source freshness and separate room-at-event history, and customer groups with regional access, aggregate oversight and explicit per-venue policy application. It also covers customer-configured named operating-policy versions, local exceptions, acknowledgements and aggregate service-level alerts, which remain off until a group manager configures them. On 3 October it also covers a customer-authorised Cloudbeds connection limited to read:reservation and OfficeRnD Flex and Microsoft Entra ID connections limited to source ID, name, email and active status for the shared people list. The Cloudbeds reader keeps only the minimal stay context described below and never changes provider records. The OfficeRnD reader excludes memberships, bookings, invoices, payments, custom properties, addresses and phone numbers; the Entra reader never creates vFound staff accounts, roles or access decisions. It also states that deactivation prevents new assignments while authorised venue staff can resolve open parcels, equipment, reservations and visitor records. On 2 October it added optional private visitor photos, photo badges and a staff-recorded visual check of a physical photo ID, with no ID document image or number stored and no automated verification or facial recognition. On 25 September it began to cover vFound Parcels, vFound Checkroom, vFound Equipment and vFound Visitors, directory connections and My vFound pages. On 26 September it added Checkroom stations, events, its exit queue, kiosk self check-in and fee recording. On 28 September it added that every product’s records can be exported for 90 days after an account closes, that My vFound links expire after 60 days and can be reset, that people-list email addresses are shown in full only to owners and managers, that a visitor type can follow the venue’s retention period, that lost-item report links expire after 30 days, that a host’s browser alerts end when they leave the people list, and that Slack host connection records and the Checkroom phone wallet option are no longer kept or offered. The previous version was dated 19 October 2026.
Also on 15 October 2026: optional enterprise sign-in uses the customer’s own OpenID Connect or SAML identity provider. Optional authenticator-based two-step sign-in is available to venues on an arranged plan (vFound Enterprise, Terms section 3). Owners can require it for their team; venue policies never force it on platform administrators. These settings start off. No identity-provider account is supplied by vFound. When an arranged plan ends, single sign-on and two-step sign-in are no longer required and sign-in falls back to the password.
Shared lost-report kiosks (15 October 2026): A venue can pair a tablet for passenger lost-item reports. The normal report, language, consent and retention rules apply. The private report link is emailed rather than shown on the shared screen. Entered details clear on submission, return to the home screen or 60 seconds without activity. Personal sign-in and language cookies are cleared on kiosk entry; device pairing still uses an essential, revocable cookie. The venue is responsible for securing and locking its tablet.
Lost & Found integrations (15 October 2026): A venue can explicitly give a customer-managed API key permission to create a guest report, record a human ownership review and decision, record release approval and physical pickup, or record eligible donation or disposal. The audit names the manager who created the key; the customer must control its own operators. A review keeps its method, result, actor and time with the claim, not an identity-document copy or a claim of document authenticity. Custody reads include the private collection name and time, but no signature image. Claim erasure clears that name and any handover history that contains it. These decision and handover operations are unavailable to MCP and Ask vFound assistants.
Phone alerts (15 October 2026): SMS and WhatsApp notifications are optional, off by default, and use the venue’s own messaging-provider accounts. A guest must explicitly choose each channel for their claim or lost-item report. We send the guest-supplied number, venue name and a private link through that provider; WhatsApp uses the customer’s approved templates in English or Arabic. The customer may change the words of each SMS; every SMS still names the venue and carries that private link, and wording with any other web or email address is refused. Email continues separately. Provider acceptance is not proof of delivery. Replies go to the customer’s provider, not to a vFound message inbox. If the customer connects its provider’s reply address, vFound reads a reply only to recognise a stop word such as STOP and does not keep its text. Phone alerts are available to venues on an arranged plan (vFound Enterprise, Terms section 3), and they stop when that plan ends.
Phone-alert choices include an encrypted number, a keyed fingerprint of it used only to match stop replies, channel choices, language and consent timestamp. They remain with the underlying record and are removed when it is deleted or its guest details are erased. Stopping both channels through a message’s private link, which keeps working while the choice exists, clears our active alert number for that record; a stop reply does the same for every alert to that number from that venue or group, and START does not turn alerts back on; messages already accepted by a provider cannot be recalled. Delivery-attempt records and provider references are kept for 30 days and pruned nightly. The customer controls provider fees, sender registration, template approval, local messaging rules, the provider’s own retention and international processing. vFound supplies no messaging-provider account. A dedicated deployment must assess those providers, carriers and recipients separately; residency mode cannot certify their processing locations.
Dedicated customer deployments (15 October 2026): The hosting locations and providers below describe vfound.io. A separately agreed dedicated deployment uses the customer’s infrastructure and the locations and providers named in its contract. Optional residency mode disables vFound’s default external services; customer-configured destinations remain under the customer’s control. Infrastructure, mail routing, backups and each connected service must also meet the agreed location requirements. The configuration check does not establish the physical location of a customer-configured service.
