Privacy policy
What vFound collects, why, who can see it, and what you can ask us to do about it. In effect from 17 November 2026.
vFound is operated by Naltyx Data and Marketing Consulting (“Naltyx”, “we”), Ontario, Canada. We sell software to organisations and their sites. We do not sell personal information, we run no advertising trackers, and we do not use your data or your guests’ data to train AI models.
Contents
1. Who is responsible for what
This distinction matters, so it comes first.
- We are the controller for site account data, staff sign-in data, billing data and data from our public website. We decide how that is used. The site continues to control the ownership claim and its decision to release an item.
- The site is the controller for the found items it publishes, for claims made to it, for found-item messages people send it and, if it uses vFound Parcels, vFound Checkroom, vFound Equipment, vFound Visitors or vFound Queue, for its parcel, checkroom, equipment, visit and queue ticket records. We are only its processor, acting on its instructions under our Data Processing Agreement.
So if you submitted a claim, the site handling your item decides what happens to your information. Contact them first; we will help them respond.
2. What we collect
If you make a claim as a guest: your name, email address, optional phone number, where and when you think you lost the item, your description of it, your answers to the site’s verification questions, any photos you upload as proof, and your messages with the site. If your item is returned we also keep a shipping address if it is sent to you, or your name and, where the site asks for one, your signature when you collect it, plus any pickup time you book and any feedback you give. We also record the internet (IP) address you submitted from and an approximate city and region derived from it, so the site can weigh a claim before handing over someone’s belongings, and so we can detect abuse. We do not collect precise GPS location. The site’s owners and managers see the address and the approximate place; its other team members see only the approximate place, and view-only members see neither.
When a site enables claim email verification, we send a one-time code to the address you provide before creating a claim. It expires 15 minutes after your request. 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. Email jobs are encrypted and checked again before sending. Database backups and failed email jobs follow the retention periods described in this policy. This checks control of a mailbox, not ownership of an item.
If the team posts your item to you: the delivery address you give on your private claim page, and the carrier and tracking number the team records. The site's team uses them to post the item with a carrier it chooses and pays itself; vFound sends nothing to the carrier. If you open the tracking link, your browser goes to the carrier's own website, under that carrier's privacy policy. These details are never shown publicly and are deleted with the claim's details.
If you open a private walkthrough: a walkthrough is a video we make for one named person or organisation and send as a private link, so a record of it being opened is personal information about the person we sent it to. When the page is opened, our server records which walkthrough, the time, whether the device is a computer, phone or tablet (worked out from the browser’s identification, which we do not keep) and the main language the browser asks for. We do this because we have a legitimate interest in knowing whether a film we sent has been seen, so that we can follow up with the person it was made for. Nothing is stored on your device for this, the page sets no cookies, and the only thing it reads from your device is whether you pressed Allow on an earlier walkthrough. This applies only to walkthroughs we make as prospect films; walkthroughs made for our customers record nothing. Only if you press Allow on the page, we also record how much of the video you play and for how long, how far you get, which chapters you reach, the subtitle language you choose and whether you reach the end, and your browser keeps one note that you allowed it. That note applies to all vFound walkthroughs in that browser until you press Stop, which removes it and ends recording on every walkthrough page open in that browser. Stopping does not delete what was already recorded: it stays for the 12 months in section 6, or until we delete it on your request (section 9). Without Allow none of that is recorded or stored. We do not link one open to another unless you press Allow: no code made from your IP address or your device is kept, so a count of opens is not a count of people. We do not store the IP address. Visits by our own team while signed in, and the automated previews and crawlers we recognise, are not counted. The records are shown only in vFound’s platform administration, never to a site or to anyone else you share the link with. Our emails to ourselves about them name the walkthrough and the person or organisation it was made for (section 4).
If you report a lost item: your name, email address, optional phone number, what you lost, when and where, any item-location link you add (such as an Apple Find My link) and any photo of the item you choose to add. The photo is kept privately with your report: the site's team can see it, it is never shown publicly, and when the site keeps AI assistance switched on, vFound AI compares it with found items to suggest matches. When you send the report from the site’s lost and found page, we also record the internet (IP) address it came from and an approximate city, region and country derived from it, to prevent abuse and to help the site check a later claim of ownership. The same people at the site see them as for a claim. A report made at a site’s kiosk, by its team or through its own systems keeps no address. When you change your report from its private page, the site’s team can see what it said before each change; those earlier versions are kept and deleted with the report, and also when your details on a claim made from it are deleted. If you set an alert before 7 October 2026: your email address and what to watch for. New alerts are no longer offered; a lost report includes them.
If a site enables optional journey details, you may add a flight or route, service date and time, seat or gate, event name, and station or seating area to your private lost-item report. Do not include passenger names, booking references, identity documents or medical information. These details are available through your private report link and to authorised site staff; platform support access, service providers and backups follow the access and processing arrangements described elsewhere in this policy. Earlier values are retained in the report's edit history. The details follow the existing report retention and deletion periods; erasing guest details from a linked claim clears the current journey details and report versions.
A site’s 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 the site chose those fields. Do not provide passwords, payment information or identity documents.
Where the site chose those fields, its team can record the same kind of private details on a found item. They are not shown on public item pages.
Messages about your lost report: the site’s team can write to you about your lost-item report. We keep the team’s messages and your answers with the report, email each message from the team to the address on the report with a fresh link to your private report page, and show the conversation there, where you can answer. A reply to that email goes to the site’s own reply address, not into the conversation. The messages are plain text, are never sent to vFound AI and are deleted with the report, and also when your details on a claim made from it are deleted or an owner or manager deletes your details from the report.
If you tell a site you found something: when the site has turned this on, the photo you send, what the item is, where and when you found it, where it is now and, only if you add them, your name, email address and phone number. Nothing from your message is published while the site reviews it: the site’s team and our platform administrators can see it. If the team logs the item, its photo may appear on the site’s found items page like any found item the team logs. If you give an email address, we send it one short receipt (none if that address has had several receipts recently), and replies go to the site. To stop receipts being used to flood someone’s inbox, we keep a coded (hashed) form of the email address and a count of receipts for two days. When the site’s team starts logging the item with vFound AI switched on, the AI provider below reads the photo to suggest a description, as it does for any found item. Sending a message is not proof that the site or vFound has the item.
If a site receives parcels for you (vFound Parcels): your name, email address, room or apartment and any ID the site adds to its list; and for each parcel, a photo of its label (showing whatever the label shows, such as your address), the carrier, tracking number and sender, handling instructions, where it is kept, any reminder snooze or hold date, whether you said you were at the desk, any delegate name and email you provide, the emails sent to you about it, and the name, optional pickup photo and, where the site asks for one, the signature of whoever collected it. For an outgoing parcel or a delivery round, it also records the destination, courier or recipient and handover signature. Parcel records are never shown publicly: the site’s team and our platform administrators can see them, and the AI provider below reads a label photo when the site logs a parcel with vFound AI switched on. If the site also uses vFound Visitors, the same list is who visitors can come to see, and you are emailed when a visitor signs in to see you. If the site turns them on, you are also emailed when your visitor signs out, and you can use your private My vFound link to approve or decline visitors who asked at the kiosk, the QR sign or the site’s visit request page to see you, and to write to a visitor and the desk about a visit.
If an Enterprise site offers visitor alerts by phone, you can choose SMS, WhatsApp or both on your private My vFound page with your own mobile number. We first send one code to that number through the site’s own messaging provider, and no alert goes to it until you type that code on your page. We keep the number encrypted, a keyed fingerprint used to recognise a stop request, your channel choices, language, consent wording version and consent, confirmation and withdrawal times; the code works for 15 minutes and only a scrambled (hashed) form of it is kept. The provider receives your number and a message with the site’s name, a line that a visitor has arrived for you or, if the site turns that on, has left, and a link that opens only these alert settings. The message never contains the visitor’s name, and the link never opens My vFound. You can stop alerts with that link or the button on your page; where the site’s provider passes replies on to vFound, replying STOP works too. Stopping, an owner or manager resetting your My vFound link, a change of your email address and leaving the site’s people list each end the alerts and every link sent by phone at once, and clear the stored number. A number never confirmed is cleared after one day. Delivery-attempt records, without message text or phone numbers, are deleted after 30 days. The site must manage its provider’s own records, opt-out lists and retention separately.
Wrong-recipient reporting is on unless the site turns it off, and an existing saved off choice is preserved. If you confirm a wrong-recipient report, we keep your report that a parcel is not yours, linked to the parcel and site, the time it was reported and when staff resolve it, with the parcel's activity history. Reporting it removes its assignment to you and stops its reminders; the site's staff check and correct the recipient. It does not identify another recipient to you. Optional parcel desk notice hours also keep scheduled delivery times, delivery-attempt states, parcel and site references, the staff actor where applicable, and hashed forms of the recipient address and pickup code to check whether a notice is stale or duplicated. These records are not shown publicly; authorised site staff and vFound platform administrators can access them to operate and support the service. Our existing hosting, email and backup providers process the relevant data as described below.
If a hotel links a stay to an item or parcel: the hotel may store its stable stay reference, an optional guest reference, your name, arrival and departure times, source time zone, stay state, current room and the room recorded when the item or parcel was logged. This private context is visible to the site team and our platform administrators, never on a guest page. A room search helps staff navigate only; vFound never treats a room number as proof or a suggestion of ownership. The feature does not accept rates, payment details, loyalty data, identity documents, preferences or unrelated reservation notes. The hotel can enter this context manually, import it by CSV or API, or, on vFound Enterprise, connect its own Cloudbeds property key limited toread:reservation. Connection credentials and the sync cursor are encrypted, and the hotel can revoke access in Cloudbeds or vFound.
If you leave things at a site's checkroom (vFound Checkroom): what you handed in and a photo of it, its number and, for a multi-piece ticket, each piece's letter, type, storage location and hand-back state; and, if you give them, your name, email address and room; the language of your ticket; its station, event and storage location; a request to have your things ready; any fee and whether the site records it as cash or an external POS or card payment; when each piece was collected, and who collected it, with a signature when the ticket was lost. Your ticket is a private page whose long random address is the only key to it. Tags on your things show only the ticket and piece number, type, station and, on a bag tag, where it is stored; they never show your name, email address or room. The ticket’s QR code is printed only on the stub you keep. Checkroom records are never shown publicly: the site’s team and our platform administrators can see them. If your things are still there at closing, the site may move them to its lost and found, with your details in its private notes so it can contact you. If you lose your ticket and the team uses vFound AI to find your things from a description, the AI provider below compares that description (with email addresses, links and phone numbers removed) with the photos and the type of that night's checked-in items. Ticket notes and the name, email address and room on any ticket are never sent, and the team still checks who you are before handing anything back. If the site lets you reserve luggage space ahead (only when the site turns this on): your name, email address, language, the number of pieces, the time window you chose, whether you arrived, cancelled or did not come, and the checkroom ticket it became. If the site takes group bookings, we also keep the number of travellers and the group name you typed. If the site uses booking IDs, we keep the booking ID we gave you. We email you a confirmation with a private link to see or cancel the reservation. In the reservation record we keep only a scrambled (hashed) form of that link's key. Your confirmation email contains the full private link; its queued copy is encrypted. If the site also turns on pre-arrival emails, we email you once more at the same address, within a day before your time window, unless you have cancelled; that email has no private link. If the team links your event ticket or wristband code to your checkroom ticket, we keep only a keyed hash of that code, never the code itself, and only while the link is active. If the site turns on its under-18 form (only when the site turns this on), a parent or guardian can send the young person’s name and date of birth, their own name and a phone number or email to reach them, with their agreement to the words the site wrote. We keep these encrypted and show them to the site’s team, with a form number to show at the door. We do not check who anyone is, send nothing by email and delete the form 30 days after it is sent.
If an Enterprise site enables Checkroom phone alerts, you may choose SMS, WhatsApp, both or neither at drop-off or self check-in. We record only your explicit choice for that ticket. We keep the alert number encrypted, a keyed fingerprint used to recognise a stop request, your channel choices, language, consent wording version and consent and withdrawal times. The site uses its own messaging provider and pays its provider directly. That provider receives your destination number and a message containing the site name, a short ticket, ready-for-collection or left-behind status and your private ticket link; the message does not include your name, email, room, item description or photos. Anyone with that private link can open the ticket, so keep it private. You can stop alerts from the ticket's Phone alert settings. Where the site has connected its provider's reply webhook, replying STOP also withdraws alerts for that number within that connection's site or group. Stopping both channels clears the stored alert number and fingerprint; it does not stop separate email updates or recall a message already started or accepted by the provider. We retain consent records for the ticket's lifetime, except that correcting the email address on a ticket erases its alert choices and consent records at once; orphan records are removed in nightly cleanup. Delivery-attempt records, without message bodies or phone numbers, are deleted after 30 days. Existing Checkroom ticket and backup retention periods still apply. The site must manage its provider's own records, opt-out lists and retention separately.
A site may also turn on these Checkroom choices; each starts off. If it takes your phone number as your ticket, the ticket keeps only the last four digits and a keyed fingerprint of the number. The number itself is kept only where you choose phone alerts, encrypted in the alert record described above. If you prefer not to give a number, you get a PIN, kept encrypted and deleted when your ticket is finished. The team finds your ticket by those last four digits, the full number or that PIN. If the site turns it on and you choose SMS updates, you also get a PIN, and your ticket text carries it as a pickup code; it is deleted the same way. If the site lets you type your own details on your phone while the team takes your things, what you type is kept encrypted until it is added to your ticket. If you send it after the team has already checked you in, it waits for the team to add it or discard it, and the page does not open your ticket. The link and anything not added are deleted a day after the link was opened. If the site lets you add a photo of your things at self check-in, it is checked and kept like the photo the team takes. If the site turns it on, your own ticket page shows the photo of your things while they are here; only your private ticket link opens it, and the page shared with a friend never shows it. With your agreement, which the team confirms and is recorded on your ticket, the team may take a photo of you to see who to hand back to; it is kept for the site's team with your ticket, never shown publicly, never sent to the AI provider or our photo safety check, and deleted when everything is handed back or moved to lost and found. The site may mark your ticket VIP, and may see how many earlier tickets at that site share your email or phone (only ones its retention still keeps); if it also turns on guest history, its team sees those earlier tickets themselves, with the team's own notes on them. If the site uses reusable hanger tags, an NFC tag is kept only as a keyed fingerprint of its serial number and holds nothing about you. If a site uses guest tap tags, we keep a one-way hash of the tag's address and a one-way hash of a secret held by the guest's phone, with the ticket, and delete them with it. If the site imports the guest list of an event you are attending from its ticket system, its team can find you at check-in by your name, email, order number or ticket barcode; your name and email are kept encrypted for the site's team only, a barcode only as a keyed fingerprint, and all of it is deleted 14 days after the event ends. If the site uses a changing QR, your ticket page shows a code that changes every 30 seconds and holds no link to your ticket. If you share your ticket with someone collecting for you, we keep only a scrambled (hashed) form of the share link; the page it opens shows only a QR to collect with, and it ends when you stop sharing or everything is collected. A site's counter screen shows your ticket number for 45 seconds after check-in, with a QR that opens your ticket on the first phone that scans it, then leaves the screen; it never shows your PIN. We keep that link as a scrambled (hashed) form, and the link itself encrypted while the screen shows it, cleared within about a minute after its 45 seconds, and we record when a phone opened it, so the team can give you a new ticket link if it was not yours. The link ends at once if the site removes the screen. If the team gives you a new ticket link, browser alerts you turned on for the old one stop; you can turn them on again from the new page. Details typed on a phone for that ticket that the team had not added yet are always erased. Unless the team confirms that the email and phone on the ticket are yours, they are removed from it and phone alerts stop.
A site that uses Checkroom in a hotel or at events may also turn on these choices; each starts off, and while a choice is off nothing it describes is recorded. For a car or a bike, the team may record the number plate and where the key is kept, take photos of the vehicle, its key or its plate, and, if the site uses a damage diagram, pin marks on an outline with a short note and the time. You can see the marks and notes, with the time each was noted, on your own ticket page, never the plate or the key. The team also sees the marks on earlier tickets at that site with the same plate, for as long as those tickets are kept. If the site uses tamper seals, the number of the seal on your bag is kept with your ticket, with any mismatch or a note that the seal was broken or missing; if the site records seals for guests' own bags, that is the number you type at self check-in. If you or the team take a photo of a seal to fill in its number, the photo is read on vFound's own server; it is not stored and is not sent to any other service. If things arrive by carrier or are sent on, the team may record the carrier and tracking number, and a date until which things are kept. If the site uses a bell desk, a delivery to your room keeps 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. The photos, marks, seal, tracking and delivery records are for the site's team only, are never sent to an AI provider and are deleted with their ticket; a finished or cancelled bell desk task is also deleted 90 days after it ended. If the site keeps an event guest list, the ticket type and any seat or table label on it are kept with your name and email, for the team only, until the list is deleted. If the site turns on event RSVPs, a person who has an event's private link can send a name, an email address, an answer (yes, no or maybe) and how many people are coming; these are kept encrypted for the site's team, no email is sent about them, and they are deleted 14 days after the event ends or when the team deletes them. If the site turns on its member list, it keeps its members' names, email addresses, membership type and optional expiry date, encrypted, for its team only; a member is deleted 13 months after they were last added, changed or checked in at the desk, or when the team erases them, and erasing a member also deletes any RSVP answers given with the same email, and a ticket already made keeps the name and email that were filled in until the ticket is deleted. vFound sells no membership and takes no payment for any of this.
A site may also turn on these Checkroom storage and queue choices; each starts off, and while a choice is off nothing it describes is recorded. If the site keeps where things have been, your ticket keeps each storage place your things were given, with the team member who moved them, when, where from and where to, and whether the place was scanned or typed. If it records ID checks, a hand-back to someone who does not have the ticket can record which team member checked that person’s ID and when; never the document, its type or its number. If it offers pickup times, your ticket keeps the time you choose until you change or clear it. If it uses its To store and To fetch lists, your ticket’s tasks keep their type, when they were made, which team member took them or was given them and by whom, which team member finished them, any pickup time, and when they were done or ended; while it uses the To fetch list, each team member’s status (available, busy or away) is kept with when it last changed, and turning the list off deletes every status. If it lets someone else collect with your approval, the team types the name of the person collecting and we email a link to the address given at check-in, and only while the email on your ticket is still that address. The link works once and stops working 60 minutes after it was asked. To check the address, a ticket checked in while this choice is on keeps a keyed hash of it, not a second copy. For each request we keep a scrambled (hashed) form of the link’s key, the collector’s name, which team member asked and when, a partly hidden form of the address, your answer and when you gave it, and whether a hand-back used it. The email’s queued copy is encrypted. The team sees that the request was approved from that partly hidden address, and when; we cannot know who opened the email, so it never says that a named person approved. Whatever the site chooses, a hand-back records whether the team compared your photo or scanned the tag on your things, and if the team marks your things as missing or as out for a while with you, or emails you a reminder that they are still there, your ticket keeps which team member did it and when; and when a team member blocks a hook number or opens extra ticket numbers, the site keeps which team member did it.
A site may also turn on these Checkroom choices about money, shifts, terms, things left behind and messages; each starts off. Money: for each payment the site records at its desk or till, we keep its type (fee, deposit, deposit given back, tip or late fee), amount, whether it was cash or an external POS or card payment, the kind of item it was for, which team member recorded it and when. A team member with the right role can void a payment with a reason; the payment stays on record, marked void. If the team marks a ticket free, it keeps the reason the team typed. We never receive a guest's card details. Shifts: when a team member opens a shift on a device, we keep their name, a device name they type, a keyed fingerprint of a random name that device's browser keeps, the cash in the drawer when they opened, any cash drops, the cash they counted, the totals recorded during the shift and when it opened and closed; these are team records, deleted 12 months after the shift was opened. Disputes: a team member may mark a ticket disputed, with a short note about what is disputed and, later, how it was settled; the note stays with the ticket. Terms: if the site asks you to accept its own terms, your ticket keeps the exact words you accepted, the liability limit and prices shown beside them, a fingerprint of all of these, when and where you accepted them (your ticket page, self check-in or the desk) and, if the site asks, the value you declared. Things left behind: if a site turns on follow-up for things left at closing and you gave an email address, we email you a reminder on up to three days the site chose after closing, until your things are collected, moved to its lost and found or disposed of, and we keep which reminders were planned and whether each was sent, not their text. If the site sets a disposal date, it is fixed when your things are left, shown on your ticket page and in the reminders, and a later change does not alter it. vFound never disposes of anything: if the site records a disposal, we keep that it did so, when, which team member and the note they typed, and your ticket then shows that your things were disposed of. A site can print a list of tickets left at closing to give a lost-property office; it shows ticket numbers, items, places and dates, and no guest name, email address or phone number. Messages: a site may put its own words in its alert texts and one plain sponsor line on your ticket page and printed stub, not in any email; the site writes both. If an Enterprise site that uses its own messaging provider turns on offers, you may tick a box, separate from phone alerts and not implied by them, to receive offers by SMS after you collect your things. We keep that choice with the alert record described above (the encrypted number, its keyed fingerprint, the time and the wording version). After everything is handed back, that provider receives your number and one text with the site name, the site’s offer line, a coupon code if there is one, a prompt to answer the survey if the site asks one, and your private ticket link. Offers are sent only where the site has saved the details its provider needs to pass STOP replies on to vFound; when your STOP reply reaches vFound, it withdraws offers and alerts for that number. Whether or not replies reach us, you can stop offers alone, or alerts alone, from the ticket’s Phone alert settings. Only if you ticked offers, your ticket page after collection also shows the coupon and a short survey; your rating and optional comment are kept with the ticket. Closing a ticket in bulk, or moving things to lost and found, sends no offer. A site’s team can also send one short text, such as the closing time, to guests whose things are still there and who chose text updates about them (never to a guest who only chose offers); it goes through the same provider, with the site name and your private ticket link, and the words the team typed are kept 30 days with the delivery records. A site may also schedule an offers text to guests who chose offers and whose things were collected, aimed only by how many times a phone number was given on tickets the site still keeps and when the last of them was; it sends one text for each number, checks your choice again just before sending, and keeps its words and its rule 30 days. If the site turns them on, it may also send a reminder, once, to a guest who chose text updates after their things have been there a set number of hours, and a follow-up, once, to a guest who chose offers a set number of days after collection; your STOP reply ends both. If the site turns it on, you can also ask for your things by replying READY to its texts: vFound reads the reply only to find your own ticket from the number you gave and does not keep the reply or send anything back. A site may also write how to make a claim for damage or loss, shown on your ticket page. A site can print a receipt for the money it recorded on your ticket, or on several of your tickets together; it shows ticket numbers, amounts and how each was taken, never your name, email address or phone number, and its QR opens a page that tells whoever scans it whether the receipt still matches the site’s records, with the site name, a receipt number and the total. A site may also record a validation, a partner discount code and its amount, on your ticket; it holds no details about you. Payment, terms, reminder, disposal, validation and survey records are deleted with the ticket they belong to; shift records are kept 12 months as described above, and the site’s own provider keeps its own records of messages.
If a site turns on Remembered guests, a guest can choose to be remembered at that site. The guest first proves the number is theirs with a text code sent through the site's own text provider. The site then keeps the number (encrypted), a visit count and, if the site uses points, a points total. They are deleted when the guest asks (on their ticket page, on the site's My tickets page after a text code, or by asking the site to delete their data), at the end of the retention the site chose (3 to 24 months after the last visit), 30 days after the site turns the choice off or its plan ends, or when the site is deleted. Points are a thank you from the team: they have no money value, and vFound takes no payment for them. Offers by text from a remembered guest's profile are a separate choice, reach a later ticket only when that ticket's number was proven by text code and the guest made no different choice on it, and a STOP reply ends them.
A site may ask one optional question on the ticket page. Answers are counted with others, never shown with a guest's name or number, kept against the ticket for 30 days, then only a count for each day remains (kept 13 months). Sites may not ask about health, beliefs, ethnicity, sexual orientation, politics, age or gender; vFound refuses questions that use those words but does not read what a site writes beyond that check. A site can show buttons on the ticket page that open the guest's own WhatsApp, text message or Telegram app with the ticket number and code already typed; the guest decides whether to send it, and vFound sends and reads nothing through them.
If a site connects its own Salesforce (in beta) and chooses to add Checkroom guests to it, a guest who agrees on their ticket page to offers by text and to the team keeping their name and number in its own customer system has that name and phone number sent there, never their email address. An offers choice made without that wording is never sent. If the guest replies STOP, or their ticket data is erased, vFound deletes the lead it created there while the connection is on; a lead the site already had is not touched.
If you borrow something from a site's desk (vFound Equipment): your name and, if you give them, your email address and an ID or reference such as a student number, room or department; what you borrowed, when, and when it is due back; the emails sent to you about it (a receipt, reminders, reservation notices and a return receipt, with one receipt for things from the same checkout brought back together), in the language chosen for you; your signature where the site asks for one; any reservation you make, whether it needed approval, its dates and status; an extension request or problem report you send; and when each item came back, in what condition, with any note or photo the team takes. An equipment item can also hold a serial number, replacement value, purchase and warranty dates, site-defined custom fields, maintenance history and stock-take dates. Owners and managers can add a purchase price, supplier, order number and fund or cost centre, depreciation settings, insurance details and how the item was disposed of. Maintenance work orders can name a team member or an outside technician, a supplier, a cost, a fund or cost centre and the parts and tools used, and a borrower’s problem report can become a maintenance request that names them. A site can also keep licences for its equipment: name, vendor, seats, end date, cost and the items they are installed on, never a licence key. Owners and managers can also keep a register of hazardous substances, as the site enters it: the substance, where it is kept, hazard classes, supplier, review dates, notes and an optional safety data sheet file. We also keep equipment status changes and their times for utilization reports. If a team member chooses warranty reminder emails, or an owner or manager chooses insurance, licence and safety review reminder emails, we keep their choice for that site and a record of each delivery attempt, linked to the item, licence or substance, its date and the team member. These records are deleted with the site; item-linked records are also deleted when the item is deleted. These records are never shown publicly: the site’s team and our platform administrators can see them. The AI provider below only ever sees the photos staff choose to send for these tasks, all of them photos attached to an item (a photo a site adds, or the photos taken when an item goes out and comes back, when staff ask for a comparison), the item name or kind of item a staff member types for a draft check list, and a photo of a supplier’s invoice when a manager asks for a purchase order to be filled from it, never who borrowed it. vFound does not detect people in a photo itself: the provider is told to ignore any person and to say when one is visible, and vFound throws such an answer away, but a photo that shows a person by accident is still sent for that one request. Staff choose each of these; vFound does not send them on its own. If a site keeps a desk rota, we keep each shift’s typed name, times and note until a manager removes it or the site is deleted, and places taken on a shift are deleted 13 months after it ended; the site’s team and our platform administrators can see them. When authorised sites in one customer group move an item, vFound also records its owning, source, destination, service and custody sites, locations and codes, transfer status and times, operational notes and which team members performed each step. Borrower and staff history from the source site is not shown to the destination through the transfer. If the desk hands you stock (such as batteries, gloves or radios), we record what it was, how many, where it came from and its batch, who handed it out and when, when it is due back if it comes back, the terms you accepted where the site asks, and how many came back or were written off. If the site connects its own learning platform (Moodle, Canvas or another LTI 1.3 platform) for course rosters, we keep the platform’s address and identifiers, a signing key we create for the connection (its private half is encrypted) and, for each course a teacher opens the tool from, the course’s identifier and title; when staff read a course roster, vFound reads each learner’s name, email, student reference and status only to match them to the site’s own people list, keeps nothing about a learner who does not match, and records the training for those who do. If the site connects its own Jira, Zendesk or ServiceNow, we send it a ticket for a damaged return or one that staff raise, holding the item’s name, label code, asset tag, serial number, category, location and condition, the desk’s note and the borrower’s own description of the problem exactly as written (which can contain a name or phone number), and keep a copy of the ticket text, its link, its status and its sending errors. If the site connects Microsoft Intune or Jamf Pro, we keep its encrypted credentials and, on the items it links, each device’s record number, name, serial number, maker and model (a device name can contain a person’s name). If the site connects Kandji (in beta), vFound only reads from it: on the items it links, each device's name, serial number, model and platform (a device name can contain a person's name).
Some of these Equipment records exist only when the site turns an option on (accepted terms, returns at a paired kiosk and passing an item on from My vFound); the others only when the site's team uses them (checkout photos and notes, what it went to and who collected it, trainings, borrower types, holds, hand-overs they start and clearance certificates). The record can then also hold: the terms or waiver text you accepted, a fingerprint of it and the time; a photo and a note of each item as it goes out; the place, department, project or job it went to, who collected it for you and why; the trainings you hold, when you earned them, when they expire and, where the team adds one, a scan of the proof, which at the site only its owners and managers can open; the borrower types you belong to; a hold on your borrowing with its reason (the email we send you about a hold never shows the reason); a request to pass an item to someone else and their confirmation; and a clearance certificate listing what was out with you when it was issued. A training can also come from a group in your organisation's directory, when the site links one. If you return equipment at a paired kiosk, we record which kiosk and that nobody at the desk has checked it yet. The reservation options can also hold: your place on a waiting list (your name, your email, the times and a note), your answers to a risk-assessment form and who approved a booking, the places you chose to collect from and return to, the items you saved, and, if you ask for one, a private calendar address for your bookings and due times. If a site opens its equipment catalogue or lets people ask for an item by scanning it, the catalogue page shows no personal details, and a request by scanning sends an email only to an address already on the site's people list.
If a site records fees for Equipment: it keeps what you owe it for borrowing. Each entry holds the amount and currency, what it is for (a late return and how late, damage, a replacement, use of an item or a fee the site names), any tax, a billing code or department the site types, the item and checkout it came from, its status, the reason a team member types when they waive or void it, and which team member recorded it, with your name, your email address and your ID or reference. The site can also record a deposit it holds for you, a payment it took from you by its own means (with the method and reference its team types), and invoices numbered for its site; a statement is worked out when someone asks for it and is not kept. vFound does not take, hold or refund any payment: an entry is only a record. The site's team and our platform administrators can see these records, and the site's private API, webhooks and CSV downloads carry them. Your My vFound link shows only your own balance, deposits, entries, invoices and statements. If the site chooses to stop borrowing until you owe less than a limit it sets, nothing can be checked out or booked for you while you owe that number or more, in its fee currency or in any other currency you owe in (nothing is converted); anything you have out can still be returned. Entries the site recorded under an email address before you were on its people list are counted as yours when you are added with that address, or when an owner or manager changes your address to it, unless someone else on the list has the same address; the site's audit log records which entries moved and who caused it. A reference never moves entries. Your 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, and an invoice goes when it is 13 months old and none of your entries in its currency remain. They are also deleted with the site. If the site removes you from its people list, the entries stay under the name and reference they were recorded with, without the link to you or your email address; a keyed fingerprint of your address is kept with them until they are deleted, so that if the site adds the same address again they are counted as yours again.
Quotes, payment requests, deliveries, team notes and custom fields for Equipment: when a site's team uses these, it can keep, about you or a booking of yours: a quote with its items, dates, price lines in a currency, terms and every revision; a payment request with an amount, currency, an optional date and a note, and which payments the team recorded against it; a delivery address, a delivery and a collection time, the team member who runs it and a note; notes the team writes on an item, which are free text and can name you if a team member types your name; and, on a site with Enterprise, the fields the site defines for its borrowers and bookings. These are for the site's team and our platform administrators only; nothing in them is sent to you, shown in My vFound or used by vFound for anything else, and vFound takes no payment. Your quotes, payment requests and borrower fields are deleted when the site removes you from its people list; a booking's delivery details and fields are deleted with the booking; team notes are deleted with the item; quotes and payment requests are deleted 13 months after they were made, and all of it with the site.
Two more Equipment options are off until the site turns them on. With scan positions, a team member who says yes on the Equipment screen and then allows their browser has the place where their phone or computer was recorded when they count items in a stock-take, or scan an equipment label from a workspace screen other than the Equipment desk, with the item, the time and who scanned. The place is also recorded when a team member hands items out or takes them back at the Equipment desk, the main Equipment screen where items are checked out and back in, once for the items just handed out or taken back, with the item, the time and who did it. A team member agrees to this in words that name the desk: an earlier yes that covered only equipment labels does not cover the desk, and nothing is recorded at the desk for them until they agree again. Other Equipment pages, such as kits, transfers and last seen, are workspace screens. The place is rounded to about 100 metres unless the site chooses exact positions. Nothing is recorded between scans, a borrower, a kiosk or an API key never records a position, and a team member who says no again has their saved positions at that site deleted. With borrower confirmations, while a stock-take is open a borrower who holds an item it covers can tell the site on their My vFound page that they have it or that it is not with them; we keep the answer and the time.
Household members. A site that uses household members can record, under a borrower on its people list, a first name or nickname for each member of that borrower's household, for example a child in a toy library, with an optional limit of items out at once, and nothing else about them. The name is shown to that site's team and kept on the loans handed out for that member. It is never sent in webhooks, the API or exports to connected services, which carry only a number that means nothing outside the site. Removing the member or the borrower deletes the member and the name from the site's records, including stored webhook deliveries and saved API responses, and everything is deleted with the site.
If a site turns on library card sign-in (in beta, on vFound Enterprise), its team can store a library card number on a person on its people list, and the borrower can then sign in to that site's Equipment catalogue with the card number and PIN. The card number is kept with the person, appears in the site's people export and is deleted with the person and with the site. The PIN is passed only to the library system the site named, to be checked there, over a connection that checks that system's certificate whenever it crosses the internet; vFound does not store, log or audit it. A sign-in, and a failed one with a card that is linked to a person, is recorded with that person in the site's audit log, never with the card number or the PIN.
A site's fixed RFID readers post tag reads that are kept with the tag, the matched item, the reader and the time, never a person, for 90 days, and are deleted with the site. When equipment is posted back, the site can record the carrier, tracking number, tracking link and posting day on the loan; these are kept and deleted with the loan. A site can record start and end days and a short fee note on a person's borrower type, and booking credits as a count for each person; these are records only, vFound takes no money for either, and they are deleted with the person and with the site. A credit used for a booking stays used when retention later deletes that booking.
If a site marks someone as a volunteer, we keep that mark with their record on the site's people list. When a volunteer or a team member takes a place on a shift, we keep the name shown on that place with the shift. A person's places on shifts that have not started are released when they are made inactive, taken off the list or, for a team member, removed from the site. Places on shifts that ended are deleted 13 months after the shift, and the mark and places are deleted with the person or when the site is deleted. If a site turns on member cards, each person on its people list can show a card with a QR code. We keep a random value and a hash of the code, not the code, and a new code ends the old one. The site can also record a membership type and a valid-until date for a person. These are kept with the person's record, are part of the people export, and are deleted with the person or the site. They carry no payment. A pass's QR code opens a page that needs no sign-in. It shows the pass name, its note, the guests it allows, the site, the valid-until time and whether the pass is valid, and never who has it. The page is not listed by search engines. The site's own signed-in team can see who has the pass when they check it at the desk.
If a site connects a Google Calendar (in beta), vFound adds an event for each approved Equipment booking naming the item and the time, never the borrower, and removes it when the booking is cancelled. Tickets sent to a receiver address a site gives contain the item details and the notes written by the team or the borrower, which can include personal details. Staff at a site that keeps hotel stays in vFound can look up in-house guests (name, room and departure time) when checking equipment out; the guest they choose has their name and room copied onto the loan, no link to the stay is kept, and nothing is read from or written to a hotel system for it.
If a site turns on Equipment access control (in beta), vFound 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 address the site chose, which is the site's own door or access system, when an item is handed over (only in the categories the site chose, if it chose any), and a message to take that access away when the loan ends. That system is the site's own provider, not a vFound sub-processor. When a person is removed from the site's people list, vFound first asks that system to take their access away; if that cannot be confirmed after five tries, the person is removed anyway and the access is recorded as not confirmed, so the site must remove it in its own system. Records of access for loans that have ended are deleted 30 days after the access was taken away, and records whose removal could not be confirmed 180 days after they were closed.
If you visit a site that uses vFound Visitors: your name, who you came to see and when you arrived and left (including whether you were signed out automatically); if you or the site give them, your email address, company and the reason for your visit, your answers to questions the site sets, a time you are expected, the dates your pass is valid and whether it repeats; the language of your emails and the invitation sent to you; whether the site approved or denied the visit; any short reply your host sends to the desk; and, where the site has visitor terms, a copy of them, that you agreed, and your signature where the site asks for one. We also record who approved the visit (a team member, or your host from their phone) and, if the site turns on messages, what you, your host and the desk write to each other about it. During a roll call the site also records whether it marked you safe, as needing help or not yet accounted for, when, and which team member did it. Your pass is a private page whose long random address is the only key to it. Once the site has approved the visit it may show arrival information the site chooses to share, and the site’s Wi-Fi details while you are signed in. Printed badges carry only a short desk code, never the pass address. A site can optionally require a private visitor photo, which its authorised team and our platform administrators can see and which can appear on the printed badge. If the site also turns on the photo link in the notice to your host when you sign out, that email carries a private link to the photo: anyone who has the email can open the photo for 2 days, and the link stops sooner if the site turns the setting off, the visit is deleted, or the host’s My vFound link is reset, their email changes or they leave the people list. The photo is never attached to the email. A site can also require a staff member to record that they visually checked a physical photo ID; we keep who checked it and when, but no image or number from the ID. vFound does not verify document authenticity or compare faces, and visitor photos are not sent to vFound AI. If the site’s team pastes or forwards a meeting invite with vFound AI switched on, the AI provider below reads it to suggest the expected visits (names, email addresses, companies, host and time), with links, passcodes, phone numbers and place lines removed first; the team checks each visit before it is created. An invite forwarded by email is kept for up to 30 days. Visit records are never shown publicly: the site’s team and our platform administrators can see them. The visit, its optional photo and its staff check record follow the same 7 to 365 day retention chosen by the site or visitor type. When you sign in, the person you came to see is emailed your name and, if given, your company and reason. A site can also list up to eight more email addresses, and rules by visitor type, weekday and time with their own addresses, to be told of an arrival: those addresses, which the site chooses and need not be its team’s, are emailed your name, the name of the person you came to see, your sign-in time and, if the site chooses, your visit type, your expected time and a note of the site’s own, never your company, reason, answers or contact details. If the site turns it on, your host is also emailed when you sign out, and your host may get an SMS or WhatsApp alert without your name (see the people list above). A Slack, Microsoft Teams or Google Chat channel the site connects is told only the name of the person you came to see.
A site can choose to email you after you sign in and after you sign out, once each, with its own words and, if it adds one, a link it chooses, such as a survey on another website; the words may include your name, your host’s name and the site’s Wi-Fi details, and the after-sign-in words also show on your pass while you are signed in. vFound does not record whether you open that link. A site can also email you reminders 1, 2 or 3 days before your visit. If the site turns on messages, you, your host and the desk can write to each other about your visit from your pass, your host’s My vFound page and the desk while the visit is approved and expected or in: the messages are stored encrypted, the emails that tell you of a new message never contain it, and the messages are deleted 30 days after they were written or with the visit, whichever is sooner. Once the visit is cancelled or not approved, your pass no longer shows them. If a site requires approval of invitations, the invitation waits until an owner or manager approves it, and the guests added to it wait with it. In an Enterprise network, a team member can invite you to more than one of its sites at once: each of those sites then keeps its own copy of your name, email address, company, reason, visit dates and times, language, the team’s note and your host under its own settings and retention.
A school can switch on the school office in vFound Visitors; it is off until a manager does. It then holds, for that site only, pupils’ names, year or class and school reference, the names, relationship and phone numbers of the people allowed to collect them, the school’s own list of people who must not collect a pupil, and each late arrival or early leave with its reason and time; volunteer applications and hours; and staff sign-in times. Only the site’s owners, managers and staff can see it; it is never shown on a kiosk or a public page, and no pupil record is sent to vFound AI. Late arrivals, early leaves, volunteer hours, staff sign-in times and declined volunteer applications are deleted after the retention period the school sets, from 7 to 365 days. Pupil, guardian and approved volunteer records stay until the school removes them, and an owner can delete everything in the school office at once. We do not check any outside registry.
A site can switch on the building features in vFound Visitors. It then holds tenants (the companies in the building), the people from its people list who host each tenant’s visitors, and tenant admins: a name and an email address for each, who sign in with a link emailed to that address and see only their own tenant’s visitors, invitations and blocklist. The site’s owners and managers can keep a blocklist of names and email addresses with a note for the whole building, and each tenant admin can keep one for their own tenant’s visitors. Both are encrypted when stored. A tenant’s entries and notes are shown only on that tenant’s own page, not to the site’s team. A visitor who matches either list waits for the site’s team and is not told why. An entry ends on the date set and is deleted by the nightly clean-up. A tenant admin stays until an owner or manager removes them. If the site turns on the leavers option, a person its directory sync switches off is added to the building blocklist for up to a year, or until they are switched on again. If the site turns on visiting limits, it keeps which people from its people list live in which ward, visible to owners, managers and staff only, and a visitor who is stopped is told only to speak to the front desk.
A site can connect its own Cisco Meraki account (in beta). While a visitor is signed in, their name and their email address, or a made-up address if they gave none, are sent to Meraki to make a guest Wi-Fi login. It ends at Meraki at the end of that day, and vFound takes it away when they sign out, trying again until Meraki confirms it. The login and the Wi-Fi password made for the visitor are stored encrypted, shown only on their own pass and deleted when the login is taken away; the record of what was made is kept for 30 days after. A site can instead connect its own Aruba ClearPass server for guest Wi-Fi (in beta). While a visitor is signed in, their name and their email address, if they gave one, are sent to that server to make a guest Wi-Fi login that ends at the end of that day, and vFound takes it away when they sign out, trying again until the server confirms it. The login and the Wi-Fi password made for the visitor are stored encrypted, shown only on their own pass and deleted when the login is taken away; the record of what was made is kept for 30 days after. A site can also connect Eventbrite: the names, email addresses and companies of one event’s attendees are read so the team can check them before anyone is added. A team member’s questions to Ask vFound about the visitor log are handled as described in section 4, and the visitors it finds are not sent.
A site can also connect its own door system: Kisi, Brivo or Avigilon Alta, or any other system through a signed webhook (each in beta). While a visit is signed in and approved, vFound sends that system the visitor's name, and their email address where the system takes one, to make a pass for the door group the site chose, and takes the pass away when the visit ends. The door system is the site's own account, and the site decides what it keeps. If the door system does not answer, vFound records the pass as unknown and still takes it away when the visit ends. Where the site's keys were changed after a pass was made, vFound cannot confirm that the pass was removed, and the site removes it in its door system. The record of a pass that was taken away is kept for 30 days.
If a site connects its own Salesforce (in beta), vFound sends it the name, email address, company, host and sign-in day of each visitor who signs in with an email address, from the day the connection is turned on. What the site does with that record is the site's own, and erasing a visit in vFound does not erase it there. If a site sends its visitor emails through its own mail server, those emails and their recipient's address pass through that server, which is the site's own. Emails to hosts and staff, emergency messages, sign-in codes and account emails always come from vFound.
If a site lets visitors bring guests, the visitor who was invited can add a guest’s name and, if they choose, an email address from their own pass; the guest did not give us these details themselves. A guest’s name may contain only the letters and punctuation of a name. We email that guest their own pass, or, where the visit type needs approval, nothing until the site approves them, and we tell the host. When the site’s team signs a group in and confirms everyone agreed to the visitor terms, each person’s record says that a team member confirmed it for them. If a site sets a sign-out reminder time, we email a visitor who gave an email address and is still signed in a reminder; when that address was confirmed by an invitation, the reminder links to their pass, and otherwise it has no link. We also email each host a list of their visitors still signed in, with a link that signs one out. A printed badge shows what the site chooses from your visit: your name, company, host, visit type, the date your pass is valid until and your answers to the site’s questions, and it is worn where others can see it. A paired kiosk receives the site’s visitor types, questions and terms, never a people list; after you sign in it is told only whether you are signed in or waiting, your lobby number while you wait, and, if the kiosk prints badges, your badge for two minutes. A screen the site pairs as a lobby screen shows the people waiting for the desk by that day’s number, never their pass code, with a first name and last initial only if the site chooses. If a site turns on the driving licence barcode read, your browser reads only the name from the barcode on the back of a US or Canadian driving licence and fills it in; the picture and the rest of the barcode are not sent to us or kept.
If a site turns on Remember me and you tick it on the visitor sign-in page on your own phone, we keep your name, email address and company, encrypted, and a fingerprint of each version of the visitor terms you agreed to with the date, so the page can fill in your details and not ask you to agree to the same terms again. Whoever opens that site’s sign-in page on that phone sees the saved name, email address and company. A saved agreement counts only when you type the same name and email as before; anyone else reads and agrees to the terms themselves, and is saved only if they tick Remember me themselves, which deletes the earlier person’s details. Remember me is never offered, filled in or saved on a paired kiosk or on a browser signed in to vFound. We keep these details for the site’s visitor retention period, or the shortest period one of its visitor types sets, up to 365 days, counted from your last sign-in with Remember me ticked; opening the page does not extend it. You can delete them early with Forget me on that site’s sign-in page on that phone, by signing in there with Remember me unticked, or by asking the site, whose owners and managers can find and delete them. They are also deleted when the site turns Remember me off or its account is deleted. Your pass says that your details are saved, but cannot delete them.
Blocklist and screening. A site can keep its own blocklist of people and companies, each with an optional last day, and can turn on a check of visitors’ names and companies against the US Consolidated Screening List, the US government’s free export-control and sanctions list. When you sign in or are invited, vFound compares your name, email address and company with the site’s blocklist and with the lists of other sites in its Enterprise network that chose to share entries. If the site turned the government list on, it also compares your name and company with a copy of that list that vFound downloads once a day to its own server; nothing about you is sent to anyone for this. A match is kept with your visit. The team members the site chose, or its owners and managers if it chose nobody, are emailed, and shown a browser alert where those are available, that you matched, and one of the site’s team approves or denies your visit; the government list alone never refuses anyone unless the site chose to hold matching visits for approval. A match on the same words is a possible match, not proof that you are the person listed. You are told only that the front desk will help you. A blocklist entry holds a name, an optional email address and company, and a reason the site writes; the site’s owners and managers can read and change the list, and the team members who decide on a visit can read the reason on that visit. A shared entry shows other sites its name, not its reason. An entry is deleted the night after its last day, and a visit’s matches are deleted with the visit. A site can also set a question so that one answer asks a team member to decide or stops self sign-in; you are only asked to see the front desk. vFound does not search criminal, sex-offender or other paid lists.
If a site turns them on (they start off), a screening alert email to a team member carries buttons to approve or deny the visit. The link works once, for an hour, for one team member who could decide that visit at the time they use it, and is never sent to a person whose site requires single sign-on or two-step sign-in. Anyone who holds that email can use the link while it works.
Emergencies. A site’s team can start an emergency roll call, a drill or a notice. It lists the visitors and contractors signed in and, if the site chooses, everyone on its people list, and records whether each person was marked safe, needs help or is not yet accounted for, when, and which team member did it. The site can send those on the roll call a message its team writes, by email, by a browser alert if you turned alerts on from your pass, and, if you gave a mobile number for emergencies and the site has set up its own SMS or WhatsApp provider (an arranged plan, vFound Enterprise), by SMS or WhatsApp through that provider, which receives your number and the message. Each message has a private link where you can say that you are safe or need help and add a short line; it works only while the roll call is running. On the same page you can write more lines to the team, up to 30 for one roll call, without changing whether you are safe, and read the team’s replies; those lines are kept with the roll call and deleted with it, or when you are anonymised. A team member can also write a hazard alert, a warning the team writes and sends to a group it chooses, such as everyone signed in; it is a roll call of its own kind and works the same way. vFound reads no weather, news or threat feed, so nothing is sent unless a team member sends it, and it never asks a phone to ignore its silent setting. A site can ask for a mobile number on its sign-in page, kiosk, desk or your pass. Giving it is optional. We keep it encrypted, use it only to send you an emergency message, and delete it with your visit; you can remove it yourself from your pass. A site can also show you its evacuation maps on your pass and on the page of an emergency message, through private links that last 12 hours. A finished roll call and its timeline of marks, messages and sweeps are kept for 12 months and then deleted. A team member can also ask for help quietly from the front desk; that alert goes only to team members and shows nothing to visitors.
The visitor directory and your information. A site’s owners and managers can search the people who have visited, read their visit history, keep private notes about them (encrypted, never shown to you), merge records of the same person, list the people signed in at the same time as a person from the sign-in and sign-out times, and anonymise a person. Anonymising removes your name, email address, company, mobile number, answers, reason for visiting, photos, signatures, feedback, saved Remember me details (those the visit points to or saved under your email) and calendar copy from your visits to that site, ends your pass links, removes the logged webhook deliveries about those visits and deletes the notes. It also deletes what else the site holds about those visits: documents you uploaded, signed agreement copies with the name and email you signed with, messages between you, your host and the desk, guest Wi-Fi logins (taken away at the provider first), catering requests, appointments, invitation delivery records, induction records, a courier’s name and company, and your contractor record and its documents, any match made by one of your answers to a screening question, and invitation emails forwarded to the site that contain your email address (one that names you only by name is deleted with the site's other forwarded invitations 30 days after it arrived), and it clears what you wrote during an emergency roll call. The visits stay as “Anonymised visitor” so the site’s counts and times still add up. A match against the site’s blocklist, a building’s blocklist or the screening list is the site’s security record and stays: it keeps the list entry that matched, your name as you typed it and the time, and the site’s team can still see it until the visit passes its retention period. Anonymising does not remove the blocklist entry itself, recall anything already emailed or already received by the site’s own systems, or remove what the site’s own backups hold until they expire. From your pass you can open Your information, download what the site holds about that one visit, cancel it while it is still waiting and erase that visit yourself, with the same effect on your details and the same exceptions, unless you are signed in; sign out first.
A site can also turn on further checks and records for visitors. If it asks for a location check on the visitor sign-in page, your phone asks your permission once, and your position is compared with the site’s and then forgotten: it is not stored or logged, and the visit keeps only whether the phone was near the site, not near it or not checked. A team member can give your visit an RFID card, whose full number we keep only while the card is in use, and afterwards only its last four characters; a returning visitor can be given a fast-track QR on their private pass page, which anyone holding it could use to sign in as that visitor until it runs out or the site takes it back; and a team member can record things handed to you for the visit and, when checking a physical photo ID, the expiry date they read on it. We do not read, store or judge the ID itself. These records go with the visit and are deleted when it is.
If a site enables invitation preregistration, you can use your private visitor pass to provide your company, answers to the site's visitor questions, a visitor photo when requested, and your agreement to the site's current visitor terms before arrival. We keep these details and the completion time with your original visit. If a site enables event signup, we also record which event you registered for, with your name, email address and visit details. A site may publish written visitor induction instructions. If it enables induction acknowledgements, we keep the version you acknowledged, the acknowledgement time and its expiry with your visit. A valid acknowledgement can be reused for repeat arrivals on the same private pass; we do not transfer it to another pass merely because its email address matches. Acknowledgement records what you confirmed reading; it is not a test or certification. The site's authorised team can view these records, subject to the support and provider access described elsewhere in this policy. Anyone you share a private pass with can use its preparation form. Invite-only event signup links may also be forwarded; they do not verify an email identity.
A site can also ask you to upload up to five documents before you arrive (PDF, JPEG or PNG, up to 10 MB each): we keep each file and its original file name (stored encrypted) with your visit; the site’s owners, managers and staff can open them, never its view only members, and each opening is logged; a new upload replaces the old file, and the files are deleted with the visit at the end of its retention period. Where your visit type asks for a signature and the site allows it, you can sign on the same page before you arrive; the signature is kept as if you signed at the desk. If an event is full and keeps a waitlist, we record that you are waiting; when a place opens before the event starts, the earliest person waiting is given it and emailed their pass, or, if the visit needs approval, waits for the site to approve it.
If a site turns on Vaccination record (it starts off), a visitor may choose to send one before a visit. A vaccination record is health information. Nobody is refused for not sending it. At the site, only its owners, managers and staff can open it. vFound does not read it. A photo goes through the picture safety check that runs on vFound's own servers, and nothing is sent to an outside service. It is deleted on the day fixed when it was sent, between 1 and 30 days after (7 by default), whatever the site's setting says later.
Documents to sign, inductions, contractors and permits. If a site uses vFound Visitors documents to sign, it uploads a PDF, and we keep that PDF and a picture of each page in the site’s private uploaded files, on the servers and in the backups described in section 5. Only the site’s team and our platform administrators can open them; you see the pages only while you sign in. When you tick that you read and agree, we keep your name, your email address if you gave one, the time, the exact version you agreed to, whether you did it on the QR sign, a kiosk or with a team member who confirmed it, and a signed copy as a PDF that holds the pages and your drawn signature if the site asked for one. If you gave an email address yourself and the site has not turned it off, the copy is emailed to you as an attachment, and your private pass links to it until 30 days after you sign out. If the site connected a webhook, it receives your name, your email address and a link to the signed copy that works for seven days, so the site can file it in its own storage. The signature record and the signed copy are deleted with the visit, after the same 7 to 365 day retention chosen by the site or visitor type; backups follow section 5. If you tick Remember me, we also keep a fingerprint of each document version you agreed to, with the date, in the details described above.
If a site uses an induction with slides, a video or a quiz, we score the quiz as you answer it and keep, with your visit, the induction’s name and version, your score and the time. We keep each try for seven days as a record that holds a one-way hash made from your name and email address, the score and the time, and not your name, so that the number of tries can be limited. Failed tries are also counted for a day against a one-way hash made from your email address, or from your name and company when you give no email, and from the browser session you used, so that a new name does not give new tries. They are counted for an hour against a one-way hash made from the kiosk or your network address, only to stop a very large number of failed tries. Visitors see the site’s slides and video only on the sign-in page. An induction record is deleted with the visit; the version you took is the site’s own setting and stays until the site removes it.
A site can show a translation of an agreement's text beside the agreement, for reading only, once a team member has saved it as reviewed. The visitor still agrees to the document itself, and the signed copy is the document the site uploaded.
If you work for a contractor company that a site lists, the site or your company (through a page only your company can open, by a link the site gave it) may give us your name and email address and upload documents about you, such as a licence or training certificate, and about your company, such as insurance. We keep each file in the site’s private uploaded files, who uploaded it, what the site’s team decided about it, who decided and when, and the date it runs out, and for an upload from your company’s page, which of its links was used. A picture is saved again and checked before it is kept. A team member checks every document before it counts. If the site has vFound AI switched on and the file is a PDF with text, the lines of that text that hold a word such as expires or valid until, and the line after one that holds only a date, at most thirty lines in all, are sent to the AI provider below to suggest the expiry date. A line that holds a word for a date of birth is not sent, in English or the languages vFound is offered in. A date of birth printed without such a word can still be sent if it sits on a line with an expiry word. A line that is sent holds whatever else is printed on it, such as your name, a licence or policy number or an address; a team member confirms the date. A picture or a scan is never sent to an AI provider; a picture goes only through the automated image check on our own server that section 7 describes. We email your company’s contact before a document runs out. A document that a newer approved one replaces, or that the site’s team turns down, is deleted 30 days after, a page link is deleted 30 days after it ends, and a worker’s or company’s documents are deleted when the site removes them or deletes its account. A document a team member attaches to a visit for a visitor is deleted with the visit. A worker’s sign-in code is kept only as a one-way hash. Contractor time on site is added up from the sign-in and sign-out times of visits linked to the contractor.
If a site uses permits to work, we keep who asked, the work, its place and time, each approver’s decision and note and the time, and email the approvers and the person who asked. They are deleted 400 days after the permit ends.
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.
If a site enables visitor delegation, a host may name up to ten people already on that site’s people list as delegates. We record the host and delegate references, when the delegation was made and, if ended, when and how it ended. A current delegate can use their private My vFound link to see the names and expected or sign-in times of that host’s approved, confirmed visits and send an arrival reply. The page also shows the host’s name and the current arrival reply, but not the visitor’s contact details, company, purpose, photographs or answers. The visit history records the delegate’s name and identifier when they reply. A delegate cannot approve a visitor’s entry. Hosts and delegates can end a delegation, and the site’s owners and managers can end it or switch delegation off. Switching it off ends existing delegations permanently.
If a site enables unanswered-arrival escalation, we keep its waiting-time setting and optional backup-person reference. We show overdue unanswered confirmed arrivals to the site’s authorised team and record who marked an arrival followed up and when. A delegate notice emails the host and site names, the sign-in time and a private link; an escalation email names only the host and site. We keep arrival, delegation and recipient references and notice-attempt status to prevent duplicate attempts. Replies and follow-up stop pending escalation, but a message already being sent cannot be recalled. An interrupted or uncertain attempt is not automatically resent.
If a site turns on staff sign-in (it is off unless an owner or manager turns it on): the people the site adds to its staff list from its people list can sign in and out of work, in the office or working remotely. For each stretch of work we keep the person, the working day on the site’s clock, whether they were in the office or remote, when they signed in and out, how (a paired kiosk, their own My vFound page, a team member at the desk or the site’s API), the name of the device, team member or key that recorded it, and whether we signed them out automatically at the time the site chose. At a kiosk a staff member shows a staff pass QR code, scans a badge or types an ID number that matches only them; the kiosk answers with a first name and last initial and the time, and counts wrong numbers only to slow guessing. The pass QR code is shown on the person’s own private My vFound page and to the site’s owners and managers, and replacing it stops the old one. We do not collect or use location. Every team member can see who is signed in today; only owners and managers can read, export (as timesheets and a hybrid-working report) or delete the history. The site is responsible for having a lawful basis for keeping this record and for telling its staff. A webhook the site connects receives the person’s name, the times and how and by whom the sign-in was recorded, never their email address.
If a site also turns on the presence feed (it is off by default and needs staff sign-in), its own badge reader, time clock, Wi-Fi or identity system can send in and out times for the people on its staff list, kept as ordinary attendance records that follow the site's attendance retention, and muster events that mark a person safe on a running roll call. vFound reads no position, device list or sign-in log itself. The site should tell its staff before it turns this on.
If a site turns on catering requests (off unless an owner or manager turns it on and chooses one inbox), a team member can ask for catering with a visit. We email that inbox the visitor’s name and company if given, the host’s name, the time of the visit, the options chosen from the site’s own list and the number of people. We email it again if the request or the visit time changes, and when the visit is cancelled or refused. Nothing can be typed into a request beyond the options the site lists. The request is kept with the visit. vFound orders nothing and takes no payment.
If a site publishes an appointment page (off unless an owner or manager turns appointment pages on), anyone with the page’s address can see its free times and book one by giving a name, an email address and, if they choose, a company. That makes an expected visit for the host the page is for, or the front desk, and we email the pass as we do for a visit planned on the site’s registration page. The same bot check protects the form (section 4). The page shows its name, the host’s name and the free times only, never who booked the others.
If a site turns on desk, room and parking booking (off unless an owner or manager turns it on), a booking is a reservation of a desk, meeting room or parking space for a person on the site’s people list. We keep the space, the times, the number of people if given, the person’s name and email address, whether it needed approval, its status, how it was made (the person’s own My vFound page, a team member, a visit or the API), whether the person checked in and, if the site chose a release time and nobody checked in, that it was released. We email the person to confirm, request or cancel a booking, and when the site retires a space. A site can keep a desk for one person on chosen weekdays. A meeting room booked for a visit is made for the visit’s host, and the visitor’s private pass names the room, where it is and its start time while the booking is confirmed. A person books, checks in and cancels from their own private My vFound link. The site’s owners and managers see how many bookings, hours, check-ins and releases each kind of space had, with no names.
A site can pair a screen as a reception display, digital signage or a room display (each off unless an owner or manager turns it on). The screen has no sign-in: anyone who can see it sees what it shows. The reception display shows the people on site and those expected today whose visits are approved, shown as counts and times unless the site chooses to show names, and then with a first name and last initial, never a pass code, company, host, purpose, email address or photo. Digital signage shows only messages the site wrote. A room display shows one meeting room’s day: free or in use until a time, and the bookings later today with the booker’s first name and last initial only if the site shows names on its screens. Turning a screen off, revoking its device or retiring the room blanks it at once.
If a visitor type asks for a vehicle registration and its badge design has a parking permit line, the printed badge shows that registration in capitals with the day the pass is valid until and the site’s automatic sign-out time. The registration is kept as your answer to the site’s question, with the visit.
If a site creates visits from calendar invitations: we receive the organizer and attendee names and email addresses, the meeting identifier, sequence and times. We discard the meeting description. The pending invitation details are encrypted in our database. If the sending mail server cannot be verified, no visitor is emailed until the organizer confirms a signed link, and a change to an invitation already confirmed is kept apart, unused, until then.
If you run a site: your name, work email, business name, site code, password (stored only as a hash), team members you add, your chosen workspace language, the address guest replies should go to, and your activity in the workspace (including an audit record of security-relevant actions such as sign-ins, staff changes and claim decisions). Owners and managers can download their site’s audit record for any period we keep it, up to 20,000 events in one file: when, which team member (or vFound support), what happened and which record, never addresses, passwords or guest contact details. When you sign up for a new site, that record also holds the internet (IP) address the sign-up came from and the one your email verification link was opened from, each with an approximate city, region and country derived from it. Only vFound's platform administrators see them; we use them to spot fake or abusive sign-ups. Basis: our legitimate interest in protecting the service.
If you sign up by card: accounts are currently set up by us after a request through the contact form, so this applies only if we switch card sign-up on. Before your card is confirmed, when you send the sign-up form we do not create a sign-in, a site, a site code or an account. We keep a pending sign-up while you are on Stripe’s payment page: your name, email, business name, the products, site code and currency you chose, your password (stored only as a hash), the internet (IP) address and browser the form came from and the language of the page. The personal parts are encrypted in our database, and nobody can sign in with it. When Stripe confirms your card, your account is created from it and the pending sign-up keeps only the link between your Stripe subscription and your site. If no card is confirmed within 24 hours, the pending sign-up is deleted. Basis: steps you asked for before entering a contract.
When a team member signs in or uses the workspace, we record the time (not the page, address or device, except for the counter sign-ins described next) so we can see how sites use vFound, support them and improve the service; only vFound's platform administrators see it. The last sign-in time and the last activity time are kept for as long as the person's account exists, and go when the account is deleted. They belong to the person, so for someone who works at several sites they reflect their activity across all of them.
If a site turns on counter sign-in for Checkroom or the Queue desk, its owners and managers register counter devices and give team members a staff number, a six digit PIN and a QR badge. The PIN is kept only as a one-way hash, the badge code only as a one-way hash, and the staff number while the sign-in is set up. Each counter sign-in records the person, the site, the device, the product (Checkroom or Queue), the method (PIN or badge) and the start and end of the session, and these session records are deleted 90 days after the session ends or expires. The audit log of the site also notes each counter sign-in (person, device, method, time); the site's owners and managers and vFound's platform administrators can read it, and audit entries are kept for 24 months.
If your organisation groups several sites: we keep the group name, the sites and optional region assigned to each one, group members and their group or regional roles, group policy templates, and an audit history of group, access, site and policy changes. Network settings show aggregate operational counts and account health for sites within that person's group and region, and the network page, named after the group, lists the open work of each product open at those sites: item titles, claim status, the title, category and date of open lost reports, parcel recipients and units, checkroom ticket numbers and guest names, equipment and who has it, and visitor and host names, as that site's own team sees them. These lists never include a guest's email address, phone number, borrower reference, checkroom room or message, nor the name, address or photo of the person who reported a loss. A person receives any other record detail only after opening a site they are authorised to use. To answer a request from a guest, a group owner, manager or regional manager can enter that guest’s full email address or phone number to see which of their sites with Lost & Found open hold a lost report, claim or finder record with it; the result shows only the site, the kind of record, its reference and date. The search is recorded in the group’s activity without the address or number.
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 the site’s own lost and found page, including the internet (IP) address it came from and the approximate place derived from it. Matching across a group’s sites is off unless the group’s owner switches it on. While it is on, each open lost report is compared with the found items at the group’s other sites. People in the group who have a role at both sites, within their region, can see what was lost and found, where and when, and the two sites. The matches do not show the reporter’s name, email address, phone number, the address the report came from or any photo; opening a record shows only what the person’s role at that site already shows. Private details recorded on a report or item may be used to order the matches but are not shown in them. A site that leaves the group stops appearing in them at once. While matching across sites is on, a guest whose report is open may also be told, on their private report page and by email, about a found item at another site of the group. This never happens for a report made with a site that keeps its found items private, and never names an item held at one. If the guest claims that item, people with a role at both sites can see that the claim came from that report, and its status. The report’s contact details are not passed between the sites; the guest gives their own details in the claim.
Locations in a group: When a group publishes an organisation page, each site the page lists also shows the group’s name on its own page, with links to the page’s other locations. If the group lists found items, a guest can search the found items of the listed sites from any listed site that shows its own items, and sees possible matches from those items after reporting on the organisation page. These are the items, fields and photographs each site’s own page already shows, with that site’s public label. A site that keeps its found items private is listed as a place to report only, and none of its items appear in these searches or matches. A private report page and the email about a report name the site it was reported to and the group it belongs to. On a group’s organisation page, the same form checks every location that page lists.
The person who runs each site may also get one email a day listing new matches with sites where they have a role: what was lost and found and the two sites, never who lost it. Staff can mark a match as not a match, which hides it for everyone in the group, or send the item to the site of the report; a report is never turned into a claim at another site.
Enterprise service reports contain platform status samples and incident notes, plus aggregate support request counts (from Help & support in the workspace and the contact form while signed in) and first take-up times. We match a request to a group when submitted only if it was sent while signed in to vFound as an active owner or manager of exactly one active group, from that login’s own address. Other requests are excluded. Membership changes do not reassign earlier requests. Messages and contact addresses are not included in the report.
If you contact vFound support: from the contact form while you are not signed in to a workspace, or with the Enterprise topic, we keep your name, email address, organisation, the topic you choose, the number of sites you give, for a trial request the products you choose, and your message as an enquiry record in vFound. With it we keep how you found us, if you choose an answer, and where your visit to our website started: the address of the website that linked to us, without its query or fragment, the first page you opened here, and any campaign tags (utm_source, utm_medium, utm_campaign) or referral code in that page’s address. Your browser holds these in the page’s memory only, not in a cookie or browser storage, and sends them only with the form. We use them to learn how people find vFound. A person on our team answers it by email, from our Google Workspace mailbox (section 4) or from vFound. Each enquiry and each support request has its own reply address at vFound, which our emails about it use: your replies to them, and the replies our team sends from the company mailbox to that address, are kept with the conversation in vFound. We keep its stage and notes our team writes for itself, which are never sent to you. Copies of the conversation, including copies of replies we write in vFound, may be delivered to our company mailbox. If you email someone at vFound directly, we may forward that email into vFound, where it becomes an enquiry record in the same way. Attachments in an enquiry conversation, and attachments our team sends, are passed on by email, up to 10 MB in total; vFound keeps only their names, types and sizes. If you send the contact form on another topic while signed in to a workspace, or use Help & support in the workspace, it becomes a support request for the site you are working in: we keep your sign-in name and email address, the topic, subject and message, and that site, its products and the page you came from (Help & support shows these before you send; the contact form names the site). If you tap Ask the vFound team in the Ask vFound help panel, the request carries your question and the conversation so far, with phone numbers and email addresses removed. Your later messages in the workspace, verified replies to our support email and our replies are kept with the request in vFound’s support records, together with notes our team writes for itself, which are never sent to you. In the workspace, a site’s owners and managers can read all of that site’s requests and other team members see only their own. A reply by email joins the conversation only when it comes from the email address the enquiry or request was sent from, or, for a workspace request, from the current sign-in of its sender who still has access, or an owner or manager of the site. A reply from our company mailbox joins it only when it comes from that mailbox’s own address. We check that the delivering mail server is authorised to send for that address’s domain. When a message reaches a valid ticket address but fails our checks, we send the reason and up to 10,000 characters of plain text, without attachments, only to vFound’s owner notice mailbox for review. It is not added to the ticket thread. The admin ticket shows a count of these held emails; the notice record keeps no sender address or message text. Messages over the daily limit are also held for owner review. Unknown ticket addresses, automatic replies, delivery reports and duplicates are ignored without an email response. We keep each support conversation, with our replies and notes, for 24 months after its last message or change, then delete it together with the record of any held emails (section 6). Enquiries from the contact form, with their stage and notes, are kept for the same period. The metadata of a held forwarded email that creates no enquiry is deleted after 24 months. Copies of enquiry emails in our company mailbox (Google Workspace), with our notices about them and our replies, are kept there until we delete them.
Enterprise sites may define custom attributes on Lost & Found, Parcels, Checkroom, Equipment and Visitors, and workflow checklists for them; Equipment checklists (checking out and taking back) are on every plan. We keep field labels, types, choices and the values staff enter, plus workflow checklist labels, answers, notes, staff identity and completion times. They are available to authorised site staff and platform administrators, and through the private API, configured webhooks and exports. Required fields and checklists never block guests, kiosks or self-service. Values follow their product record retention; orphaned completions are removed nightly. Claim guest erasure removes its completed checklists. Site definitions go with site deletion; group definitions are deleted 24 months after group closure. Enterprise expiry deletes 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.
If a group configures operating policies: we keep the policy name, permanent numbered versions, their rules and service-level targets, site assignments, local exception reasons and optional expiry dates, acknowledgements, aggregate breach counts and alert-notification times. Reports and escalation emails contain counts, policy and site names, not claimant, visitor, parcel or other operational record details. Assignment and escalation notices go to active group owners and managers who are authorised for the affected site; a regional manager receives them only for their region. Replies go to the group manager who performed the assignment or the group owner. These records do not make operational decisions or change payment access.
Items your team logs: photographs, descriptions, storage location, internal notes and return records. Photographs and descriptions your team publishes are public on your guest page and, if your customer group turns it on, the titles and photographs of those items also appear on the group’s organisation page with your site’s public label and in an all-locations search on the group’s guest pages; internal notes and claimant details never are. When sites in one customer group send a found item from one site to another (a terminal desk to a central store, for example), vFound also records both sites, where it was kept and where it goes, an optional note, the times and which team members sent, received or took it back. The item, its photos and its history then belong to the receiving site, and a hotel stay linked at the sending site is removed from it. While it travels it is on neither site’s public page. An item with a claim is never sent, so a guest’s claim stays with the site they claimed from.
Private found items: a site can choose to keep its found items private. Its guest page then lets people report what they lost (and tell the site about something they found, if the site turns that on), but none of its found items, their photographs or possible matches are shown on its guest page, item pages or a group’s organisation page, and no automatic email tells a guest about a match. Its team still compares reports with its found items and writes to the guest. An item the team chooses to share with one guest, for example by starting a claim from their report, is shown to that guest only.
If your site uses email to inventory: each site has a private address that its own team can email or forward photos to. Only mail that a team member’s own mail system really sent is accepted; mail from anyone else is dropped and not kept. For each accepted photo we keep a draft with the photo (saved again without the location or other details the phone added), the sender’s email address, the subject and the first 500 characters of the message, until someone logs or discards it. The photo file is deleted as soon as the draft is logged or discarded, and with vFound AI on, the AI provider below reads the photo to suggest a description. Every draft, with its sender, subject and note, is deleted 30 days after it arrived, whether or not it was logged.
If a site connects its people directory: we receive the name, email, room or department, reference, language, active status and external identifier the site sends. A CSV link is encrypted in our database; we also keep its host, sync mode, last run time and row counts. Automatic provisioning creates people-list entries only, never staff accounts. If a site lets borrowers open its Equipment catalogue through the site's own identity provider, we receive the email that provider confirms, use it only to find the one active person on the site's people list with that email, and record the sign-in in the site's audit log; it never creates or opens a staff login. A site can also upload its student information system's OneRoster export: we read only the teachers and staff in it, and its students only if the site ticks that option, never parents, guardians or relatives; we keep the same fields for each person and, only if the site asks, each class as a borrower type with the people enrolled in it, which starts see-only; nothing is sent back. If a school connects its OneRoster service (in beta), vFound reads staff names and email addresses (students only if the school chooses) and, for the school office, pupils' names, classes and the system's own IDs. It reads nothing about parents or guardians and writes nothing back. A person's signed My vFound link shows the parcel, visitor-host and equipment records linked to that person. If the site enables its private Equipment catalogue, the link also lets its holder browse that site's equipment names, categories and photographs and request individual items, category quantities or a saved kit for selected dates. We link the request to the existing borrower record and keep its selected equipment, dates, group membership and approval status with the site's Equipment reservations. An availability preview does not reserve equipment. Anyone holding the current link can open it, so keep it private. Each link works for 60 days, and each new service email carries a fresh one. Earlier links stop working when the person’s email changes, when they are deactivated or removed, or when an owner or manager resets their link. A site’s owners and managers see each person’s full email address; other team members see it masked. Deactivation also stops new records from being assigned to that person. It does not erase open operational records; owners and managers can review their counts until the site resolves them.
If the site enables equipment specifications, its team can write technical descriptions for borrowers to read in the private equipment catalogue. Staff should not put personal information, internal notes, item values or serial numbers in those descriptions. If the site separately enables reservation history and change requests, the holder of your current private My vFound link can view your reservation or group, recorded status changes and requested changes. We record proposed dates, equipment quantities, an optional note of up to 1,000 characters, the request time, and the staff decision and time with the reservation. Authorised site staff can review these records; platform support access, hosting, service providers and backups follow the arrangements described elsewhere in this policy. A request does not itself change or approve the booking. Staff may accept or decline it; acceptance checks availability and booking rules again. Do not include identity documents, payment details or sensitive personal information in a note. No attachments are accepted.
Card validation and payments: when you pay by card, Stripe validates the card and handles the payment. Where we invoice you instead, no card is involved. We store the customer, Checkout and subscription or payment references, amounts and status, not your full card number. A site may record that it collected a Checkroom fee, deposit, tip or late fee as cash or through its own external POS or card terminal, but vFound receives no guest payment or card details.
Technical: application logs of errors and events, which can include an IP address and the page requested, kept to keep the service running and secure. Our web server keeps no access log. To notice an email link that stops working, we keep a count per day of how each kind of link in our emails ended (opened, ended or not found), with no address, token, IP address or person attached, for 90 days. When someone arrives at a page of our public website from an AI assistant (such as ChatGPT, Perplexity, Claude, Gemini or Copilot), we add one to a count for that day, that assistant and the page, with no address, cookie, browser details or person attached, for 13 months. This count does not wait for analytics consent because it records nothing about you. A paired kiosk (for visitor sign-in, parcel arrivals, equipment self check-out and return, or checkroom self check-in) keeps a random, encrypted token in an essential cookie and we keep its site, device name, permitted actions and last-seen time. The kiosk never stores a people list in the browser.
If you turn on browser alerts: the browser’s push address, public encryption key and authentication token, its stated expiry (if any), recent delivery result, and the account, pass, ticket or service-email record that authorised it. The address and keys are encrypted in our database. We do not receive a device identifier, contact list or the other sites you visit.
If a site enables private Checkroom ticket conversations, we store message text, whether it came from the guest or desk, and its sending time, linked to the site and ticket. Anyone holding the private ticket link can read retained messages while the feature and site’s Checkroom access remain available, and can send messages while the ticket is pending, checked in or left behind. Authorised site members can read messages; owners, managers and staff can reply. Existing platform support and service-provider access arrangements apply. Message text is encrypted in the application database. Messages stop appearing after 30 days and are deleted by routine pruning, or when the ticket or site is deleted sooner. Turning conversations off hides retained messages and prevents new messages; it does not immediately erase them. Existing backup retention applies. For checked-in or left-behind tickets, staff can request an email containing a private-ticket link without conversation text. Replies go to the site’s configured reply address and are not automatically added to the conversation. Do not send identity documents, payment details or sensitive personal information. Keep the ticket link private.
Accepted-terms copies are on unless the site turns them off; an existing saved off choice is preserved. Your current eligible private visitor pass can show a printable copy of the visitor terms stored as accepted for that visit, their SHA-256 digest and recorded acceptance time. This uses the stored text, not the site's replacement terms. Anyone holding the private pass link may access the copy while access remains available. Access ends when the relevant option is disabled, the link is revoked or expires, the site or Visitors access is unavailable, or the visit is deleted. A copy you print or save remains under your control.
If your site enables visitor feedback, you may choose to give one rating from 1 to 5 and an optional comment of up to 1000 characters linked to your visit record after signing out, including between sessions on a recurring pass. Feedback does not affect entry or approval. Authorised site members with access to visit records and vFound platform administrators operating or supporting the service may read the response. Existing service-provider and backup access described in this policy also applies. Do not include identity documents, payment details or sensitive personal information. A feedback invitation email is sent only when the site allows it and you request one through your private pass, using the email address and pass token present when you requested it. Changing either clears the active email choice and requires a new request. The email contains the site name and a private feedback and preferences link, not your response. You may turn that email choice off before sending starts or opt out of feedback for that visit. A message already being sent cannot be recalled.
If you take a number at a site that uses vFound Queue: the ticket records its number, the line and service, the counter, when you joined, were called, were served or left, and the team member who served you. When you join from your phone or a kiosk, the line decides whether you give your name, only your initials or neither, and whether it asks for a party size, an email address and answers to its questions (up to 10). When the site's team adds you at the desk, or a system the site connects does it through vFound's API, it can type a name, a party size and a short note itself, and mark you as a priority, whatever the line asks of you. Your email address, your answers and the link to your ticket are stored encrypted. Your ticket is a private page whose long random address is the only key to it, apart from the view-only link you may make to share your place (described below). If you give an email address and the site sends email, vFound emails you your ticket link, tells you when you are nearly up (if you joined before arriving), when you are called and when the team writes to you, with replies going to the site. If you turn on browser alerts, the browser's address for sending them is deleted when your ticket ends or, for a no-show, when the site's day ends, because the team can undo a no-show on the same day. If the site has set up its own SMS or WhatsApp provider (an arranged plan, vFound Enterprise) and you choose text or WhatsApp, your number is kept encrypted (your choice and the time you gave it are kept beside it) and your number goes to that provider. The waiting-room screen shows ticket numbers and counters, never a guest's name (a site can also show the first name of the team member at a counter, as described above). The site's authorised team and our platform administrators can see queue records. If the site connects its own systems through vFound's API or webhooks, they receive the ticket's number, line, name, party size and note; a logged copy of a webhook is deleted when the ticket's details are cleared (section 6) and in any case after 30 days. A team overview across the sites of one organisation shows ticket numbers, lines, services, counters, status and times, with no name, email address or answer. The ticket file a site downloads lists numbers, lines, services, counters, times, party size and the team member who served, with no guest name, email address or answers. The site's owners and managers can also build a report that includes the name you gave, and download it or send it by email.
A site can also turn on more for Queue, each off until it does. Booked times keep your name or initials, party size, the time you booked, your email address, your answers, a private link to your booking and a coded form of your email address that finds a second booking by you on the same day; the email address, answers and link are stored encrypted. If the site sends email, vFound emails you the booking link and tells you when the team cancels it, with replies going to the site. A team member can make a private calendar link of booked times that shows initials, the line and the time, never an email address. Messages let you and the team write short text messages (up to 500 characters) from your ticket page, stored encrypted; the email or browser alert that tells you of one never contains it. A short survey after you are served keeps a rating from 1 to 5 with your ticket, and, once the site's period for the ticket has passed (section 6), without anything that names you, and an optional comment, stored encrypted. If you tick "Remember that I have been here" with your email address, the site keeps a coded form of it made with a key that is different for each site, so it cannot be matched at another site, how many days you visited and your last two visits, never your name, email address or phone number; you can delete it from your ticket page. Wait targets and alerts to the team carry line names, counts and minutes only, with no name or ticket.
More that a site can turn on for Queue, each off until it does. Booked times: a reminder goes by email to the address you gave when you booked, once for each reminder time the site chose and not for a time booked after it; the record that a reminder was sent holds no name or address. If a booking page has its waiting list on, you can leave your email address and name for a day with no free time; the site may email you once if a time that day is cancelled, someone else may book it first, your details are cleared when you book and deleted two days after that day, and "Stop emailing me about this day" deletes them at once. A booking can name the team member you booked with, and a team member can print a day's booked times with names as the line asks for them, never an email address, link or answer. The team can also put coloured labels on your ticket, finish a visit with an outcome from the site's own list and quote you a wait; only the team sees them, and they are deleted with the ticket's numbers 13 months after it ends. Messages and alerts: if the site turns on a follow-up message and you tick the box on the join page, you get one message after your visit, by text if you chose text alerts and otherwise by email, with a link the site chose, and never a second. If a site pauses every line at once, each person waiting is told once through the alert they chose: a browser alert, the email they gave, or a text message where the site has vFound Enterprise and its own provider and you chose it, or a WhatsApp message only where the site has also added a template for this notice (otherwise it is not sent by WhatsApp). If a site uses its own SMS provider (vFound Enterprise) and turns on joining by text, a text with the site's chosen word to its number gives you a place and one text back with your ticket page, and you can reply 1 if you are coming or 2 to leave the line; the history of the ticket records the reply and nothing is sent back. If a site turns on showing team messages in your language, the team's own words in a message to you, and nothing else, are sent to Amazon Bedrock to be translated; you see the translation marked as automatic with the original under it. The join form: a line's questions can ask for an email address, a phone number, a number or several choices from a list, and a line can show up to four consent boxes the site worded; each box you tick is kept with your ticket (or booked time) with the words you saw and the time, is cleared with your other details and is listed in the ticket file a site downloads. A line can give one place at a time for each email address or phone number; we compare the contact you give only with the live places of that line, and store nothing more for it. A line can need an invitation link the team made: each works once, for one person, and is stored only as a hash. A site can show a line's join form on its own website with a script tag: only the websites the line lists may frame it, it keeps the same bot check and opening it sets or clears no sign-in or language cookie. From your ticket page you can tell the team you are on your way or running late (a note for the desk that never changes your place) and, where the line offers it, share a link that shows where your place is in line and nothing else; a new link stops the old one, and the link's stored code is cleared with the ticket's details. The block list: a site can add a phone number or an email address to a block list for 1 to 365 days (30 unless it changes that). Only a coded form made with a key that is different for each site is kept, so the number or address cannot be read back, a short label the team types is kept with it and is hidden from view-only team members, and the entry is deleted when its days end. When you join from your own phone, the email address and the number you gave for phone alerts are checked against the list and nothing is stored for that check. The waiting-room screen can show the first name of the team member at a counter, only where the site turned that on for that counter, and can rotate short announcements the site wrote; it never shows a guest's name. Analytics: a site can enter its own Google Analytics measurement id for the join page and the ticket page. They then ask you first and nothing from Google loads until you allow it; once you do, Google may set its own analytics cookies, receives your network address when your browser contacts it, and the page view and the events Google adds carry no join key and no ticket link in the address. It is never offered where a deployment keeps data strictly in its own country. A site's own systems: a site's own website can take a number for you through the site's API key, under the same rules as joining yourself; a test key writes only labelled test tickets with no email address, which are deleted with the key and after seven days. Reports: counts of what people chose for a line's list and tick box questions are shown to owners and managers only, never for a choice made by fewer than 5 people, written answers are never read, and a team member's survey average shows only from 5 answers.
Optional public website analytics
If you accept analytics on our public marketing website, Google Analytics receives the public page path, language, broad traffic and device information, an analytics cookie identifier and clicks on trial and demo links. Google receives your network address when your browser contacts it. We strip URL query strings and fragments, send only the origin of the referring website, and send no form answers, names, emails, account IDs or private record links. Analytics is excluded from signed-in pages, guest websites, registration, claims, guest passes, kiosks and administration. A trial-link click measures interest, not a completed signup or a paid subscription.
Ask vFound on our public website
If you type a question into Ask vFound, the AI assistant on our public marketing website, we keep the question (with email addresses and phone numbers removed), whether it was answered, the page you asked it on and the pages the answer pointed to, for 90 days, to improve our pages, and then delete it. We keep no network address, cookie or other identifier with it, and the assistant adds no cookie. Please do not type personal details into it. To answer, the question, up to four earlier turns of the same conversation (which your browser keeps only while the page is open) and the parts of our published pages that match it are sent to our AI provider (section 4). The assistant answers only from vFound’s published pages and cannot see any account, site or person’s records. Before your first question, Cloudflare Turnstile checks that a person is asking (section 4), and a one-way hash of your network address is kept for at most a day to limit how many questions can be asked. The assistant is AI and can be wrong: the pages it links to are what we publish.
When a site records who handed in a found item, we keep the name, email, phone, affiliation and request for an unclaimed-item notice that its team enters, with the receiving team member and time. These details are available to the authorised site team and platform administrators supporting the site, and are never shown on public item pages. Staff can send a hand-in receipt or an unclaimed-item notice to the supplied email address; no unclaimed-item notice is sent automatically. Owners and managers can erase the finder’s contact details and notice preference while keeping a history entry without those values. Details otherwise remain with the item until the item or site data is deleted; protected backup copies age out under the existing backup periods. When sites in one customer group send a found item from one site to another, the finder’s details recorded with it go with the item. At the receiving site they are available to its authorised team and platform administrators supporting it, can be erased by its owners and managers, and are kept and deleted under that site’s rules. Between sites that are not in the same customer group, items are never sent. Erasing finder or claimant personal details also replaces the site’s stored retry responses with an empty-data refusal, including responses containing identification-check notes. Staff-contact and finder emails share limits of 50 per site and 3 per recipient address per site-day, including confirmed resends. Coded recipient, date and count records enforce these limits even after an item or claim is deleted; they contain no email address and remain until site data is deleted. Unclaimed-item notices are checked again before sending and dropped if the preference, address, site or unclaimed holding state no longer permits them. Queued staff-contact and finder emails are dropped if their reserved site-day has ended.
A site’s team can enter a possible owner’s name and email to open a private claim and send that person an invitation to discuss collection, including for an item whose photo is private. This is a possible match, not a decision about ownership. The claim follows the existing claim access, correction, deletion and retention rules. At handover, staff may record the type of identification they checked and a short note; they are instructed not to enter identification numbers. Release receipts show the identification type, the handover and any recorded pickup signature or shipment tracking, but exclude finder contact details, internal item notes and the identification-check note.
3. Why we use it, and our legal basis
- To provide the service: publishing items, routing claims, sending service email, taking payment. Basis: performance of a contract.
- To keep it secure: bot protection, rate limiting, fraud and abuse detection, audit logs, backups. Basis: legitimate interests in protecting our service, our customers’ sites and their guests.
- To help a site assess a claim or a lost-item report: including the submitting IP address and approximate city, region and country. Basis: the site’s legitimate interest in not handing property to the wrong person.
- To meet legal duties: accounting and responding to lawful requests. Basis: legal obligation.
- To answer questions asked in Ask vFound on our public website and improve our pages. Basis: legitimate interests in answering questions about vFound.
- To answer your enquiries. Basis: legitimate interests, or consent where you gave it.
- To learn how people find vFound, from where an enquiry’s visit started and how you say you found us. Basis: legitimate interests.
- To send optional browser alerts you request. Basis: your consent, which you withdraw by turning them off on that device. Email continues independently.
We do not carry out facial recognition or biometric identification, and we never identify a person from an image. When a site uses vFound AI, it compares descriptions and photos of items, never of people, to suggest possible matches and to help staff check a claim. These are suggestions only: we make no decisions about you by automated means that produce legal or similarly significant effects, and a person at the site decides every claim. 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. The suggestions themselves are kept so the team can see them again: item descriptions and search words, match verdicts for lost reports, claim checks, weekly insights and the wording of the daily summary. See section 6 for how long.
To improve our public website and understand demand: optional analytics uses your consent. Rejecting it does not affect the service. You can withdraw through Analytics preferences on a public page.
4. Who we share it with
Your claim is visible to authorised staff at the site handling your item, and to our platform administrators who operate and support vFound. If the site connects other services, such as Slack, Microsoft Teams, Google Chat or its own systems through our API and webhooks, the details that service receives go there on the site’s instruction. A member of the site’s team can also add a private calendar link to the calendar app they choose; that app then reads upcoming visits, equipment due times, luggage collection times and booked pickups, including the names shown with them. An owner or manager of the site can also make a report data feed link, which a reporting tool such as Power BI reads without signing in, and can have a saved report emailed to members of the site’s team with a CSV file attached. Both can include the names shown with the records; email addresses and a checkroom guest’s name and room go only to owners and managers, and into a feed only when the link was made to include them. A directory, published CSV or hotel property system a site connects is chosen and controlled by that site; it is not our service provider. Property-system, coworking-member and organisation-directory connections (including the beta LDAP or Active Directory and Google Workspace connections) store their credentials and settings encrypted and read only the minimal stay or member context described below. The same is true of an AI assistant a site owner or manager connects to vFound by signing in (for example through its connector for our MCP server): it receives the records its tools return, only within the permissions the site chose and for the products the site has open, and its provider handles them under the site’s own agreement with it. We keep a record of each connection (the assistant’s name, the address it returns to, who connected it and when it was allowed, renewed and disconnected) and store only fingerprints of its codes and tokens. Beyond that we share data only with the providers below, for the purposes shown:
- OVHcloud: hosting of the application, database and uploaded files, in Singapore. Photos a site’s team emails to vFound, and replies to our support and enquiry emails, arrive at our own mail server on this hosting.
- US Department of Commerce (trade.gov): if a site turns on the screening list check, our server downloads the government’s public Consolidated Screening List from it once a day. The request carries no visitor data, and the checking happens on our own server.
- Resend: sends our service email, such as claim, parcel, visitor, account and support emails, 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.
- Stripe: when you pay by card, card validation, vFound subscription payments, payment contact details and receipts. We store payment references and status, not full card numbers.
- Cloudflare: Turnstile bot protection on every public form that asks for it: tenant page sign-in link, visits page for visitors, volunteer application, sign-in, registration, password reset, contact, claims, claim and report lookup, lost reports, photo search, found-item messages, the lost-item chat, checkroom self check-in, checkroom ticket lookup, visitor self sign-in, visitor registration and appointment booking, the luggage reservation form, the under-18 form, the event reply form, the website assistant, the queue join form, the queue booked-times form, the queue booked-times waiting list form and the library card sign-in form.
- Google Analytics: only where a site enters its 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: converting the IP address a claim, a lost-item report sent from a site’s lost and found page or a new site sign-up came from into an approximate city, region and country. Private and internal addresses are never sent.
- Amazon Web Services (Amazon Web Services Canada, Inc.): Amazon Bedrock, which runs Claude, an AI model made by Anthropic, used when a site keeps AI assistance switched on: to read a found item's photo and suggest its details and search words; to read a parcel's label photo and suggest who it is for, the carrier and the tracking number; to suggest a name for equipment a site adds, from its photo; to compare the photo taken when equipment went out with the photo taken when it came back, to read a serial number from a photo of its label, to draft a check list from an item's name and kind, and to read 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); to compare what a guest describes, and any photo they choose to add, with found items to rank possible matches, when they report a loss and again when the site logs a new item or looks for matches to their report; to help the site's team check a claim against their record of the item, including its private description and internal notes, and any proof photos the claimant uploaded; to translate messages between guests and the team (in Queue, only the team's own words in a message to a person in line, when the site turns that on) and draft the team's replies; to draft, only when an owner asks, a translation of the agreement text, questions, answer choices and kiosk screen wording a site wrote for its visitors (only that text is sent, never a visitor's answers or details); and to turn a guest's lost item chat into a report; to turn what a team member types in Ask vFound into a suggested action (phone numbers are removed first, and the records it finds are never sent); to answer a team member's question in the Ask vFound help panel from vFound's own guides to the products the site has (Lost & Found, Equipment, Visitors and Checkroom): the question, the conversation so far, the sections of those guides that match it and, at a site with Lost & Found, its Lost & Found settings, and the site's plan, open products and the person's role are sent (phone numbers and email addresses are removed first); no guest, claim, lost report or item record, and no vFound source code, configuration or secret, is ever sent; and, every night, to group the questions the panel could not answer (with names and contact details removed), check them against the guide and write short answer pages for the guide; to tell whether a photo taken with the workspace camera shows a found item or a parcel label and read it (QR codes and barcodes are read on the device and not sent); to answer a question a visitor asks Ask vFound on our public website from vFound’s published pages only: the question, up to four earlier turns of that conversation and the parts of our pages that match it are sent (email addresses and phone numbers are removed first), and nothing about any account, site or person; to read a meeting invite the site pastes or forwards and suggest the expected visits; to compare a description of a checkroom item with that night's item photos and item types, never ticket notes or a guest's name, email address or room; to cut a photo that shows several items into one photo per item; to compare a newly logged item's photo and description with up to three earlier items to flag a possible duplicate; to word the daily summary on the workspace home page and the checkroom's end of night summary, from counts only, never names. 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 the site's owners and managers unless the site switches 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. A guest's search photo is used for that one search and not kept by vFound; a photo a guest adds to a lost report is kept with the report, as described above. Photos of items already flagged as showing personal details (an ID, a card, a lit screen) 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: the AI is only told that an answer was given. Proof photos a claimant uploads are the exception: when AI is on for the site they are sent as supplied, because nothing can tell what they show first, so please do not upload identity documents or cards. The lost item chat never asks for a guest's name or contact details, and the form that collects them is not sent to the AI. AI suggestions never decide a claim: the site's team makes every decision. Amazon Web Services runs the request in Sydney and Melbourne, Australia, and sends the answer back. 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. Sites can switch AI off at any time.
- 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, armaan@vfound.io, which receives the messages and requests people send us, and our own notices about site accounts: sign-ups, trials, payments, cancellations and closures, and when a private walkthrough is opened, played or finished: the walkthrough and the name of the person or organisation it was prepared for, the time, the type of device and, if you pressed Allow, how far it was played. These emails stay in that mailbox until we delete them.
- IndexNow (used by Bing and other search engines): the addresses of our public pages and guest pages listed in our sitemap, when they are new or changed, so search engines find them sooner. Only those public addresses are sent, nothing from private records.
We may also disclose data where the law requires it, to protect our rights or someone’s safety, or to a buyer as part of a merger or sale of assets (you would be told beforehand). We never sell personal information.
Customer-configured CRM destinations: Selected webhook events may be sent to systems a site chooses, such as its CRM. Extra report contacts are sent only after a separate explicit choice, and the source record and transport are checked again before each send. 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.
Google Analytics: consented public marketing measurements only, under Google's analytics processing terms. Advertising personalisation, Google signals and user-provided data collection are disabled. Google may process this information in the United States and other countries. It is separate from the records we process for a site under our DPA.
5. Where your data is held
Our application, database and uploaded files are hosted by OVHcloud in Singapore. An encrypted copy of our backups is kept in Canada, where we are based. Our AI provider processes data in Australia. Our payment, bot protection, email delivery and support email providers may process data in the United States and elsewhere. When a site keeps AI assistance on, the photo or text being read is sent to Australia for that, from wherever the site or guest is, and Australian law applies to it there. Where personal data is transferred out of the EEA or the UK, we rely on an adequacy decision where one applies (such as for Canada), or on Standard Contractual Clauses (with the UK Addendum where relevant) together with appropriate safeguards.
6. How long we keep it
- Items and claims: for as long as the site keeps them, under the retention and disposal policy the site sets. Items expire from public view on the site’s schedule. A site can delete a guest’s details from a finished claim at any time. The record of a found item sent between sites is kept with the item and deleted with it.
- Support conversations: an enquiry from the contact form (with its stage, how you found us and where your visit started) or a request from Help & support in the workspace, every later message, our replies and our team's notes are kept for 24 months after the conversation's last message or change, then deleted, together with the record of any emails held for review. Enterprise service reports count only requests that are still kept.
- Parcels: while a parcel waits, and for 12 months after it is collected or returned; then the record, its label photo, pickup photo and any signatures are deleted. Wrong-recipient reports and parcel-notice scheduling and attempt records are kept with the parcel while it waits and for 12 months after collection or return, then deleted with it, or sooner when the site's data is deleted. Unresolved waiting parcels keep these operational records. Site notice-hour and recipient-reporting settings remain until site deletion. Setting-change security audit records follow the existing audit retention period. Copies in backups follow the existing backup retention period. Finished outgoing parcels follow the same 12-month period. Expired delegate codes and served desk-arrival rows are deleted after 30 days. A site can remove a person from its list at any time, which also removes their name from parcels already collected or returned.
- People and directory settings: a site keeps people until it removes or deactivates them. Connected-directory details and people-list entries are deleted with the site account after the 90-day closure period. Removing or deactivating a person, changing their email or resetting their link immediately invalidates their earlier My vFound links, and each link expires after 60 days. Open parcels, equipment checkouts, reservations and visitor records keep their normal retention periods and remain available to the authorised site team for resolution.
- Queue tickets: the name or initials, email address, answers, note and any phone consent of a ticket are deleted the number of days after it ends that the site chooses, from 1 to 365 (30 unless the site changes it); the browser alert is deleted when the ticket ends, or for a no-show when the site's day ends. A copy of the ticket sent to a webhook the site connects is removed from the delivery log at the same time (the log keeps nothing longer than 30 days). Messages on the ticket and a survey comment are deleted at the same time. The ticket number, line, service, counter, times, party size, priority, the team member who served, the ticket's history and a survey rating, none of which holds a guest's name, email address or answer, are kept for the site's reports until 13 months after the ticket ends, then deleted. A booked time's name, email address, the coded form of the email address, answers and link are cleared the same number of days after the booked time and the booking itself is deleted 13 months after it; a private calendar link nobody has read for 180 days is deleted. A remembered-visitor record is deleted the same number of days after the person's last visit, and all of them at once if the site turns the feature off. Records of a wait alert that cleared more than 13 months ago are deleted. 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, and every Queue record goes with the site when it is deleted.
- Checkroom tickets: deleted, with their piece records, hand-back proofs, photo and any signatures, 90 days after all the things are handed back; a ticket left at closing is kept 12 months from that closing. A self check-in nobody handed anything over for is deleted, with any photo, when the team ends the night or after two days. An event is deleted 12 months after it ends once no ticket refers to it. Station names, number ranges and storage locations stay until the site deletes them or closes its account. A guest's face photo is deleted when everything is handed back or moved to lost and found, and otherwise with its ticket; a PIN when the ticket is finished; a link for typing your own details, and anything typed that was not added to a ticket, one day after it was opened; share links with their ticket; a counter screen's ticket link one day after it was shown, or sooner with its ticket. Where things have been, tasks, a pickup time, the keyed hash of the email given at check-in and pickup approval requests are deleted with their ticket; a new ticket link that removes the ticket’s contact details also removes that hash. A team member’s queue status stays until it changes, the site turns its To fetch list off or the site closes its account. The payments recorded for a ticket, the terms you accepted, planned and sent reminders, a disposal record and a survey answer are deleted with the ticket. A shift and its cash drops are deleted 12 months after the shift was opened. Hanger tags, item kinds and counter screens stay until the site removes them or closes its account.
- Checkroom for hotels and events: 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. An event guest list, with the ticket type and any seat or table label, and the event's RSVP answers are deleted 14 days after the event ends, or when the team clears or deletes them. An under-18 form is deleted 30 days after it is sent. A member of a site's member list is deleted 13 months after the member was last added, changed or checked in at the desk, or when the team erases them. All of it is deleted with the site's account.
- Luggage reservations: deleted 30 days after the end of the reserved time window, whether you came, cancelled or did not come. Time windows nobody reserved are deleted 30 days after they end.
- Equipment: while the item is out, and for 13 months after it comes back or is marked lost; then the record, any photo taken as it went out or on its return, the terms accepted for it and any signature are deleted. Collected or cancelled reservations and completed stock-takes, with any borrower confirmations given for them, are also deleted after 13 months. Saved scan positions are deleted after 90 days, and a team member's record that they agreed to them 13 months after they withdraw it or leave the site. A person's 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 their site, custody, location, status and note history, are deleted after 24 months. The items a site hands out, with their photos, asset details and maintenance history, stay until the site closes its account.
Reservation change requests and recorded status history are deleted with their related reservation. Collected or cancelled reservations are removed after 13 months without an update. Removing the borrower from the site’s people list deletes their change requests and recorded reservation history sooner; site deletion also removes them. Turning the feature off hides these records but does not erase them. Copies in protected backups follow the existing 30-day backup retention.
A stock hand-out is kept while anything from it is still out, and for 13 months after the last of it is back or written off; then it is deleted. The stock history (each change to a count, with the team member who made it and any note they add) and finished or cancelled purchase orders are deleted after 24 months. Suppliers and their contact details stay until the site changes or clears them or closes its account.
A training record is deleted 13 months after it expires, with any proof scan; one with no expiry stays while you are on the site's people list. A hold is deleted 13 months after it ends, and a hand-over request or a clearance certificate 13 months after it was made. Removing you from the people list deletes your trainings, borrower types, holds and hand-over requests at once; a clearance certificate keeps the name it was issued for until its own 13 months pass.
A place on a waiting list is deleted 13 months after it ends. Your answers to a risk assessment and the approvals signed on a booking are deleted with the booking, 13 months after it ends. Removing you from the people list deletes your waiting-list places, saved items, calendar address and risk-assessment answers at once, and a calendar address nobody has read for 180 days is deleted.
A ticket sent to a site's own ticketing system is deleted 13 months after it closed or, if it has not closed (it is still open, waiting or failed), 13 months after it was sent to that system, or after it was raised if it never was, and at once if the connection is removed. A course, its platform and its signing key are deleted when the site removes them or closes its account; the people a roster matched keep the training until it is removed or expires. Device records stay on the item until it is deleted, and a removed connection's credentials are deleted with it.
Equipment help desk tickets, including the name of the person who asked and the team's notes, are kept until 13 months after the ticket is resolved, then deleted. For documents and packages tracked in Equipment, vFound keeps the record of each hand-over (the names, the place, the time and the drawn signature of the person who took it) until 13 months after delivery, or after its last change if it was never delivered, then deletes it with the signature images. When a person is removed from a site's people list, their name and signature are removed from document custody trails, including where the next step records who gave it on, and the help desk tickets they asked are deleted. Names typed by hand, without choosing a person from the list, are not linked to a person and are not changed.
- Hotel stays: a stay with no linked item or parcel is deleted 13 months after its last known date (its departure, or if it has none its arrival, or if it has none the time it was last updated), whether or not the source ever marked it departed or cancelled. If an item or parcel still refers to it, its minimal context follows that record and is removed after the record no longer needs it. All remaining stay context is deleted with the site account after the 90-day closure period.
- Visits: the site chooses 7 to 365 days for the site, 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. That period starts when the visit ends (you are signed out, or an invitation is cancelled or not used); then the visit, its optional visitor photo, its staff visual-check record, its sessions, roll-call entries, courier link and any signature are deleted. Calendar invitation details with no visit are deleted after 30 days. Anyone still signed in after the day ends, in the site’s time zone, is signed out automatically once they have been signed in for 12 hours.
- Staff attendance: each stretch of work is deleted after the retention period the site sets, from 30 to 1,095 days with 365 as the default, counted from its working day, whether or not the site still has staff sign-in turned on; sooner when an owner or manager deletes them all, when the person is removed from the site’s people list, or when the site’s account is deleted.
- Catering requests and appointments: a catering request and the booked time of an appointment are deleted with their visit. An appointment page stays until the site removes it or its account is deleted; removing it ends its address at once.
- Desk, room and parking bookings: 13 months after the booking ends or is cancelled; then the reservation and what Visitors keeps about it are deleted. Removing the person from the site’s people list cancels their open bookings and deletes their booking records and any desk kept for them at once.
- Remember me details: kept for the site’s visitor retention period, or the shortest period one of its visitor types sets, up to 365 days, from the last sign-in with Remember me ticked, then deleted; deleted sooner by Forget me, by signing in with it unticked, by the site on your request, when someone else chooses Remember me on that phone, or when the site turns it off.
- Blocklist and screening: a blocklist entry is deleted the night after its last day, or when the site removes it; the matches a visit raised, and a mobile number given for emergencies, are deleted with the visit. The copy of the US Consolidated Screening List is replaced whole each day and holds no visitor data.
- Visitor directory notes: a note about a person, and a merge of two records, are deleted when the person has no visit left at the site, or when the site removes them or anonymises the person.
- Emergency roll calls: an ended roll call, its people, timeline, messages and sweeps are kept for 12 months after it ended, then deleted; the people on it who were visitors are also removed with their visit when its retention period ends. What a person wrote back is deleted when they are anonymised.
- Lost reports: watched for 90 days, then kept with the site’s records. The address a report was sent from, its approximate place and any photo the guest added are kept only as long as the report and are deleted with it, and also when the guest’s details on a claim made from the report are deleted, or when an owner or manager deletes the guest’s details from the report. Alerts (set before 7 October 2026; no new ones are made): 60 days from the day they were set, then deleted 30 days after they end.
- Reports recorded by staff: 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 the site’s data is deleted.
- Found-item messages: deleted 30 days after they arrive if the site’s team does not deal with them, 7 days after the team declines one, and 30 days after the team logs the item. The message’s own copy of the photo is deleted as soon as the team logs the item or declines the message; a logged item keeps its photo like any found item, and none of your contact details.
- Customer groups: active group membership, site-region mappings and policy templates remain while the group is active. Group activity records are deleted after 24 months. Closing a group removes group access immediately; its remaining membership, site mapping, operating-policy versions, assignments, exceptions, acknowledgements and alert and completed equipment-transfer records are deleted 24 months later. A site’s owner can take their site out of a group at any time, which ends group access to it at once. Removing a site from a group stops its policy assignments, exceptions and open alerts. Removing a site or closing the group does not delete that site's account or operational records.
- Matches across sites: kept only while the group has matching switched on. Switching it off, erasing the report or deleting either site removes the stored matches, and they are deleted with the group’s records 24 months after the group closes.
- A card sign-up whose card is never confirmed(only if card sign-up is switched on): a pending sign-up is deleted 24 hours after it was made if Stripe has not confirmed a card by then; no sign-in, site or account was ever created for it. A site created before 15 October 2026 that has not started its trial through Stripe’s payment page 48 hours after sign-up, never opened Checkout and holds no records, is deleted with its sign-in and its audit record (including the sign-up addresses). You can ask us for a trial again at any time.
- After an account is closed: the site’s owners and managers can still sign in for 90 days to download the exports listed in the Data Processing Agreement, or ask us to reopen it. After 90 days we permanently delete the site’s data, except billing records, the site code, which stays reserved so a printed QR sign can never lead to someone else’s site, and the sign-in of an owner who still has another site (kept with this site’s details emptied, and deleted when that other site is deleted); copies in backups are deleted within 30 days after that.
- Billing records: kept as long as applicable Canadian law requires, normally six years.
- Connector sync history: when a site connects a hotel property system or a people directory, the time, outcome, counts and any error message of each sync run are deleted 90 days after the run.
- What vFound AI wrote for the team: item descriptions and search words, match verdicts for lost reports and weekly insights are deleted 13 months after they were written, like the records of AI use; the wording of the daily summary is deleted after 30 days. A claim check is kept with its claim and is deleted when the guest’s details on that claim are deleted or when the site’s data is deleted.
- Notes sent with reminders: 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 questions on our public website: each question (with email addresses and phone numbers removed), whether it was answered and the pages involved are deleted after 90 days. No network address or other identifier is kept with them.
- Ask vFound help panel conversations: what your team types in the help panel and what it answers are kept on vFound’s servers for 30 days and then deleted, or when the site’s data is deleted, whichever is first, and are never emailed. A person can delete their own conversation at any time. A question the panel could not answer, was sent to the vFound team or was asked again within two minutes is also kept for 30 days, with names, email addresses, phone numbers and street addresses removed, so vFound can improve its guide; vFound’s team sees how many such questions there are and a shortened, anonymised version of each question the product cannot answer yet, never a conversation. Guide wording written from such questions is part of vFound’s guide and is kept with it.
- Whether an email was delivered: for each email we send, whether it was delivered, bounced or marked as spam, with the provider’s reason (any email or IP address removed), the recipient’s domain and a one-way hash of the address, never the address itself; deleted 90 days after the email was sent, or sooner with the site’s data.
- Photos emailed to a site’s address: the draft, its sender, subject, note and photo are deleted 30 days after they arrive, logged or not; the photo file goes sooner, as soon as the draft is logged or discarded.
- Logs: the logs our application, PHP and mail server write 7 days (the server’s system journal, which records service start and stop messages, is kept by the operating system under its own limits and is not part of that 7 days); the audit record of security-relevant actions 24 months (including the sign-up addresses described in section 2); records of AI use 13 months; meeting invites forwarded to vFound Visitors 30 days; encrypted copies of the webhook deliveries a site sends to its own systems 30 days; answers kept so an API request can be retried safely 24 hours; background tasks that could not finish, with the details they were working on, 30 days; the record of an AI assistant connection 90 days after it is disconnected; error reports 90 days after the error was last seen. An error report records a fault in vFound itself (on our server or in vFound’s own code in a browser): its type, where in our code it happened, the page’s address with any record numbers removed, and how often it happened. Before a report is stored, email addresses, numbers, codes and any quoted text are removed from its error message, and a database error keeps only the database’s reason, not the values being saved. It does not read what was submitted or your account. A report sent by a browser is counted against its sender’s address for 24 hours, so one sender cannot flood the reports; that count is kept under a keyed one-way hash and the address itself is never stored with a report. A plain-language reading of each new report, from the same AI providers named in section 4, is added for the owner. A private calendar link stops working when its owner replaces or removes it or leaves the team, and is deleted after 180 days without use.
- Browser alert addresses: until you turn alerts off on that device, the browser expires the address, the account or private record that authorised it is deleted, a host’s My vFound link is reset, their email changes or they are deactivated or removed (for alerts about their visitors), or delivery keeps failing. A failed address is deleted after 30 days. Access to the related site and product is checked again before every alert.
- Private walkthrough records: each record of a page load, with anything you allowed us to note about watching, is deleted 12 months after the page was opened. A marker that an email about a walkthrough was sent (which walkthrough, which kind of email and its date, with no device or playback detail) is kept without a time limit so the same email is never sent twice. Copies in backups are deleted within 30 days after that.
- Backups: daily backups are kept for 30 days, so deleted data can remain in them for up to 30 days. Archives made when we moved vFound to new servers in September 2026, on our server, are kept only in case the move has to be undone, and are deleted once we confirm it is complete.
Delegation relationships, including ended delegations and their timestamps and revocation record, remain until the host or delegate is deleted from the people list or the site’s workspace is deleted. Ended relationships disappear from the workspace’s recent-delegation list after 30 days; this does not erase the stored relationship. Pausing a person removes their access but retains the relationship. Arrival follow-up records, notice references and statuses, and delegate reply attribution are kept with the visit and deleted when that visit is deleted under its retention rules. Ending a delegation or deleting a person stops delegated access but does not erase historical reply attribution from a retained visit. Copies in backups follow the backup retention described in this policy.
Website analytics: identifiable event and user data retention is set to 14 months without extending it on new activity. This setting does not delete Google's aggregate reports. Consent choices are remembered in local browser storage for 180 days. Analytics cookies expire after 180 days without renewal by our tag configuration; withdrawal removes them from this browser and stops further collection, but does not erase earlier reports.
Optional enterprise identity records: we keep the customer’s provider settings, encrypted client secret, domain-ownership proof and provider subject/email linked to a staff login. New provider settings saved while single sign-on is required are kept encrypted until a sign-in through them succeeds or the owner keeps the current ones. Authenticator secrets are encrypted; recovery codes are stored only as fingerprints. Sign-in challenges work for 10 minutes and are deleted after 24 hours past expiry. Account authenticator records go with the login. Site identity settings and linked provider identities go with the site’s deletion. Group settings follow its 24-month closure retention, with provider access disabled and its client secret and any waiting provider settings removed on closure. Settings and sign-in audit events are retained for 24 months.
Your organisation’s identity provider authenticates you under your organisation’s agreement. vFound validates its signed response and restricts access to existing site memberships. Creating staff at first sign-in starts off and grants staff access only in configured sites. Provider MFA follows your organisation’s policy; it can also require a vFound authenticator after single sign-on. A designated break-glass owner keeps password and authenticator access if the provider is unavailable.
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.
Preregistration details, event association and induction acknowledgements follow the existing retention period for the related visit and are deleted with it. An acknowledgement expiring does not by itself delete its record. Event signup configuration and induction text versions remain until the site account is deleted. Turning these optional features off stops their forms but does not shorten the existing retention period. Copies in backups follow the backup retention periods described in this policy.
Visitor feedback, its submission time, the opt-out time, the active feedback-email choice time and its email/pass fingerprint, and the invitation-attempt time are kept with the related visit under its existing retention period and are deleted with that visit or with the site's data. Choosing “Opt out and remove my feedback” clears the live rating, comment, submission time and active email choice (including its fingerprint), prevents further feedback for that visit and retains the opt-out and any invitation-attempt time until visit deletion. Turning email off, opting out or changing the visit email or pass token clears the active email choice and its fingerprint. Turning the site setting off hides the feature but does not erase retained data. Expected or signed-in visits use their existing arrival or valid-date window for private follow-up access; visits marked signed out permit 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 backup, application-log, email-delivery and failed-task retention periods continue to apply. Encrypted invitation jobs may contain visit and site references and a recipient/pass fingerprint; they contain no feedback comment. Deleting a visit prevents a new invitation attempt, but cannot recall an already-started send, delivered mail, saved copies or protected backups awaiting scheduled expiry.
7. How we protect it
Traffic is encrypted with HTTPS. Passwords are stored only as salted hashes, and sign-in is rate limited. Instead of the password, a person can ask for a one-time sign-in link by email: it works once, for 15 minutes, only on the address where it was asked for, and to check it we keep only a one-way hash, deleted 24 hours after the link is used or expires. Access is restricted to those who need it: every request is checked against the person’s site or customer-group membership, group access is narrowed to an assigned region when applicable, every record query is limited to an authorised site, and automated tests check that one site or region cannot reach another’s records. Group summaries and their summary downloads contain counts and site settings. Separate open-work lists and their CSV downloads contain the limited operational details described in section 2, scoped to the sites and regions the person may see, without email or phone fields. Security-relevant actions are recorded in an audit log, including the reads and refused changes a platform administrator makes while supporting a customer (the page and who, never the content). Directory CSV links are encrypted in the database, every redirect is checked again and downloads are limited to public HTTPS addresses and 10 MB. Daily backups are kept on our server with access limited to administrators, an encrypted copy is kept off the server, and restores are rehearsed. Public forms are protected against automated abuse. No system is perfectly secure, but if a breach affects your personal data we will notify the relevant supervisory authority and affected people as the law requires and without undue delay.
Every photo sent to vFound is checked on our own server by an automated image check for sexually explicit content before it is kept. The photo is not sent anywhere for this check, and the check keeps no copy. A photo it flags is refused and not kept; we keep only a record that a photo was refused, its score and when.
8. Cookies
We use essential cookies: vfound_token keeps you signed in for a limited time; vfound_session and XSRF-TOKEN protect forms against forgery and last two hours; vfound_lang remembers the language you pick on public and guest pages for a year. Your workspace language is also saved on your account and remembered in a separate language cookie, vfound_ui_lang, for a year. A paired visitor kiosk, which a site can allow to sign visitors in and out, record parcel arrivals, hand out equipment for self check-out and take in coats and bags for self check-in, also uses one essential, revocable cookie, vfound_kiosk, for up to 400 days, renewed when the kiosk is used. A paired Checkroom counter screen uses one essential cookie, vfound_checkroom_counter, for 30 days, renewed while the screen is in use, until the site removes the screen. A counter sign-in at a registered Checkroom or Queue counter device also sets one essential, HttpOnly cookie, vfound_counter_proof, for the length of that session (at most 10 hours), which lets the browser open that session's printed tickets and, at Checkroom, photos. If you tick Remember me on a site’s visitor sign-in page, an essential, HttpOnly cookie, vfound_visitor_me, holds a random key to your saved details at that site, for the same period as the details (up to 365 days from your last sign-in with it ticked); Forget me removes it.
We also keep a few things in your browser’s own storage, which is not a cookie. Local storage stays until you clear it: vfound_legal_seen remembers that you dismissed the notice of an updated legal page, vfound_analytics_consent_v1 your analytics choice (for 180 days), vfound_sessions and vfound_install_hint how many visits you have made and whether the install hint was shown, and vfound_label_format the label size a team member chose, vfound_checkroom_station the Checkroom station a team member chose for quick check-in, vfound-checkroom-device a random name this browser gives itself and vfound-checkroom-device-label the device name a team member typed, which tie money recorded at the Checkroom desk to the shift open on that device, and vfound_walkthrough_consent that you pressed Allow on a private walkthrough (only if you did; Stop removes it). Session storage is cleared when you close the tab: vfound_venue remembers which site you are working in, vfound_session_counted that this visit was counted, vfound_fab_closed that you closed the trial prompt, and vf-workspace-reload stops the workspace reloading itself twice for your language. Where your visit started, which the contact form sends with an enquiry, is held in the page’s memory only and is gone when the page reloads or closes.
If an owner or manager turns on offline mode for a site (it starts off), a team member can record equipment check-outs, returns and stock-take scans, visitor sign-ins, sign-outs and roll-call marks, Checkroom check-ins and hand-backs, and Queue additions, calls and the end of a visit on the Offline desk while the connection is down. Each waiting action is kept in that browser’s own storage (IndexedDB, not a cookie) encrypted with a key the browser makes and cannot export; only its id, when it was recorded and whether it is waiting are readable, and the person and site it belongs to are stored only as codes made with another key the browser cannot export. The names of people added to a Queue line this way are inside the encrypted part, so they are kept encrypted on the device until the action is sent. It is kept for the person and the site that recorded it, and is deleted when it is sent, when that person signs out (if any actions are waiting, they are told first and choose), when someone else signs in on that browser and, if it was never sent, once it is 72 hours old, the next time vFound is opened in that browser. The records the Offline desk shows are held in the page’s memory only and are gone when the page reloads or closes. The workspace's service worker still stores no page or answer from the server; a paired visitor kiosk with offline sign-in has its own, described below. An action is dated at the moment it was recorded only if 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 the action arrived; otherwise it is dated 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. The record’s history and the site’s audit log say that it was recorded offline, with both times. Once sent, we also keep 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, for 30 days.
If a site turns on offline sign-in for its visitor kiosks (it starts off), a paired kiosk that loses its connection keeps the walk-in sign-ins it takes in that tablet's browser storage, encrypted with a key kept in the same storage, and deletes each one once it is sent or after 12 hours. A photo, a signature or an agreement is never kept this way. A separate service worker, used only by that kiosk page, keeps the kiosk's start page and its files, and the browser keeps the kiosk's settings (no visitor details), so the page can open without a connection.
Optional Google Analytics cookies are used only after you accept analytics on the public marketing website. Accept and reject are equally available. Use Analytics preferences on a public page to change your choice. We do not enable advertising cookies or advertising personalisation.
Optional identity-provider sign-in also uses the essential vfound_sso cookie, encrypted, HttpOnly and lasting 10 minutes. It ties the response to the browser that started sign-in and is cleared when the attempt finishes. It uses SameSite=None with Secure for a cross-site SAML response; signed assertions, state and replay checks protect that route. When you choose single sign-on on the sign-in form, vfound_sso_email keeps the email you typed, encrypted and HttpOnly, for up to five minutes so the next step can find your organisation’s provider; that step clears it. When single sign-on, or a vFound administrator's sign-in from vfound.io to a vFound region, asks for an authenticator code, vfound_mfa (HttpOnly, 10 minutes) names that sign-in step so it never appears in the page address; it is cleared when the code is accepted. When you sign up by card, vfound_signup (HttpOnly, 24 hours) lets only the browser that filled in the form return from Stripe’s payment page to its new workspace or try Checkout again; it is cleared when the workspace opens and the pending sign-up it names is deleted after 24 hours if Checkout was never completed.
9. Your rights
Depending on where you live, you may have the right to access your data, correct it, delete it, restrict or object to its use, receive it in a portable format, withdraw consent, and not be discriminated against for exercising these rights.
If your data relates to a claim, contact the site’s team handling it: the site can correct, export or delete a guest’s details in vFound itself, and we will assist them. Otherwise write to armaan@vfound.io. We respond within 30 days and may need to verify your identity first. There is no charge unless a request is manifestly unfounded or excessive.
If your data relates to a visit, open Your information on your visitor pass to download what the site holds about that visit or erase it, or ask the site: its owners and managers can find, correct and anonymise you in the visitor directory. Write to armaan@vfound.io if you cannot reach the site.
If your data relates to a queue ticket or a booked time, ask the site. Its team can see your ticket or booked time, end or cancel it, and erase a remembered-visit record by the email address it was made with; you can also delete that record yourself from your ticket page. The other details of a ticket or booking are deleted when the site's period ends (section 6). Write to armaan@vfound.io if you want something done sooner or cannot reach the site; we respond within 30 days.
You can also complain to a regulator: the Office of the Privacy Commissioner of Canada, or in the EEA/UK your local supervisory authority or the UK Information Commissioner’s Office. We would rather you raise it with us first.
10. Children
vFound is not intended for children. Site accounts are for adults acting for a business, and we do not collect children’s data for our own purposes. A school that uses vFound may load pupil records it controls: in the Visitors school office (section 2) and, if it ticks that option, the students in its OneRoster export. We process those records only for that school, on its instructions. They stay until the school removes them (the school can delete people from its people list, and an owner can delete the school office all at once), except the school office records that have the retention period described in section 6. If you believe a child’s data has reached us in any other way, through a claim for example, contact us and we will work with the site to remove it.
11. A note for guests making a claim
Treat the private claim link we email you like a password: anyone with it can see that claim. Do not send passwords, card numbers or identity documents through a claim message or a general enquiry. Submitting a claim does not confirm ownership; the site decides. The private link to a lost-item report works for 30 days; every email about the report carries a fresh one, and while the report is open the guest page can email a new one to the address it was made with.
12. Changes and contact
If we make a material change we will update the date above and tell account holders by email or in the product. The previous version, dated 4 October 2026, is available on request. For any privacy question or request, email armaan@vfound.io, or use our contact page. See also our Terms of service and Data Processing Agreement.
Version history
What changed on 17 November 2026 (Equipment, Visitors and Checkroom choices): section 2 now describes what the newer optional choices keep: for Equipment, the place recorded at the desk, household members, library card sign-in, fixed RFID readers, posting items back, membership days and booking credits, volunteers and member cards, pass checks, Kandji, OneRoster, Google Calendar, a ticket receiver, hotel guest look-up and access control; for Visitors, a site's own Salesforce, door systems, guest Wi-Fi through Aruba ClearPass and mail server, the presence feed, vaccination records, agreement translations and decision links; and for Checkroom, Salesforce, remembered guests, the optional question, message buttons, tap tags and seal photos. Section 4 says 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, section 6 how long help desk tickets and document custody records are kept, and section 8 what an offline visitor kiosk keeps.
What changed on 17 November 2026 (Queue, more a site can turn on): section 2 now describes what Queue keeps for booked-time reminders and the waiting list, follow-up and text messages, consent boxes and the new kinds of answer, the one place for each email address or phone number, invitation and share links, a join form on a site's own website, the block list, staff first names on the waiting-room screen, a site's own Google Analytics id, the API and test keys and the report counts; section 4 names Google Analytics for that use and says the team's words in a Queue message can be translated by Amazon Bedrock when a site turns that on; and section 6 says how long each of these is kept. Section 4 now also says what is sent to the AI when a site uses Match columns with AI, Describe your site or a drafted message, and the weekly read sentence now covers every product the site has. Section 6 now says how long a note sent with a reminder is kept.
What changed on 16 November 2026 (Queue): section 2 now describes what vFound Queue keeps about a person who takes a number, and what a site can turn on for it (booked times, messages, a short survey and remembered visitors), and section 6 how long each is kept. The sentence about Enterprise custom attributes now names the products that have them.
What changed on 13 November 2026 (Ask vFound on our website): sections 2, 3, 4 and 6 now describe Ask vFound, the AI assistant on our public website: what is sent to answer a question, that Cloudflare Turnstile checks before the first question, and that questions are kept for 90 days with no network address or other identifier.
What changed on 16 November 2026 (Queue desk counter sign-in and offline mode): sections 2 and 8 now say that the optional counter sign-in covers the Queue desk as well as Checkroom (its session records name the product, and its printed tickets use the same essential cookie), and that the optional offline mode covers Queue additions, calls and the end of a visit, with the names of people added kept encrypted on the device until sent. Both stay off until a site turns them on.
What changed on 13 November 2026 (Checkroom counter sign-in): section 2 now describes the optional counter sign-in for Checkroom: a staff number, a PIN and a QR badge kept only as one-way hashes, the devices an owner or manager registers, and the session records of each counter sign-in and how long they are kept. It is off until a site turns it on.
What changed on 13 November 2026 (Equipment sign-in, quotes, deliveries and directories): sections 2 and 6 now describe what a site can keep when its borrowers open its Equipment catalogue through the site’s own identity provider, when it imports a student information system file or connects its own LDAP, Active Directory or Google Workspace directory, and when its team keeps quotes, payment requests, deliveries, notes on items and fields on borrowers and bookings, and how long each is kept. These are for a site to use or turn on.
What changed on 13 November 2026 (Visitors cards, fast-track codes, ID dates and location checks): section 2 now describes the optional location check, RFID cards, fast-track codes, things handed over and the expiry date of a physical photo ID that a team member types. They go with the visit and are deleted when it is.
What changed on 13 November 2026 (Checkroom text PINs, guest photos, offers and validations): section 2 now describes the optional text PIN and pickup code, the photo of your things on your own ticket page, details a guest types on their phone, reminder and offers texts, replying READY to find your ticket, and a partner validation recorded on a ticket, and how long each is kept. Each is off until a site turns it on.
What changed on 13 November 2026 (Ask vFound guides): section 4 now says that Ask vFound answers from vFound’s own guides to the products a site has (Lost & Found, Equipment, Visitors and Checkroom), and that a site’s Lost & Found settings are sent only at a site with Lost & Found.
What changed on 13 November 2026 (Equipment maintenance, connected systems and AI suggestions): sections 2 and 6 now describe what a site can keep for its Equipment: purchase, supplier, fund, depreciation, insurance and disposal details, licences, a hazardous substances register with data sheet files, work orders and maintenance requests (which can name the borrower who reported a problem), and a desk rota; what is sent and kept when a site connects its own learning platform, ticketing system, Intune or Jamf; the photos and words sent to the AI provider when staff ask for an Equipment suggestion; and how long each is kept. These choices start off, and a site turns each on.
What changed on 13 November 2026 (Checkroom hotels and events): sections 2 and 6 now describe the Checkroom choices a hotel or event site can turn on: vehicle plates, key notes, photos and damage marks, tamper seals, shipping notes, bell desk deliveries, a ticket type and seat label on an event guest list, guest history showing earlier tickets and the team's notes, event RSVPs and a member list, and how long each is kept. We also corrected the sentence about earlier tickets.
What changed on 12 November 2026 (offline mode, phone messages and reports): sections 2 and 8 now describe the optional offline mode (what a team member's browser keeps while the connection is down and when it is deleted), a site changing the words of its SMS messages, and the report data feed links and the saved report emails an owner or manager can set up. Each is off until a site turns it on.
What changed on 12 November 2026 (Checkroom money, shifts, terms, things left behind and messages): sections 2 and 6 now describe the Checkroom choices a site can turn on for recording money taken at its desk, team shifts and cash counts, its own terms and a declared value, reminders and a disposal date for things left at closing, a list for a lost-property office, its own words in alert texts, a sponsor line, and offers by SMS with a coupon and a short survey for guests who chose offers, and how long each is kept.
What changed on 12 November 2026 (Checkroom storage and queue): sections 2 and 6 now describe the Checkroom storage and queue choices a site can turn on: where things have been, ID checks at hand-back, pickup times, the To store and To fetch lists with each team member’s status, and asking you by email to approve someone else collecting, sent only to the email given at check-in; the Checkroom records kept whatever a site chooses; and how long each is kept.
What changed on 11 November 2026 (Checkroom): sections 2, 6 and 8 now describe the new Checkroom choices a site can turn on: the phone number or a PIN as the ticket, typing your own details on your phone, your photo of your things, an optional face photo the team takes with your agreement, VIP marks, returning-guest counts, reusable hanger tags, a changing QR, sharing a ticket and a counter screen with its cookie, and how long each is kept.
What changed on 12 November 2026 (Visitors): sections 2, 6 and 8 now describe vFound Visitors guests added by another visitor, team-confirmed group agreements, sign-out reminders, what printed badges and paired kiosks show, the driving licence name read, and the optional Remember me with its vfound_visitor_me cookie. Sections 2 and 6 also describe more of what a site can turn on in vFound Visitors: invitations and reminders, documents uploaded and a signature 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, visiting limits for wards and residents, guest Wi-Fi and Eventbrite connections, staff sign-in and its attendance records, catering requests, appointment pages, desk, room and parking booking, reception, signage and room displays and the parking permit on a badge. Each is off until a site turns it on, and section 6 says how long each is kept. Sections 2, 6 and 9 also describe the Visitors blocklist and the optional check against the US Consolidated Screening List, questions whose answers ask a team member to decide, emergency roll calls with messages, replies and conversations with the team, hazard alerts a team member writes and sends to a chosen group, a mobile number for emergencies and evacuation maps, the visitor directory, what anonymising a person deletes and what it keeps, Your information on a pass, and how long each is kept. They no longer say that vFound runs no watch list.
What changed on 13 November 2026 (children and school records): section 10 now says exactly what is true: we do not collect children’s data for our own purposes, and a school may load pupil records it controls (the Visitors school office, and students in a OneRoster import if it ticks that option) for us to process only for that school. Section 2 now says the OneRoster import reads teachers and staff, students only when ticked, and never parents, guardians or relatives.
What changed on 12 November 2026: sections 2 and 6 now describe what new Equipment options keep (accepted terms, checkout photos, trainings and their proof, borrower types, holds, hand-overs, clearance certificates and kiosk returns), each kept only when the site turns an option on or its team uses them, how long each is kept, and that a site's own Equipment checklists are on every plan and keep working after Enterprise ends. Section 2 also now describes waiting-list places, risk-assessment answers, saved items and a borrower's calendar address, stock handed out and supplier contacts, Equipment fees entries, deposits, payments a site took itself and invoices, saved scan positions and borrowers' stock-take answers, with how long each is kept in section 6. vFound records fees and payments a site took itself and never processes a payment.
What changed on 11 November 2026: section 2 now says that we count visits to our public website that arrive from an AI assistant, per day, assistant and page, with nothing about the visitor attached.
What changed on 10 November 2026: sections 2, 3, 6 and 8 now say that an enquiry from the contact form also keeps how you found us, if you choose an answer, and where your visit to our website started, which your browser holds in the page’s memory until you send the form.
What changed on 7 November 2026: section 2 now says that a trial request through the contact form also keeps the products you choose, and that the pending sign-up it describes applies only to card sign-up, which is switched off while we set up every account ourselves. Sections 2, 4, 6 and 8 now say that Stripe and the sign-up cookie apply when you pay by card. 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.
What changed on 4 November 2026: sections 2, 4 and 6 now describe the Ask vFound help panel and how long its conversations are kept, and section 4 now says that vFound AI helps choose which found items a guest is told may match their report.
What changed on 3 November 2026: section 4 now names Amazon Web Services (Amazon Bedrock, which runs Anthropic's Claude) in Sydney and Melbourne, Australia, as the provider of vFound AI, in place of OpenRouter and the model providers it used, and also says what the claim check is given, and section 5 says where AI requests are processed.
What changed on 3 November 2026: section 2 now calls the group's command centre Network settings and says that the network page, named after the group, lists the open work at the venues a person may see. The cookies section now says that vfound_mfa also names the authenticator step of a vFound administrator's sign-in from vfound.io to a vFound region.
What changed on 2 November 2026: section 2 now says that on a group’s organisation page, "Check my claim or report" checks every location that page lists.
What changed on 31 October 2026: section 2 no longer says guests are not told about matches at other venues. It now describes the match a guest may be told about at another venue of the group (never at a venue that keeps its found items private), locations in a group, and the daily email to the people who run each venue. Section 2 also now says that a venue’s found items can be searched across the group’s venues.
What changed on 30 October 2026: section 2 now describes messages between a venue’s team and a guest about a lost report, and venues that keep their found items private.
What changed on 25 October 2026: section 2 now says that matches across a group’s venues do not show the reporter’s name, email address, phone number, the address the report came from or any photo, and that opening a record shows only what the person’s role at that venue already shows. Section 6 says that the address a lost report was sent from, its approximate place and any photo the guest added are also deleted when an owner or manager deletes the guest’s details from the report. Section 2 now says that a group’s command centre also lists open lost reports at the venues a person may see, by title, category and date, never who reported them. It also says that owners and managers can download their venue’s audit record. Organisation pages can list found items that their venues already publish, off unless the group turns it on. When venues in one customer group send a found item from one venue to another, the finder’s details recorded with it now go with the item. Section 2 also says that, to answer a request from a guest, a group owner, manager or regional manager can find which of their venues with Lost & Found open hold a record with that guest’s email address or phone number.
What changed on 24 October 2026: section 2 now describes lost-item reports that a venue’s team records for a person by telephone or in person, which can omit a name and contact details and are on unless the venue turns them off, and the private location or journey details a venue can choose to collect on reports and found items, which are off unless the venue chooses them. It also describes organisation pages that a group can publish to route a report to one of its venues, off unless the group publishes one, and matching across a group’s venues, off unless the group’s owner switches it on. Section 4 describes selected webhook events that a venue can send to systems it chooses, such as a CRM. Section 6 says how acknowledgements, phone messages and mailbox verification work for staff-recorded reports, and how long matches across venues are kept.
What changed on 23 October 2026: sections 2 and 6 now describe Visitors delegates and unanswered-arrival escalation, both off unless the venue turns them on, and how their records are kept. Sections 2 and 6 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. On vFound Enterprise, an owner or manager can connect a Cloudbeds property API key limited to read-only reservation access, an OfficeRnD Flex application or a Microsoft Entra ID application. 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.
What changed on 22 October 2026: sections 2 and 6 now also describe equipment status history, optional staff warranty reminders, CSV invitation previews, event names and optional backup-host notices, with matching changes to the Data Processing Agreement. The Terms are unchanged apart from their date. Section 2 now says what we record when someone opens a private walkthrough link we sent them: what our server notes when the page is opened, and what we note about watching only if the viewer presses Allow. Section 4 now says our own notice emails tell us when a private walkthrough is opened or played and name the person or organisation it was made for. Section 6 says how long these records are kept, and section 8 names the one note the page keeps in the browser if you press Allow. Section 2 now also describes what we keep when you tell a venue you found something, and that the venue’s team can see what your lost-item report said before each change you make to it; section 6 says how long found-item messages are kept. Section 1 now names found-item messages among what a venue controls, and section 2 says when a receipt is sent and the short record we keep to limit receipts.
What changed on 19 October 2026: section 2 now says that a lost-item report sent from a venue’s lost and found page records the internet (IP) address it came from and an approximate city, region and country, as a claim already did, why we keep them and who at the venue sees them: owners and managers see the address and the place, other team members only the place, and view-only members neither. Section 4 now says the location lookup also serves those reports, and section 6 says how long they are kept.
What changed on 17 October 2026: section 2 now says what we keep when you contact vFound support, from the contact form or from Help & support in the workspace, and who can read it; replies to our support emails now arrive at our own mail server (section 4). Enterprise service reports now count requests from Help & support in the workspace too. Sections 2 and 6 now say that support conversations are deleted 24 months after the last message or change. Section 2 now says that a contact form message from someone who is not signed in to a workspace is kept as an enquiry record and answered from our Google Workspace mailbox, and that a message sent while signed in becomes a support request for the venue you are working in. Section 2 now says that each enquiry and support request has its own reply address at vFound, so replies to it, including the replies our team sends from the company mailbox, are kept with that conversation, and that copies of our replies may be delivered to our company mailbox.
What changed on 16 October 2026: we removed the optional service through which a guest could pay vFound to post an item back, before it was switched on for any venue, so Easyship is no longer one of our providers and no shipping details were ever sent to it from a venue. Section 2 now says what we keep when a venue's team posts an item to you itself. Section 2 now says that a group's command centre also lists the open work at the venues a person may see, with names but never a guest's email address or phone number.
What changed on 15 October 2026: when someone signs up for a new venue, we now record the internet (IP) address the sign-up and its email verification came from, with an approximate place, so we can tell genuine venues from fake sign-ups; section 2 describes it and section 4 names the lookup service. Sections 2 and 6 now say that a new venue sign-up creates no account until Stripe confirms a valid card: until then we keep only a pending sign-up, which is deleted 24 hours after it was made if no card was confirmed. Section 2 also says what vFound records when a venue sends a found item to another venue of the same customer group, and that an item with a claim is never sent; section 6 says those records are kept with the item.
What changed on 8 October 2026: sections 4, 5 and 6 no longer mention a stopped server that held archives from before our September 2026 move. That server has been deleted.
What changed on 7 October 2026: our service email is now sent through Resend, which section 4 names with what it receives. vFound now records whether each email it sends was delivered, without keeping the address, so a venue’s team can see when a notice did not reach someone; section 6 says this record is kept 90 days. Section 5 adds our email delivery provider to those that may process data in the United States.
What changed on 6 October 2026: vFound now records when each team member last signed in and when they were last active in the workspace (the time only, not the page, address or device). Section 3 describes it and says how long it is kept. Section 6 now says that a browser’s error reports are counted against the sender’s address for 24 hours under a one-way hash, without storing the address. Section 7 now describes signing in with a one-time link by email.
What changed on 5 October 2026: Ask vFound no longer takes spoken requests, so section 3 no longer describes voice input. Section 4 now names IndexNow, which receives the addresses of our public pages. Section 6 now says that a checkroom ticket left at closing is kept 12 months from that closing, and how long background tasks that could not finish and disconnected AI assistant connections are kept. It also describes the error reports vFound keeps to find and fix faults.
What changed on 4 October 2026: this page now says more completely what we already do. It describes email to inventory (the photos staff email to a venue’s private address, kept as drafts with the sender, subject and note, and deleted after 30 days), what vFound AI is and is not sent, the weekly insights and their Monday email, photo splitting and duplicate checks, how long what the AI wrote is kept, how long application logs are kept and that the server’s system journal is separate, every cookie and browser storage key we use, Cloudflare Turnstile as the only captcha provider, how long hotel stays and connector sync history are kept, and what stays after an account is closed. Drafts and AI results are now deleted automatically on the periods stated. A venue’s owner can take their venue out of a customer group at any time, and a platform administrator’s reads and refused changes of a customer’s records are now recorded in the audit log. When the team describes a lost checkroom ticket to vFound AI, ticket notes are no longer sent and email addresses are removed from the description.
What changed on 3 October 2026: this page now describes the minimal hotel stay context a venue can link to a found item or parcel, what it deliberately excludes, who can see it and when it is deleted. It also describes customer groups, regional access, aggregate command-centre counts, group policy settings and the 24-month retention of their audit history. An owner or manager can connect a Cloudbeds property API key limited to read-only reservation access, an OfficeRnD Flex application or a Microsoft Entra ID application. From Cloudbeds, vFound keeps only the reservation and optional guest references, guest name, arrival and departure, time zone, current room, reservation state and source timestamps needed for private stay context. From OfficeRnD and Entra, it keeps only the source ID, name, email and active status needed for the shared people list. It does not read Cloudbeds rates, payments, loyalty data, identity documents, preferences or unrelated notes; it does not read OfficeRnD memberships, bookings, invoices, payments, custom properties, addresses or phone numbers; and it does not use Entra to create vFound staff accounts, roles or access decisions. Customer-configured operating policies add permanent versions, local exceptions, acknowledgements and aggregate service-level alerts; these advanced controls remain off until a group manager configures them. When a person is deactivated, their private My vFound access and host browser alerts end and they cannot be selected for new work. Open parcels, equipment checkouts, reservations and visitor records remain available to the authorised venue team until they are resolved.
Analytics update on 2 October 2026: optional Google Analytics on public marketing pages now asks for consent, with equal accept and reject choices and withdrawal controls. Private product workflows are excluded.
What changed on 2 October 2026: a visitor type can optionally require a private visitor photo, use it on a printed badge and require staff to record a visual check of a physical photo ID. This page now states who can see the photo, what the check records, what is deliberately not stored or automated, and that both follow the visit retention period.
What changed on 28 September 2026: a signed My vFound link now works for 60 days, and earlier links stop working when a person’s email changes, when they are deactivated or removed, or when an owner or manager resets their link. A visitor pass shows arrival details once the visit is approved and Wi-Fi details only while you are signed in, and printed badges carry only a short desk code. A visitor type without its own retention period follows the venue’s, and anyone still signed in is signed out automatically after the day ends once they have been in for 12 hours. Checkroom tags on your things show only the ticket number. The private link to a lost-item report now works for 30 days, and the venue page can email a fresh one. Team members other than owners and managers see a masked email address for people on a venue’s people list. A host’s browser alerts about their visitors end when they leave the people list, including when a directory sync deactivates them. Hosts are no longer messaged through a connected Slack workspace, and any stored Slack connection records were deleted; Slack, Microsoft Teams and Google Chat channel alerts are unchanged. A Checkroom ticket can no longer be saved to a phone wallet app.
What changed on 26 September 2026: vFound Equipment now supports reservations, multi-item checkouts, borrower self-service and paired-kiosk checkout, plus asset, maintenance and stock-take records. vFound Checkroom now supports stations, events, an exit queue, printed tags, paired-kiosk self check-in and optional fee recording. This page now names those records and their retention.
What changed on 25 September 2026: this page now covers the vFound suite: vFound Parcels, the mailroom tool (what it keeps about the people a venue receives parcels for, that vFound AI can read a parcel's label, and that finished parcel records are deleted after 12 months), and vFound Checkroom, for coat check and luggage storage (what a ticket holds and how long it is kept), and vFound Equipment, for handing out equipment (what its records hold about a borrower, and that finished records are deleted after 13 months). Later the same day it added vFound Visitors, for visitor sign-in (what a visit record holds, who is told when you arrive, and how visit records were retained). Later still it added private calendar links for a venue’s team, Google Chat alerts, directory connections, each person’s signed My vFound page, and how long unused calendar links are kept. It now also covers visitor types and their questions, self-registration, approvals, multi-day passes, kiosks, roll calls, calendar invitations, host replies, couriers and a venue's visitor retention choice.
What is changing on 25 October 2026: anyone who turns them on can get vFound notifications in their browser. A venue that has agreed to the push services sooner (see the notice) offers them before that date. They are delivered by their browser’s own push service (Google, Apple, Mozilla or Microsoft), encrypted end to end so the push service cannot read them. A person chooses alerts separately in each browser, either while signed in, from a private pass or ticket, or from a signed link in their service email. Emails continue as before. The notice in our Data Processing Agreement has the details.
Also from 7 October 2026: a venue's lost and found page no longer offers a separate email alert. A lost report now does that job: it shows possible matches straight away and emails you each time a likely match is logged over the next 90 days. Alerts set before this date keep working as before until they are used, removed or 60 days old, as section 6 says. One form, "Check my claim or report", now sends a fresh private link to each of your claims and open reports at that venue when you give the email you used. A guest whose claim ends because the item was not collected is now told by email.
What changed on 24 September 2026: this page now names where our servers are (Singapore), our support mailbox (Google Workspace) and our own mail server; lists everything we hold for lost reports, alerts, pickups and returns; states how long each kind of record is kept; and describes our security, closed accounts and the tools venues use to correct, export and delete claim records. It no longer describes extra sign-in checks, the last of which we removed on 23 September 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.
