● Independent Android studio · Ontario

Independent apps. Built with purpose.

Alam Development Labs creates focused Android experiences that are useful, approachable and made to fit real life.

Our apps

Explore our Android apps.

Built independently with care, clarity and a focus on everyday usability.

Mature 17+

Grow Boss

A detailed Android grow log for keeping plant records, images and notes together.

  • Record every plant
  • Build grow logs with images
  • Keep detailed grow information
Explore Grow Boss →
Mature 17+

WeedStash

A medical cannabis companion for tracking strains, daily consumption, treatment results and spending.

  • Track strains and effects
  • Log consumption sessions
  • Review personal insights
Explore WeedStash →
About the studio

Small studio. Thoughtful software.

Alam Development Labs builds thoughtful iOS and Android experiences and trains AI models, with a focus on clarity, reliability, and practical real-world value.

SharozLead iOS/Android Mobile & AI Developer
Ontario, CanadaIndependent local studio
Android focusedAvailable through Google Play
Direct supportHelp from the developer
Support

Need help with an app?

Visit our developer profile for app information and support.

Open developer profile ↗
© Alam Development Labs · Ontario, Canada
← Alam Development Labs

Bobo - OpenClaw gog

A private Google reporting connection operated by Alam Development Labs for its authorized business account owner.

Bobo helps the owner review business email, upcoming calendar events and app-performance information, and receive scheduled business briefings.

Read the Google Reporting Privacy Policy →

Contact: [email protected]

← Alam Development Labs

Bobo - OpenClaw gog: Google Reporting Privacy Policy

Effective November 4, 2026.

Who operates this connection

Alam Development Labs operates Bobo - OpenClaw gog as a private business reporting connection for its authorized business account owner. It helps the owner review business email, upcoming calendar events and app-performance information, and receive scheduled business briefings.

Contact: [email protected].

This policy covers the dedicated Google reporting connection and reports produced from it. Separate consumer apps, websites, personal-agent integrations and other Bobo connections may have different data practices and permissions. This connection is not currently offered as a public sign-up service.

Google information accessed

Google sign-in identifies the authorized account and provides permission to read the selected services. Depending on the feature and authorization, the connection can access:

  • Account identity: email address and basic Google sign-in information.
  • Gmail: business message information. The current daily briefing uses recent message subjects, senders and message identifiers; it does not retrieve attachments or full message bodies. The Gmail read-only permission itself can permit broader mailbox reading, so any additional use must remain within the disclosed, authorized business-reporting purpose.
  • Google Calendar: calendar information and event details needed to identify upcoming business events, including event titles and start times.
  • Google Analytics / Firebase Analytics: property and app-stream identifiers and aggregated activity measures, such as active users, new users, sessions, engaged sessions and engagement duration. The current reporting connection does not request individual app users' identities.
  • AdMob: publisher reporting information, such as account identity, reporting currency and timezone. Earnings and advertising-performance reporting is planned but not yet included in the daily collector.
  • Google Cloud Storage / Play reporting: read access has been authorized for connecting business reporting files. The specific Play report bucket and automated report ingestion are not yet connected.

The connection can access only resources permitted by the authorized Google account and granted scopes. Permission does not mean every accessible resource is downloaded.

How the information is used

Information is used to prepare owner-requested business briefings, identify upcoming events, summarize app activity, identify gaps in available reporting and diagnose connection failures. Missing or empty results are distinguished from verified zero activity.

The dedicated reporting connection uses read-only Google permissions. It does not use those permissions to send or modify Gmail messages, edit calendar events, publish app releases, change advertising settings or make purchases.

Alam Development Labs does not sell Google user data, use it for advertising targeting or credit decisions, or use it to train generalized artificial-intelligence models. Google API data is handled subject to the Google API Services User Data Policy, including its Limited Use requirements.

Where information is processed and shared

The current scheduled collector runs on an owner-controlled Mac. It uses Google APIs to retrieve authorized information. Its daily report assembly does not call a cloud AI model.

Reports containing selected email information, calendar information and aggregated business metrics are sent to the owner's approved WhatsApp and Telegram destinations. These messaging providers process and store delivered messages according to their own terms and privacy practices. Delivery through a messaging service means report content is not confined to the Mac.

The surrounding Bobo/OpenClaw environment also supports AI-assisted work. If the owner authorizes a separate AI-assisted business or support task, relevant information may be processed by the configured AI provider, including OpenAI, or by a local model. Such use must be limited to the requested task and comply with applicable Google data-use requirements. The dedicated scheduled collector does not itself perform that transfer.

Human access is limited to the authorized owner and, when expressly authorized for a particular support task, personnel assisting with that task. Access is restricted to what is needed for the task, except where disclosure is required by law or is necessary for security as permitted by applicable rules. Reports are not intentionally published or shared with unrelated recipients.

Storage, protection and retention

Google authorization tokens are stored in a local credential store, separate from the original agent credentials. They are used to maintain authorized access without repeatedly requesting the account password. The reporting connection does not collect or store the user's Google password.

Reports and diagnostic records may remain in local OpenClaw automation history, logs or owner-maintained records. Notification-copy tracking stores delivery timestamps and status. Delivered reports may remain in WhatsApp and Telegram chat history and in provider-managed copies or backups.

There is currently no separately configured fixed automatic deletion period for this reporting connection's retained reports. Records remain until removed through the relevant local or messaging-service controls, or until the applicable service's retention process removes them. Revoking Google access stops future authorized retrieval after credentials cease to be valid; it does not erase reports already stored or delivered.

Local credential controls and restricted account access are used to reduce unauthorized access. The owner is responsible for controlling access to the Mac and messaging accounts. No claim is made that all records are encrypted at rest or that every provider copy can be immediately deleted.

Your choices and deletion requests

The owner may pause the reporting schedules, disconnect a service or revoke the connection's access through Google Account third-party connection settings. Removing permission may make the corresponding reporting feature unavailable.

To request deletion of retained local reports, diagnostic records or stored authorization credentials, contact [email protected]. Copies held in messaging accounts must also be managed through those services. Backups or records subject to legal retention requirements may not disappear immediately. Revoking access and deleting retained data are separate actions.

Changes

This policy will be updated before introducing materially different Google data uses or sharing practices. Additional permission or consent will be obtained when required. The published version will show its effective date and contact information.

Authorization update — November 5, 2026

The refreshed reporting authorization includes Gmail, Calendar and Analytics read-only access, AdMob reporting and basic sign-in information. The earlier Google Cloud Storage / Play reporting permission described above is not included in the refreshed authorization. Play report ingestion remains unconnected.

About this connection · Back to website