How Boris™ handles your data What stays on your phone. What leaves it.
Your personal checklist stays on your phone by default. Optional sharing, content requests and business services have separate data flows.
Last updated: 2026-09-06
No account needed for your checklist
Your normal personal app state stays on your device.
Your checklist progress, saved places and preferences are stored in the app’s private storage. Normal use requires no email address, password or consumer account. Financial Allowances inputs and results remain on your device.
Boris uses backend services for current content, voluntary corrections, paid-partner aggregate counts, optional encrypted phone pairing and separate business accounts. Saying that Boris has no backend would be inaccurate. These services do not turn your personal checklist into an account profile.
There is no consumer-account backup to restore your checklist from. Optional pairing is described below; it is not an account-based backup service.
The app’s network activity
Current content and images
The app requests public checklists, local guidance, directory listings, recommendations and other content, including their images. Some content requests carry coarse choices such as the selected community or status so the app can receive relevant guidance. They do not include your checklist progress or a Boris user, device or session identifier. Hosting services receive normal connection information, including an IP address and request time. The exchange-rate feature also requests rates from an external provider.
Corrections you choose to send
A correction includes the task reference, task title, the text you enter and an optional source. It is processed through Cloudflare and stored in a private GitHub repository for review. When configured, a notification containing the correction can also be sent through an email provider. No consumer-account or device identifier is added by the app.
Free text can contain personal information if you put it there. Please leave out names, personal contact details, orders and other private documents unless necessary to explain the issue. Connection information is also processed for abuse protection; when the correction rate limiter is configured, an IP-address-based record is retained for up to one hour after its latest update. Correction records are not automatically deleted when an issue is closed. If storage for failed deliveries is configured, a copy can also be retained for later handling; that optional store has no automatic expiry configured.
Aggregate counts for paid partner listings
Paid partner listings can produce totals for views and actions such as Call, WhatsApp, Directions, Website and Email. These totals describe the listing, action, date, country and platform, without an app user, device or session identifier. Views are accumulated on the phone and transmitted as totals rather than a sequence of individual views. Free listings do not produce these per-listing counts.
Temporary connection-derived records help prevent abuse. They are separate from the aggregate reports provided to businesses, and mean that describing the entire processing pipeline as strictly anonymous would be inaccurate. Directory category-demand counting is not implemented.
Pairing two phones
Boris passes a sealed envelope between your two phones — and burns it on delivery.
If you enable pairing, checklist progress and the household information needed to build the list are encrypted on the phone before transmission. The two paired phones hold the keys; Boris’s delivery service cannot read the encrypted contents. The service still processes delivery and connection metadata, so pairing does not mean that no data leaves your phone.
Stored encrypted envelopes are removed when collected by the receiving phone, or expire after 90 days if they are not collected. This limit applies to those envelopes, not to all provider logs or business records. Pairing is optional and does not create a consumer account. Pairing keys in protected device storage can survive an uninstall; use the app’s unpairing function to remove the pairing on your phone.
Business requests and accounts
Requesting a listing or claiming an existing business sends the business details and representative’s contact information to Boris for review. Submission alone does not create an account or publish a listing. An approved business account uses passkeys and necessary session cookies. Contact details, business ownership, public passkey credentials and session information are processed on the server.
Business services are separate from the personal app. An expired invitation, challenge or session does not itself mean that the associated account and history have been deleted. Payment services have their own data processing; see the privacy policy for the current service disclosures.
Checking these claims
Network activity depends on the app version and features you use. A traffic inspection can show content requests, images, rate requests, corrections, aggregate partner counts and optional pairing. Images can come from the addresses supplied with the content. A fixed list of hosts would not reliably describe every version or every image.
This page explains the product’s data flows; it is not a certification or a substitute for an institution’s own privacy assessment. The privacy policy provides the formal notice. If a statement differs from what you observe, please report it.
Ask about data Boris holds
Personal state held only on your device is different from a correction you submit, a pairing envelope or a business record stored by a service. Deletion and access requests for server-side information can be sent to hello@borispcs.com. Boris cannot read the encrypted contents of pairing envelopes.
Retention depends on the purpose of the record and any applicable obligation to preserve it. Provider records and historical copies must be considered when responding to a request; removing a current record alone is not evidence that every copy has been erased. Changes to these data practices must be reflected in the privacy notice before release.
