Privacy Policy
Last updated October 28, 2026
How UBUYBOX handles information, including ROS records, Google services and AI-assisted analysis.
1. Who this policy covers
This Privacy Policy explains how UBUYBOX INC. handles personal information in connection with the UBUYBOX website, UBUYBOX ROS, inquiries, approved access and related services. It applies to UBUYBOX’s processing. Independent partners may have their own notices for their services; common branding does not mean every partner may access your records.
2. Information processed
Depending on the service, records can include your name, email, phone, business affiliation, role, account identifiers, access requests, approval status, messages and documents you submit. Opportunity records may contain property and business details, owner contact information, financial estimates and project descriptions. Technical services can process IP addresses, browser/device information, timestamps, usage and security events. Billing providers process information entered into their own payment interfaces under their notices.
3. How information is used
Information supports inquiries, authentication, account administration, eligibility and access review, opportunity organization, requested analysis, reporting, service communications, billing records, troubleshooting, fraud prevention and legal obligations. Marketing choices are separate from necessary service messages. Providing information is not unrestricted permission for unrelated partner marketing.
4. Google Sheets, Drive and ROS
ROS uses UBUYBOX’s centrally managed Google Sheets workbook and designated Google Drive documents. Partners do not need to connect their own Sheets or Drive accounts for this workflow. Personal information in those records remains subject to this policy even though UBUYBOX manages the Google account. ROS reads workbook information and supports backend write requests, analysis and report generation. Some workflows also use local application records; the workbook is not the only storage location.
5. Google authorization and permissions
ROS uses Firebase Authentication. Its current sign-in integration requests Google Sheets read/write and read-only permissions and Google Drive read/write and read-only permissions. These broad permissions can authorize more access than the intended central-workbook workflow needs. Designating documents does not technically narrow a broad Google permission to those documents. Users should review the permissions displayed by Google before consenting. A Google permission grant does not by itself authorize UBUYBOX to use data for unrelated purposes.
6. Google user-data restrictions
Use and transfer of information received from Google APIs must adhere to the Google API Services User Data Policy, including applicable Limited Use requirements. This includes the applicable restrictions on transfers, human access, advertising, sale, generalized AI-model training and creditworthiness or lending uses. General partner-sharing or AI language in this notice does not override those restrictions. A privacy notice does not itself establish that a particular integration has passed Google verification.
7. Where information is stored
The reviewed ROS application uses Google services, application-server storage and browser storage. Browser local storage can retain account/workspace preferences and operational records. Server JSON files can retain intake records, analysis, report metadata and identifiers used to hide access requests; generated reports are stored on the server. The application’s own Google OAuth token cache is held in memory, while Firebase manages its authentication state separately. Signing out is not the same as erasing all browser or server records.
8. Service providers and partner access
Google/Firebase provides relevant authentication and Google data services. Hosting, communication, support, payment and analytics providers process information needed for their respective functions. Requested referrals or opportunity review may involve the relevant operator or partner, consistent with the collection notice, applicable agreements and consent requirements. Independent partners are responsible for their own processing. Information may also be disclosed for lawful obligations, security or a lawful business transfer, subject to applicable restrictions, including those on Google user data.
9. AI-assisted analysis
ROS includes analysis through DigitalOcean inference when configured and invoked. Selected property/project inputs can include location, asset identifiers, estimated values or budgets, project descriptions, sponsor/developer information and other analysis inputs. Outputs are saved with application records and can support reports. The source’s default model identifier is openai-gpt-oss-20b; the model and endpoint are configurable. That model name alone does not mean information is sent to OpenAI. Provider processing is subject to the configured service and its terms. UBUYBOX does not represent here that provider processing has zero retention. AI outputs require human review and do not constitute transaction approval or verified professional findings.
10. Browser storage, analytics and external services
ROS uses browser local storage for functionality and cached records. Cloudflare Web Analytics is used for aggregate website usage and performance reporting. Embedded media and linked services can cause your browser to contact their providers. Their notices govern their own processing. You can manage browser storage through browser settings, although clearing it may affect the service. No claim is made that every UBUYBOX or partner page uses identical tracking technology.
11. Retention and deletion
The reviewed ROS application has no automatic expiry schedule or comprehensive erasure workflow. Records and reports may remain until separately removed. The current access-request deletion feature hides records through a suppression list; it does not establish erasure from the workbook, cached copies, reports or backups. Contact contact@ubuybox.com to request review and deletion of your information. Requests must account for relevant copies and applicable legal or contractual retention obligations. Signing out does not automatically delete those copies. Clearing browser site data affects that device, not server or workbook records.
12. Your choices and rights
Email contact@ubuybox.com with the subject “UBUYBOX Privacy Request” to request access, correction or deletion, raise a concern, or exercise rights available under applicable law. Identity verification may be necessary and should be proportionate to the request. Applicable rights can include a copy of data, restriction, objection, withdrawal of consent, certain opt-outs, appeal or a complaint to a regulator. Exceptions may apply to legally required records. Use the unsubscribe option in promotional email to stop that marketing; necessary account and security notices may continue.
13. Revoking Google access
The Google account holder can revoke the ROS connection using Google Account third-party connection controls. Revocation affects future authorized API access; it does not automatically erase records already stored by UBUYBOX. Partners whose records are held in the central workbook can contact UBUYBOX without connecting a personal Google account.
14. Security, children and processing locations
No system can guarantee absolute security. Do not submit passwords, payment-card details or government identifiers through general chat or contact forms. The business platform is intended for adults and is not directed to children under 13; contact us if you believe a child supplied information. Providers may process information outside your location. Specific server regions, backup schedules and provider retention periods are not represented in this notice.
15. Updates and contact
Changes will be reflected in the date on this page. Material changes require appropriate notice and consent where applicable before new processing begins. Privacy contact: UBUYBOX INC., contact@ubuybox.com.