Scope and status
This draft describes the intended privacy practices for the Sorted Living website, waitlist and Bolo app, including supported call and ordering features. It is being prepared for the Bolo rollout and is not confirmation that every feature is available. The responsible legal operator, processing locations, retention schedule and feature-specific notices must be finalized before the relevant collection begins. Sorted Living and Bolo are project and brand names; there is currently no registered entity operating them. The individual or individuals responsible for the beta must be identified in the final notice. Privacy questions and requests can be sent to support@sorted.living.
Information used by Bolo
Depending on the features you use, Bolo processes account and contact details; household membership, roles and permissions; delivery addresses; language and grocery preferences; spending limits and approval rules; order instructions, baskets, transaction references and order status; and support communications. Voice features may involve audio, recordings, transcripts and information extracted from conversations. Technical information may include device and app details, request metadata, errors and security logs. The applicable feature notice will explain its collection before use. Do not share passwords, payment credentials or unrelated personal information in calls or support messages.
Where information comes from
Information may come from you, an authorized household member, your use of Bolo, or a connected ordering service. An invitation may contain your name, contact details and proposed household role before you create an account. You can ask about or request removal of that information without joining. Only supply someone else’s information when authorized; an invitation is not their consent to every data use.
Why information is processed
Information is used to operate accounts, interpret requests, apply household permissions, coordinate authorized orders, provide status updates and support, prevent misuse and investigate errors. Where disclosed and permitted, service interactions may also be used for quality review, evaluation and improvement of Bolo, including development and training of AI systems. This is not blanket permission for every provider to train on your information. The feature notice must identify the applicable uses, recipients and choices, with consent obtained where required. Waitlist signup does not authorize app processing or AI training.
AI uses and your choices
Using a model to respond to a request, evaluating a conversation, reviewing it with a human, training Bolo’s models and allowing a provider to train its own models are different uses. The applicable notice must explain which uses occur, the data involved, the actual AI recipients and your choices before sharing personal information. Agreement to service terms is not blanket consent to unrelated training. An optional improvement or training choice must be distinguished from processing necessary to fulfil an order.
You may contact us to withdraw a relevant consent or ask how information was used. We will explain which processing stops and any effect on the requested feature. Withdrawal does not retrospectively undo processing that was lawful when performed. Further retention and use must still have a permitted purpose; previous use for improvement does not create an exemption from deletion.
Calls, recordings and AI
Before applicable call or voice processing begins, callers must receive information about recording, transcription, AI processing, any human review, retention and relevant choices. This also applies to supported trial calls made before an account is created. A household administrator’s purchasing permission does not replace another caller’s privacy notice or any required consent. Audio and free-text transcripts can identify people even after names and phone numbers have been removed.
Household visibility
Bolo uses household roles and permissions to determine access to requests, orders, addresses and spending information. Before sharing begins, the app must explain what owners, approvers and other members can see. Invite people only when authorized to provide their details. Removing a member or changing purchasing permissions does not by itself delete all related records or withdraw that person’s privacy choices.
Limits on household sharing
A caller’s request may need to be shared with the household approver, and an owner may need membership and spending information to administer the household. The app must explain its actual role permissions. Membership does not automatically authorize access to every recording, private support message or unrelated information. Each member retains their own privacy choices; an owner’s spending approval does not control whether another member may submit a privacy request.
Ordering services and other recipients
Supported ordering services receive information needed for authorized transactions, such as basket details, delivery information and relevant contact details. Bolo may receive transaction references, balances or payment status where required by the integration. Funds remain with the ordering service; Bolo does not hold your grocery wallet balance. The ordering service and its payment providers manage order payments and financial transaction records. Any order reference, balance or status available to Bolo does not make Bolo the holder of those funds or the processor of an order refund. Raise order refund requests directly with the concerned ordering platform. Communications, AI, infrastructure and support providers may process information for the functions they provide. The actual provider chain, processing locations, access and training arrangements must be confirmed in the finalized notices. Ordering services also process information under their own privacy policies.
Processing locations and provider safeguards
The beta is intended for users in India. This does not mean that every provider processes or stores information in India. The final notice must identify actual processing locations and relevant transfer arrangements. Providers acting on our behalf must be subject to appropriate contractual and security obligations covering purpose limits, access, confidentiality and applicable deletion assistance. Independent ordering services also have their own responsibilities and privacy notices. Required overseas-transfer conditions must be met before processing begins.
Device permissions and local storage
Microphone access supports an enabled voice feature and can be controlled through device settings. Opening the telephone dialler is different from recording within Bolo. Notifications or other protected permissions must be requested only for relevant features, with their purpose explained. Declining an optional permission may limit that feature; it does not authorize another way to obtain the same information. Device permission does not replace additional notice or consent required for recording, sharing or training.
The current local app preview saves household information on the device. This differs from the website waitlist. The production notice must describe any cloud synchronization, diagnostics, push identifiers and SDK processing actually enabled. Clearing device data alone does not erase information already sent to a server or ordering service.
Waitlist and website information
The website waitlist collects your email, optional city, marketing preference, signup time and consent-notice version. These are used for early-access updates; other Sorted Living product news requires a separate optional choice. The website has no added advertising trackers, visitor analytics or non-essential cookies, and does not save signup details in browser local storage. Hosting providers may process IP addresses, browser details and security logs. These website statements do not describe every app SDK or connected service.
The website is hosted on Vercel. The signup information described above is stored using Supabase, with the primary database configured in Mumbai, India. This database location does not mean that all hosting, security-log or support processing occurs only in India.
Service messages and marketing
Order confirmations, approvals, account-security messages and requested callbacks are distinct from promotions. Marketing choices must be separate from purchase authorization and necessary service messages. Use the supplied unsubscribe option or contact support@sorted.living to stop waitlist or marketing updates. A minimal suppression record may be retained where necessary and permitted to respect your choice. Waitlist email consent does not automatically authorize promotional calls or SMS; applicable sender, telecom and consent requirements must be met for each channel.
Retention, personal identifiers and deletion
Account deletion covers the Bolo account and its associated personal data, not only direct identifiers. Subject to specific lawful retention exceptions, we will delete personal identifiers such as names, phone numbers, email addresses and delivery addresses, together with associated profiles, household membership and permissions, saved preferences, identifiable order and support records, recordings, transcripts and linked technical data held by Bolo. Deactivation, leaving a household or uninstalling the app is not the same as account deletion.
Limited records may be retained only where necessary and permitted for purposes such as legal obligations, security, fraud prevention or resolving a specific dispute. We will explain the categories retained, the reason and the applicable period or criteria. Such records must have restricted access and cannot be retained indefinitely for unspecified future uses. A pending order or dispute is not a reason to retain unrelated personal data. The final retention schedule and deletion timeframes remain to be confirmed before live collection; this draft does not promise immediate erasure of every record or backup.
Deletion must also cover identifiable copies in quality-review and training datasets and data held by processors on our behalf. We will instruct those processors to carry out applicable deletion requests. Backup copies must expire under the disclosed backup schedule, remain protected from ordinary use, and have deletion requests reapplied if restored. Any limitations involving data already used to train a model must be assessed and explained before that training occurs; they do not create a blanket exception to deletion obligations.
Genuinely anonymized or aggregated information that can no longer reasonably identify you may be retained for analysis, evaluation and AI improvement where permitted. Removing a name, replacing it with an account code or hashing a phone number does not by itself make data anonymous. Voice recordings, transcripts and linked order histories remain personal data where a person can still be identified. We will not attempt to re-identify information retained as anonymous.
Your choices and account deletion
See Bolo account and data deletion for the request steps and consequences.
To request access, correction, consent withdrawal, account deletion or removal from the waitlist, email support@sorted.living. For account deletion, use the subject “Delete my Bolo account” and provide its registered phone number or email. Do not send passwords, one-time codes or payment details. An authorized representative may contact us; we may verify their authority and your identity without requesting unnecessary information. Available rights depend on applicable law. We will explain the expected completion time, any retained data and the outcome of your request, including any reason it cannot be fulfilled in full and available complaint options.
Request deletion of your Bolo account and associated personal data
This web contact route does not require reinstalling Bolo. The production app must also provide an accessible way to initiate account deletion; that feature is not established by this draft. Each household member can exercise their own privacy rights without an owner’s spending approval. Shared records must be reviewed to protect the rights of other members while removing the requesting person’s data unless a specific retention exception applies.
Deleting Bolo does not automatically close an independent ordering-service account, withdraw its wallet funds, cancel a placed order or erase records that service retains under its own obligations. Contact that service for its account and wallet requests. This distinction does not excuse deletion by providers acting as Bolo’s processors. Consent withdrawal applies to the relevant future processing; if that processing is necessary for a feature, we will explain the effect on that feature. It does not authorize continued optional training or marketing.
Retention by purpose
Account, household and preference records support the enabled service relationship and are deleted when no longer needed or on a valid request, subject to specified exceptions. Audio, transcripts and quality-review or training copies require their own disclosed purposes and retention periods rather than indefinite account retention.
Order, refund and complaint records are limited to transaction handling, resolution and applicable obligations. Security logs and consent/request records require a documented security, accountability or legal need, restricted access and expiry. Waitlist records are removed when their purpose ends or consent is withdrawn, except a necessary, permitted suppression or compliance record.
Exact periods or measurable expiry criteria, processor copies and backup schedules must be verified and published before the relevant live collection begins. This purpose outline is not a completed retention schedule.
Privacy complaints and applicable rights
You may ask what personal information is processed, seek correction, withdraw consent, request deletion or raise a complaint with support@sorted.living. Additional rights, including nomination or escalation to an authority, depend on applicable law and whether the relevant provisions are in force. We will explain applicable verification, refusal and escalation processes. Contacting us does not waive a remedy available under law. The responsible privacy contact and response timeframes must be identified in the final notice.
Security
The finalized policy will describe safeguards verified for the production service, including appropriate access restrictions, secure transmission and protection of stored information. No service can guarantee absolute security. This draft does not claim a particular encryption-at-rest implementation, certification or completed security audit. Report suspected account misuse to support@sorted.living; do not include credentials.
Security incidents
Security arrangements must cover authentication, access restrictions, staff and provider access, secure credential handling, logging and appropriate protection of stored and transmitted information. Suspected incidents must be investigated, with notifications to affected people and authorities where required. Report suspected misuse to support@sorted.living without including passwords or payment credentials. A public statement does not replace operational controls; no certification or completed audit is asserted here.
Eligibility and policy changes
The India-only beta is intended for adults aged 18 or over. Contact us if a child’s information has been submitted. Material changes to data practices will be explained before the new use begins, with renewed consent where required. The final policy will identify the responsible operator, their service address and applicable privacy or grievance contact.
Children, language and policy versions
Adults should not create child profiles or invite children into an adult-only beta. If we learn that a child’s information was collected without a permitted basis, we will address it through the applicable restriction and deletion process. A household owner cannot waive a child’s protections. Feature notices should be understandable to their users, including callers using the supported languages.
The date shown on this draft is its revision date, not a declaration that live processing has begun. Material changes will be explained with any required notice and fresh consent. A later edit does not retroactively authorize a new purpose. Applicable versions and choices must be recorded when a live feature is introduced.