Privacy Policy
Last updated October 15, 2026
Biblo is a personal assistant you can use through messaging, our website, and our companion app. It helps you remember information, plan, manage connected accounts, and carry out authorized tasks. This policy explains what information we handle, why we handle it, who can access it, and your choices.
“Biblo,” “we,” and “us” mean Data Foundry Ai Inc, a Delaware corporation, operating as Biblo. Our mailing address is 434 Minna Street #1102, San Francisco, CA 94103, United States. Privacy questions and requests go to privacy@heybiblo.com.
The service is initially offered in the United States. Some features described below may not yet be available. We collect feature-specific information only when the feature is available and you use or enable it, subject to the permissions and consent it requires. Describing a possible feature here does not activate it or authorize unrestricted collection.
Our separate Consumer Health Data Privacy Notice explains our handling of consumer health data. Its more protective rules, and the Google-specific rules below, control over more general statements in this policy. A privacy notice is not a substitute for a separate consent where one is required.
What we collect
The information we receive depends on what you send, the tasks you request, and the accounts and permissions you enable.
- Account and contact information. Your phone number, name, email address, account identifiers, eligibility information you provide, authentication information, and communication preferences. We receive these from you, your sign-in provider, or the messaging service.
- Messages and submitted content. Your conversations with Biblo, its replies, uploaded photos, screenshots, files, voice messages and transcripts where supported, and the metadata accompanying that content.
- Personal context and memory. Preferences, goals, addresses, relationships, plans, reminders, routines, and summaries or inferences created from information you provide or authorize us to access. Inferences may be wrong; you can ask to see, correct, or delete them.
- Connected-account information. Permitted email and attachments, calendars, contacts, documents, cloud files, merchant-account information, reservations, receipts, and, for supported financial connections, account details, balances, and transactions. We receive only the information accessible through the permissions you grant.
- Health and fitness information. Meals, nutrition estimates, height, weight, exercise, sleep, activity, goals, wearable measurements, and other health information you choose to provide or permit through an enabled feature. See the separate health notice for categories, purposes, sharing, and rights.
- Photos and device information you permit. Selected photos or permitted library content and associated metadata, calendar or contact entries, and other specifically enabled device data. Sending one photo does not give us access to your entire library.
- Location. Locations or addresses you share, approximate location from technical information such as an IP address, and precise or background location only for an enabled feature with the required device permission and consent.
- Credentials and payment information. OAuth tokens, authorized account sessions, sign-in credentials, card and billing details, payment tokens or saved payment references, and transaction records that you provide through supported connection, vault, or payment features. The information collected depends on the feature and the payment or account provider involved.
- Task and authorization records. Requested actions, proposals, approvals, standing instructions, permission changes, order and booking confirmations, merchant charges, cancellations, and execution results.
- Technical and usage information. IP address, device and browser information, cookie or similar identifiers, delivery records, feature usage, referral information, error reports, and security logs.
Connected content may include information about other people. Provide it only when you have the authority to do so and it is necessary for your task. Connecting contacts does not authorize us to market to those people.
Google user data
Connecting Google is optional. We request the permissions needed for the Google features you enable through Google’s authorization process, with an explanation of how the information will be used. We do not request access solely for features that have not been implemented.
What Biblo asks for and why
- Gmail. Read relevant messages, metadata, and attachments; summarize information; recognize appointments, bills, purchases, deliveries, and travel; organize mail; prepare drafts; and send messages within your authorization. A sending permission alone is not permission to send any message we choose.
- Google Calendar. Read events and availability, provide reminders, and create, update, or cancel events you authorize.
- Google Contacts. Read contact details to resolve the people you mention and support the communications you authorize. Contacts are not used to build an advertising audience.
- Google Drive and files. For enabled document features, access the files or file categories covered by your permission to search, summarize, or organize them, and create or edit files when the granted scope and your instruction permit it. Access is not automatically granted to your entire Drive.
- Google account identity. Identify and display the account you connected and associate the connection with your Biblo account.
Read access, data processing, and permission to take an external action are different permissions. The approval rules in our Terms of Service, any specific authorization you give, and applicable platform requirements govern external actions.
How Google data is used
We use Google data only for the enabled, disclosed, user-facing features and permitted improvements to those features. Relevant content may be processed by contracted AI and infrastructure providers to deliver those features, subject to required disclosures and consent.
We do not sell Google data; use it for advertising or retargeting; use it to determine creditworthiness or for lending; or use or retain it to develop, improve, or train generalized or other users’ AI or machine-learning models. These restrictions follow the information into summaries, inferences, and other derived data.
Human access to Google data is restricted. People may read identifiable Google data only with your documented affirmative agreement to view specific messages, files, or other data; when necessary for security, including investigating a security-relevant bug or abuse; or when required by law. Properly aggregated and anonymized information may be used for permitted internal operations. General acceptance of our terms or this policy is not permission for unrestricted employee review of your inbox or Google-derived conversations.
How Google data is stored and shared
We protect Google credentials with encryption and access controls. We store only content, authorized task records, and derived context needed for permitted features, subject to applicable API storage and caching restrictions. We do not maintain an unrestricted permanent copy of your Google account.
Transfers are limited to permitted, consented service delivery and improvements, necessary security purposes, legal requirements, or a corporate transaction after obtaining your explicit prior consent. Our employees, contractors, processors, and successors must respect the Google-specific restrictions.
When we receive and authenticate a disconnection request, we disable further access through that connection and start deleting stored credentials, connected content, and source-derived memory under the retention rules below. Revoking access directly through Google prevents new authorized access; you can also contact us to request deletion of existing copies. Information you independently provided may remain unless you request its deletion too.
Biblo’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace user data and developer policy.
How we use information
We use information to answer you, maintain your account and personal context, provide enabled health and planning features, assemble personalized views in the companion app, and carry out authorized actions. With the relevant permissions, we can combine sources to provide the feature you enabled, such as matching a food receipt with your meal log or adapting a plan around your calendar. A restriction on a source continues to apply when sources are combined.
We also use necessary information to send requested reminders and task updates, provide support, investigate failures, prevent fraud and abuse, measure service performance, and meet legal obligations. Optional recurring check-ins and promotional messages have their own consent and opt-out requirements.
AI processing and human review
Biblo uses third-party AI services. Relevant messages, images, files, and connected information may be sent to those services to produce responses or perform tasks. Before a feature shares personal information with a third-party AI provider, we identify the provider and explain the relevant sharing through the feature’s disclosure and consent flow, obtaining permission where required.
We do not use private conversation content, connected-account content, or health information to train generalized AI models, and we require our contracted AI providers not to use that content for generalized model training. This does not mean information is never retained: providers may have limited, contractually controlled retention for service delivery, security, abuse prevention, or legal obligations. Personalizing your own assistant through saved context is different from training a model for other users.
Authorized employees and contractors may review limited conversations and task records for support, safety, debugging, and quality evaluation. Access is restricted by role, purpose, confidentiality obligations, and the information’s source. Identifiable health information is accessed only as necessary for your requested service or another separately authorized, lawful purpose. Optional review beyond those purposes requires the necessary consent. The stricter Google rules above always apply.
Employees and contractors may use internal collaboration, support, and evaluation tools to review conversations and task records for these purposes. The same confidentiality, access, consent, and source-specific restrictions apply to information handled in those tools. You may withdraw an optional consent as described under Your choices.
Advertising and commercial recommendations
We do not sell personal information or share it for cross-context behavioral advertising. We do not use private conversations, health information, Google data, device-library content, or precise location to target advertisements, and we do not provide that information to advertising platforms or data brokers.
We may advertise Biblo without disclosing your personal information. Internal campaign measurement must remain consistent with this policy. If a user-authorized transaction involves a referral fee, commission, or sponsored placement, we disclose the relevant commercial relationship before the recommendation or transaction as appropriate. Such a relationship does not permit otherwise prohibited uses of health, Google, or other restricted information.
Mobile numbers, messaging opt-in information, and consent records are not shared with third parties or affiliates for their marketing or promotional purposes. Necessary messaging providers may process them solely to operate the messaging program; consent is not sold or transferred for another sender’s use.
Who we share it with
We disclose only the information relevant to the purpose below, subject to the stricter rules for health information, Google data, and other restricted sources.
- Hosting, storage, and security providers. Operate and protect the service using necessary account, content, authorization, and technical information.
- AI, search, and browser-automation providers. Process relevant task context and permitted content to answer questions or operate supported websites. Account access is limited to the permissions and authorized tasks involved.
- Messaging and communications providers. Deliver messages, media, and notifications and process related contact information and delivery records.
- Payment processors, account-connection providers, and merchants. Authenticate connections, process authorized payments, and fulfill orders or bookings using necessary payment, contact, delivery, and transaction details.
- Support, collaboration, diagnostics, and analytics providers. Support users, investigate failures, and measure performance using minimized operational information and only those content excerpts permitted under this policy.
- People and services you direct us to contact. Receive the messages, files, appointment details, or other information you specifically authorize us to disclose.
Contracted processors may use information only for authorized purposes and must provide protections consistent with this policy and applicable requirements. Merchants, account providers, carriers, and other services may also act independently for their own service; their separate privacy notices apply to that processing. We do not share your complete personal context with a merchant merely because you place an order.
We may disclose information when legally required or, to the extent permitted by law and applicable source restrictions, necessary to investigate fraud, protect safety, or establish or defend legal claims. We may transfer information in a merger, acquisition, financing, restructuring, or asset sale only under applicable privacy restrictions. In particular, covered Google data requires explicit prior consent for a corporate transfer, and health-data rules are not displaced by this paragraph.
Cookies and online tracking
Our website and app may use cookies, local storage, and similar tools for authentication, security, preferences, and permitted first-party analytics. Contracted providers may receive device identifiers and usage information while performing those functions. We do not authorize them to track your activity across unrelated businesses for their own advertising purposes.
You can control cookies through your browser. Blocking necessary storage may prevent sign-in or other functions. Our commitments not to sell your personal information or use it for advertising apply whether or not your browser sends a “Do Not Track” signal. Where applicable law requires us to recognize an opt-out preference signal, including Global Privacy Control, we honor it for the processing it covers. You can also contact privacy@heybiblo.com about your privacy choices.
An independent website you ask Biblo to visit may use its own tracking technologies. We cannot change that website’s privacy practices, and we limit the information sent to what your authorized task requires.
How long we keep it
We retain information only as needed for the disclosed purpose, your instructions, and applicable legal requirements. We do not keep information indefinitely merely because it could be useful someday.
- Account content and personal memory. While needed for the active features you use, unless you request earlier deletion. Unneeded information is subject to periodic removal.
- Connection credentials and connected content. Until the connection expires, is revoked, or is no longer needed. After an authenticated disconnection request, further access is disabled and deletion of active-system copies and source-derived memories is completed within 30 days, subject to lawful exceptions.
- Routine technical and diagnostic logs. For the period reasonably necessary to operate, secure, troubleshoot, and evaluate the Service, taking into account the sensitivity of the information and applicable legal requirements.
- Transaction, consent, and compliance records. Only the limited records needed for applicable accounting, payment, consent, dispute, or legal-retention requirements. These are restricted to those purposes.
- Deleted information in backups. Removed through backup deletion or expiration processes within applicable legal deadlines. Pending removal, retained copies are restricted to legally permitted purposes. Consumer health data is subject to the additional deletion requirements in our health notice.
After an authenticated account-deletion request, we disable account access and future automated actions and delete active-system personal information within 30 days, except for records we are legally permitted or required to retain. We identify an applicable exception rather than treating “security” or “business needs” as permission to keep everything. Shorter legal deadlines take precedence.
Deletion covers relevant messages, memories, summaries, search indexes and embeddings, cached content, and records held by our processors. We send downstream deletion notices and require deletion where applicable law requires it. Independent merchants may retain records they are legally entitled or required to keep; this does not excuse us or a recipient from a binding deletion obligation.
Your choices
Account and information controls. Ask in chat or email privacy@heybiblo.com to access, correct, export, or delete your information; remove a particular memory; disconnect an account; or withdraw an optional consent. To delete your account, tell Biblo “delete my account,” email privacy@heybiblo.com, or use the account-deletion controls available for your account. We may need to verify that you control the account before disclosing or deleting sensitive information.
Source permissions. You can also revoke Google access through your Google account’s third-party connection settings, and manage Health, Photos, Contacts, and Location permissions in your device settings. Revocation stops future access through the relevant permission; it is different from deleting existing copies. A deletion request can cover both.
Messages and actions. Reply STOP to stop automated Biblo messages to that number, HELP for help, or contact support@heybiblo.com. You may receive one opt-out confirmation. Stopping messages does not delete your account or cancel a merchant transaction or subscription. To revoke standing action authority, tell Biblo which permissions you are withdrawing or contact support@heybiblo.com. A broad opt-out is not bypassed by moving the same messages to another channel.
Additional legal rights. Depending on your location and the law applicable to the processing, you may have rights to confirmation and access, a portable copy, correction, deletion, withdrawal of consent, limits on sensitive-information use, and opt-outs from sale, targeted advertising, or profiling used for legally significant decisions.
You may use an authorized agent where permitted. We request only information reasonably necessary to authenticate a request or an agent’s authority, do not require a new account to exercise rights, and do not unlawfully discriminate against you for exercising them. A feature may stop working when the information genuinely needed for it is removed.
We respond within the period required by applicable law, generally within 45 days of receiving a request. Any permitted extension will be explained within the initial response period. If we deny a request, we explain the reason and any appeal right. You may appeal by emailing privacy@heybiblo.com with “Privacy appeal” in the subject; we respond within 45 days or any shorter applicable period. The separate health notice includes additional rights and regulator-complaint information.
Security and processing locations
We use administrative, technical, and organizational safeguards appropriate to the information, including access controls, encrypted credential storage, and encryption for supported communications between systems we control. We limit production access and apply additional restrictions to sensitive information. No system is perfectly secure.
Do not send passwords, full card numbers, security codes, bank PINs, or wallet recovery phrases through ordinary chat. Use only the secure connection, payment, or vault flow provided for the supported feature. We do not retain card security codes after authorization or for future purchases.
Messaging platforms control the security of their delivery channels. Once your message reaches Biblo, it is processed under this policy; using an encrypted messaging platform does not prevent access by Biblo’s permitted providers or authorized personnel.
Biblo is operated from the United States. Our providers and authorized personnel may process information in other countries, subject to applicable transfer requirements and contractual protections. We do not promise that every copy or every access occurs only in the United States.
Children
Biblo is not intended for anyone under 18. We do not knowingly collect personal information from children who use the Service in violation of this restriction. If you believe a child has provided personal information to Biblo, contact privacy@heybiblo.com so we can take appropriate action, including deletion where required by law.
An eligible adult may provide limited information about another person for a lawful, authorized task, such as a family booking. That does not authorize a child to operate the account or permit unnecessary collection of children’s sensitive information.
Changes
We update this policy when our practices change and revise the effective date. We provide conspicuous notice of material changes through the app, website, email, or permitted messaging before they take effect, except when a shorter period is legally necessary. We obtain additional consent before new collection, sharing, or uses where required. Continuing to use Biblo does not replace a legally required affirmative consent.
Contact
Privacy: privacy@heybiblo.com
Support: support@heybiblo.com
Mail: Data Foundry Ai Inc, Attn: Privacy
434 Minna Street #1102
San Francisco, CA 94103
United States
Biblo