BookBy Beta Privacy Notice

1. Information BookBy processes

Depending on what you connect or submit, BookBy processes:

• Owner account information, such as name, email, password hash, sessions, and consent receipts.
• Property configuration, operating goals, constraints, and dashboard preferences.
• Encrypted provider credentials and verified connection metadata.
• Normalized reservation facts, such as stay dates, booking date, status, channel, revenue, guest count, and classification.
• Calendar, pricing, availability, preference, and aggregate market evidence returned by authorized providers.
• Execution receipts, capability health, model and tool versions, feedback, and optional screenshots.
• Limited security information, such as privacy-protected request evidence, login attempts, and timestamps.

2. Information BookBy avoids retaining

Historical imports are parsed to normalized reservation facts and the raw file is discarded. BookBy's importer ignores guest names, guest email addresses, guest phone numbers, and raw reservation identifiers. Credentials are encrypted and are not placed in Claude or ChatGPT conversations.

Do not upload information that BookBy does not request.

3. How information is used

Argo uses beta information to:

• Authenticate the owner and isolate the private property workspace.
• Connect authorized services and refresh permitted evidence.
• Build owner-approved operating memory, analysis, dashboards, and receipts.
• Secure, diagnose, maintain, and evaluate the beta.
• Respond to owner requests and feedback.
• Develop generalized product improvements only within the owner's recorded learning choice.

4. Models and service providers

When you connect Claude or ChatGPT, your chosen model provider receives the normalized summaries and tool results needed for that conversation under your account with that provider. BookBy does not send saved provider credentials or raw historical uploads through the connector.

Argo may use infrastructure, database, storage, email, security, and integration providers to operate the beta. They receive only the information reasonably needed for their role and are subject to their own contractual and legal obligations.

5. Sharing and sale

Argo does not sell beta owner or property data. Argo does not disclose one owner's private data to another owner. Information may be disclosed when the owner directs it, when needed for an authorized connected service, to protect the beta or its users, or when required by law.

6. Security

BookBy uses tenant-scoped access, encrypted credentials, hashed passwords and sessions, access limits, and capability boundaries. No system is perfectly secure. Notify Argo through the invitation channel if you suspect unauthorized access, and revoke affected connectors or provider credentials promptly.

7. Retention, export, and deletion

Argo retains beta data while the evaluation is active and for a reasonable period needed for security, recovery, legal obligations, and closing the pilot. You may request a continuity export, disconnection, or deletion through the private portal or invitation channel.

A verified deletion request will be processed within a reasonable period. Limited consent, security, dispute, and legal-compliance records may be retained when necessary. Residual encrypted backups may age out through normal backup cycles.

8. Your choices

You may disconnect Wheelhouse, revoke the private model connector, stop importing data, opt out of general product learning, request an export, or end the evaluation. Ending a model connection does not automatically delete the private BookBy workspace.

9. Changes and contact

If this notice materially changes, BookBy will identify a new version and request any legally required acknowledgement or consent. Privacy questions, access requests, and deletion requests may be submitted through the private BookBy feedback control or the email channel used for your invitation.