Last updated September 12, 2026
Privacy Policy
This policy describes Remz's current friends-beta data practices, including exactly how connected Google and Microsoft mailbox access is used.
1. Scope and who we are
This Privacy Policy explains how the Remz early-access service ("Remz," "we," or "us") collects, uses, stores, and shares information. Remz is maintained by the Remz team. Questions or deletion requests can be sent to contact@lxcommercialcleaning.com.
This policy applies to the Remz website, authenticated workspaces, contact-management tools, connected email features, local PDF scrubber, and beta feedback tools.
2. Information you provide
We process information you enter or upload so Remz can provide the features you choose to use.
- Account and workspace information, such as your name, email address, company or workspace name, and role.
- Contact records, notes, custom fields, activities, files, and import data that you add to your workspace.
- Email drafts, personal script and voice preferences, and sent-message records, including sender, recipient, subject, message body, status, and timestamps.
- Support or beta feedback that you choose to copy or email to us.
3. Local PDF scrubber
The PDF Mapper & Statement Scrubber v1 processes the source PDF and builds the sanitized PDF locally in your browser. Remz does not upload or store either file as part of this tool. Closing or clearing the browser view removes the in-memory working copy, subject to ordinary browser memory behavior and any downloads you chose to save.
Automatic detection may miss sensitive information or flag harmless values. You are responsible for reviewing every page and selected redaction before sharing the sanitized result. Image-only PDFs and OCR are not supported in v1.
4. Google and Microsoft account data
When you connect a mailbox, Remz receives basic account identity information and authorization credentials from the provider. Provider credentials are encrypted and stored server-side; they are not exposed to the browser after connection.
For Google accounts, Remz requests basic identity scopes and the least-privilege Gmail send scope. Remz uses this access only to identify the connected sender and send messages that you compose and deliberately submit. Remz does not request permission to read, download, or scan your Gmail inbox.
For Microsoft accounts, Remz requests basic profile access, offline access, and permission to send mail that you deliberately submit.
Remz's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
5. How we use information
We use information only as reasonably necessary to:
- Authenticate users and operate isolated workspaces.
- Provide contact, import, local PDF scrubbing, document, draft, connected-mailbox, sending, and history features.
- Secure the service, prevent abuse, diagnose failures, and provide requested support.
- Improve user-facing Remz functionality using product feedback and service performance information.
6. What we do not do with Google user data
We do not sell Google user data, use it for advertising, provide it to data brokers or information resellers, use it to determine creditworthiness or lending eligibility, or use it to train generalized or non-personalized artificial-intelligence or machine-learning models.
We do not allow people to read Google user data except when necessary for security, legal compliance, user-requested support with consent, or internal operations permitted by Google's policies.
7. When information is shared
We may share information with cloud hosting, authentication, database, storage, monitoring, and email providers only as needed to operate user-facing Remz features. We may also disclose information when required by law or when necessary to protect users and the service.
We do not sell personal information. We do not transfer Google user data for advertising, data brokerage, credit, lending, or unrelated purposes.
8. Storage, security, and workspace separation
Remz uses access controls intended to keep each organization's records separate. Connected-mailbox credentials are encrypted server-side, sensitive provider secrets are not placed in browser-visible configuration, and database access is restricted by authenticated workspace membership.
No service can guarantee absolute security. During the friends beta, use only test or low-sensitivity business data and report any suspected unauthorized access immediately.
9. Retention, disconnection, and deletion
We retain account and workspace information while the account is active and as needed to provide the service, resolve disputes, prevent abuse, and meet legal obligations. Retention can vary by data type and backup lifecycle.
Disconnecting a mailbox deletes Remz's stored access and refresh credentials. Existing sent-message history remains in the workspace so the user has an accurate business record. The user may separately revoke Remz from the provider's account-security settings.
You may request deletion of your Remz account or workspace data by emailing contact@lxcommercialcleaning.com from the account address. We may need to verify the request and may retain limited information where legally required or necessary for security and fraud prevention.
10. Your choices
You can choose what contact data to enter, disconnect a mailbox, delete or restore supported records, clear locally saved beta-feedback drafts, and request access, correction, export, or deletion by contacting us. Rights can vary by location.
11. Children, changes, and contact
Remz is a business service and is not directed to children under 13. We may update this policy as the product changes. We will update the date on this page and provide additional notice when appropriate.
Privacy questions and requests: contact@lxcommercialcleaning.com.
This friends-beta policy reflects the product's current behavior. It should be reviewed by qualified counsel before Remz expands beyond trusted beta testers or begins handling regulated or highly sensitive data.