Privacy Policy

2.1 Account Information

When you create an account, we collect:

• Full name
• Email address
• Phone number (optional)
• Professional license number (optional)
• Professional certifications
• Timezone preference
• Biography/professional description (optional)

2.2 Business Information

If you set up a company profile, we collect:

• Company name
• Business address
• Business email and phone number
• Company website
• Company logo

2.3 Inspection Data

When you conduct inspections, we collect:

• Property information: Address, city, province/state, postal code, country, property type, year built, square footage, number of bedrooms/bathrooms
• Inspection details: Observations, saved field notes, descriptions, severity ratings, recommendations, weather conditions, inspection scope
• Consumer/client information: Name, address, phone number, email of property buyers, sellers, or owners
• Realtor information: Name, company, license number, phone, email, website

2.4 Media Files

• Photos and videos: Images and video recordings captured during inspections
• Audio recordings: Voice recordings for transcription purposes (processed transiently; see Section 3.2)
• Annotations: Markup and annotations added to images

2.5 Subscription and Payment Information

• Subscription status and plan type
• Purchase history and entitlements
• Payment processing is handled by RevenueCat together with the Apple App Store/Google Play Store (for in-app purchases) or Stripe (for purchases made directly on our website). We do not directly collect or store credit card numbers or banking information.

2.6 Usage and Analytics Data

• App usage patterns and feature interactions
• Screen views and navigation paths
• Session recordings, where session replay is enabled
• Error logs and crash reports
• Device information, such as device type and operating system version

Screens that display Google Calendar information are excluded from session replay and screen or interaction autocapture. Google Calendar event content and OAuth tokens obtained through Google APIs are not included in analytics events, screen recordings, error logs, or crash reports. We may collect limited non-content interaction information about the Calendar integration, such as whether the integration was connected or whether the Calendar feature was opened, but this information does not include event titles, dates, times, locations, descriptions, attendees, event identifiers, or OAuth tokens. See Sections 2.7 and 3.4.

2.7 Google Calendar Data (Optional)

If you choose to connect your Google Calendar, Bedrock requests read-only access to events on your primary Google Calendar (OAuth scope: calendar.events.readonly).

Depending on the information contained in your calendar events, Bedrock may access:

• Event title
• Event start and end date/time
• Event location
• Event attendee information (name and email, where present on the event)
• Google Calendar event identifiers

Bedrock uses this information to display your Google Calendar events within the App and allow you to select an event to prefill inspection scheduling details. Event title, start/end time, and location are shown in the App's calendar picker and used to prefill a new inspection. Attendee names and email addresses may be used to prefill client or realtor contact information for the inspection. Google Calendar event identifiers may be processed transiently to distinguish and select events but are not saved as part of an inspection.

Google Calendar access is optional. Bedrock cannot create, modify, or delete events in your Google Calendar through this integration.

Bedrock does not retain a separate copy of unselected Google Calendar events after they are retrieved for display. Calendar event data is retrieved live each time you use the integration. If you select a calendar event to prefill a new inspection, the start time and location are imported and parsed into standard property fields (address, city, province/state, postal code, country); if the event includes attendees, attendee names and email addresses may also be imported to prefill client or realtor contact information for the inspection. Information that you select and save as part of an inspection or appointment becomes ordinary Bedrock inspection or scheduling data and is retained according to Section 5.

OAuth access and refresh tokens required to maintain the connection are stored securely and are removed when you disconnect Google Calendar or delete your Bedrock account. See Section 5.4.

3.1 Providing Our Services

• Creating and managing your inspector account
• Generating inspection reports
• Storing and organizing inspection data and media
• Processing subscriptions and managing quotas
• Syncing with your calendar for scheduling

3.2 AI-Powered Features

We use artificial intelligence to enhance your inspection workflow:

• Voice Transcription: Audio recordings are sent to Hugging Face's Whisper service for transcription. Audio files are processed transiently and are not stored by us or the transcription service after processing.

• Content Generation: Transcriptions, saved field notes, inspection notes, existing report content, and other inspection-related text may be processed by Inception AI, Inc.’s Mercury 2 model, which is Bedrock’s primary artificial intelligence provider, to generate polished observation descriptions, implications, recommendations, executive summaries, and other draft report content.

  If Mercury 2 is unavailable, returns an error, or is unable to complete a request, the information may be processed by Cohere as a backup artificial intelligence provider.

  Where our AI service providers make relevant privacy controls available, we use those controls, to the best of our ability, to limit or prevent Bedrock submissions from being used for general model training.

  Saved field notes are stored as inspection data when you save them and may be used in generated reports when polished observation details are not available. Unsaved raw transcription drafts are not persisted in Bedrock’s database. Information submitted to an artificial intelligence provider may still be processed or retained by that provider in accordance with its terms, privacy policy, settings, and any applicable agreement with Kami Labs Ltd.

Google Calendar event data is not sent directly from the Google Calendar integration to AI transcription or content-generation providers. However, if you import Calendar-derived information (such as date, time, or location) into inspection fields and later use AI Autofill, those current form values may be included as context for the autofill request. We do not use Google Calendar data to train, develop, or improve any AI/ML model.

3.3 Analytics and Improvement

• Understanding how users interact with the App
• Identifying and fixing bugs and errors
• Improving features and user experience
• Collecting error and crash information
• Analyzing session replays to identify usability issues, where session replay is enabled

Screens that display Google Calendar information are excluded from session replay and screen or interaction autocapture. Google Calendar event content and OAuth tokens are not included in analytics events, session recordings, error reports, crash reports, or other information sent to our analytics provider. This includes event titles, dates, times, locations, descriptions, attendees, event identifiers, and OAuth tokens. Limited non-content events relating to the Calendar integration, such as whether a user connected or opened the integration, may be collected without including information obtained from the user's Google Calendar events.

3.4 Google Calendar Data Use

Google Calendar data is used only to provide the user-facing calendar and inspection-scheduling feature described in Section 2.7, including prefilling client or realtor contact information from event attendees when you select a calendar event.

Google Calendar data is not used for:

• Advertising or marketing
• Personalized, interest-based, or retargeted advertising
• Data brokerage or resale of information
• Creditworthiness or lending decisions
• Generalized analytics or user profiling
• Building unrelated databases
• Training, developing, or improving generalized artificial intelligence or machine-learning models

Google Calendar event data is not sent directly to Cohere, Hugging Face, or our analytics provider as part of the Calendar integration itself. If you import Calendar-derived information into an inspection's fields and later use AI Autofill on that inspection, those current field values may be included as context for the autofill request to Cohere - this is the same as any other manually entered field value, and is not specific to Calendar data. Event titles, locations, and other Calendar event content are excluded from analytics payloads and session data.

Our infrastructure and database providers process Google OAuth tokens, and any calendar information a user chooses to import into an inspection, solely as necessary to operate the Google Calendar integration and provide Bedrock's user-facing features.

Bedrock does not permit employees, contractors, or other individuals to access Google Calendar event data except: where you have provided explicit consent; where access is required to investigate a security issue; where access is required by applicable law; or where the data has been aggregated and anonymized for internal operations.

3.5 Google API Limited Use Compliance

Bedrock's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3.6 Communications

• Sending service-related notifications
• Responding to support requests
• Providing updates about your subscription

5.1 Active Accounts

We retain your data for as long as your account is active or as needed to provide services. Inspection data, reports, and media are retained indefinitely unless you delete them or your account.

5.2 Account Deletion

When you delete your account:

• Your personal information is removed from our active database
• An anonymized deletion log is created for audit purposes (containing no personally identifiable information)
• Associated media files are deleted from storage
• Data that has been shared with third parties may be retained according to their policies

5.3 Subscription Records

Basic subscription records may be retained for legal and accounting purposes as required by law.

5.4 Google Calendar Data Retention and Deletion

Bedrock retains Google OAuth tokens only while your Google Calendar account remains connected.

When you disconnect Google Calendar:

• Bedrock stops accessing your Google Calendar
• Stored OAuth tokens are deleted
• Future calendar information is no longer retrieved

Calendar event information that has not been imported into Bedrock is not retained as a separate calendar database - it is fetched live and discarded after each request.

Information that you previously selected and saved as part of a Bedrock inspection or appointment (start time, parsed location, and any imported attendee-derived contact information) may remain as inspection or scheduling data until you edit or delete that information, delete the associated inspection, or delete your Bedrock account.

7.1 Access and Portability

You can access your inspection data, reports, and account information directly through the App. You may export your inspection reports as PDF documents.

7.2 Correction

You can update your account information, company details, and inspection data at any time through the App.

7.3 Deletion

You can:

• Delete individual inspections, observations, or media files
• Delete your entire account through the App settings
• Request deletion by contacting us at the email below

7.4 Google Calendar Disconnection

You can revoke Google Calendar access at any time through the App or through your Google Account settings.

7.5 Analytics Opt-Out

Contact us if you wish to opt out of analytics data collection.