VISIT PORTAL
Privacy & data use
This notice describes how the BCF demo of Visit Portal handles information. The portal helps users organize work rounds, record business visits, and provide information for owner review.
Information the portal records
The portal records the name entered by a user, session start and end times, assigned locations, visit completion, business contact names, comments, checklist responses, and any explanation for ending a round early. Visit photos include their capture time, GPS coordinates, GPS measurement time, and reported location accuracy.
Camera and location access require browser permission. The portal checks location when starting or resuming work and while its visit camera is open. It attaches a recent location to each visit photo. It does not continuously track location in the background; the camera’s location watch stops when the page is hidden or the camera closes. The camera does not request microphone access. Separate owner connection-test photos do not require GPS and do not count as user visits.
Where information is stored
Structured reports are stored in the portal’s Cloudflare D1 database. Submitted photos are kept in a private server storage buffer while they await confirmation from the owner’s selected Google Drive destination. After successful Drive synchronization, the portal removes that buffer copy; a copy can remain if cleanup fails. The owner can retrieve stored photos for review.
Your browser uses a sign-in cookie and local storage to resume your session and preserve drafts, including unsent photos, during connection interruptions. Hosting and storage providers process information needed to operate these features.
Who can see portal information
A user can view their current session, their drafts, and shared location-completion progress. The authenticated owner can review reports and photographs across sessions. Users do not receive access to the owner’s Google Drive account. The portal does not create public photo-sharing links.
Google Drive access
Only the owner connects a Google account. The connection requests access to files and folders selected for this app and files it creates, rather than access to the entire Drive. The portal checks the connected account and destination permissions, creates its photo folders, and uploads, retrieves, and verifies its files. The Google account email and relevant file metadata are used for these checks.
Google authorization credentials are held on the server and are not returned to user or owner portal pages. Google data accessed through this connection is used for the portal’s photo storage, retrieval, and verification. This portal has no advertising, data-sale, or model-training features.
Retention and requests
Records and Drive photos are kept for owner review. The portal does not currently apply an automatic retention schedule. To ask about access, correction, deletion, or Google Drive disconnection, contact sanjay.ismailov@gmail.com. Removing Google authorization stops future Drive access; it does not itself delete records or photos already stored.
Maps and address lookup
Owner maps display the GPS location recorded with a photograph and the intended destination. They do not show a live user location. Map images are requested from OpenStreetMap; the provider receives the viewed map area, browser network information, and this site’s origin. Photo contents, user names, and contact details are not sent with map requests.
Opening Find address in Google Maps sends the entered business address to Google for search in a separate tab. Other external Google Maps links send the selected coordinates to Google. The owner places and saves the destination star separately in this portal.
Driving estimates and visit intervals
When routing is connected, the server sends the saved business destination coordinates to Geoapify to estimate driving time and distance. It does not send user names, photo GPS, photos, or business contact details. Results can be cached for seven days and are saved with each round for later comparison. Estimates use roads without live traffic; they are not measured driving time.
The time between saved visits is based on when the server confirmed each visit. It can include driving, parking, waiting, the next visit, and delayed uploads after a connection interruption. The portal does not use this interval to determine idle time or continuously track users.
Personal accounts, confirmations and visit bonuses
Management can assign a personal access code, account name, Driver or Salesperson role, and optional visit bonus eligibility. The code identifies the account; a name typed at sign-in does not change its saved identity. Access codes are stored as protected verification values and are not returned in reports.
The portal records notice versions and acceptance times, the bonus terms attached to a round, qualifying visit claims, management review decisions and reasons, and a history of changes to those decisions. Pending and approved bonus totals are records for review and payment handling; the portal does not transfer payments. Disabling an account or future bonus participation does not erase prior records or change the terms already attached to a round.