Google API and Microsoft API Data Usage Policy

MICROSOFT API SERVICES USER DATA POLICY COMPLIANCE

Compliance with the Data Policy of the Microsoft API Services
REMBRR INC. – Port Charlotte, Florida, USA.
Privacy and Compliance Office – privacy@rembrr.com

  1. General Statement
    This policy describes how REMBRR INC. accesses, uses, stores, and protects user data obtained through Microsoft APIs, including Microsoft Graph, via OAuth 2.0-based integrations.

    The text published on the REMBRR website and store is consistent with the information presented during the OAuth consent flows and application review processes required by Microsoft.

    REMBRR fully complies with the Microsoft API Terms, the Microsoft Graph Data Protection Policy, the privacy policies of Microsoft Entra ID, and the requirements applicable to applications that access Microsoft 365 data.

  2. Accessed Data
    With the user's explicit consent, REMBRR INC. may request only the minimum Microsoft OAuth 2.0 scopes necessary to provide productivity, automation, and synchronization features between the user's Microsoft account and the REMBRR platform.

    The categories of data that can be accessed are strictly limited to:

    Basic profile: name, email address, and profile picture, used exclusively for authentication and identity management.

    Microsoft OneDrive: view, create, and update files and metadata only within the workspace that the user chooses to link to.

    Microsoft Outlook / Calendar: read and create calendar events for schedule synchronization.

    Outlook Mail (only metadata): subject, sender, recipient, and timestamps, used exclusively for notifications or automations requested by the user.

    REMBRR never reads, stores, or analyzes the content of the messages.

    Microsoft To Do / Planner (only metadata): task titles and time stamps if the user connects them voluntarily.

    No other Microsoft user data, including email content, attachments, or contacts, is accessed, stored, or analyzed, except with the explicit and specific authorization of the user in accordance with Microsoft policies.

  3. Data Usage
    The data obtained through Microsoft APIs is used exclusively for:

    Authenticate the user and manage secure sessions.

    Synchronize files, events, tasks, and reminders within the user's environment.

    Provide the requested functions and maintain the reliability and security of the service.

    Microsoft APIs data is never used to:

    – Advertising.
    – Behavioral or commercial profiling.
    – Resale or transfer for purposes other than those authorized.

  4. Data Sharing
    REMBRR does not share Microsoft user data with third parties, except in the following cases:

    Infrastructure providers, authentication or security that support the operation of the system and are subject to strict agreements on confidentiality and data protection.

    When a legal obligation, applicable regulation or judicial order requires it.

    All processing is carried out in strict compliance with Microsoft's data protection policies and limited use principles.

  5. Storage and Protection
    The data obtained through Microsoft APIs are:

    – Encrypted in transit using TLS 1.3.
    – Encryption at rest using AES-256.
    – Stored exclusively on secure servers located in the United States.

    REMBRR applies multi-level security controls, including:

    – Role-based access control (RBAC).
    – Multi-factor authentication (MFA).
    – Audit logs.
    – Logical isolation on a pay-per-use basis.

    REMBRR does not export Microsoft data to external analytics or advertising systems.

  6. Retention and Disposal
    The data from integrations with Microsoft is retained only as long as the user maintains the connection active.

    When the user disconnects the integration or requests the deletion of their data:

    - OAuth tokens and all associated information are permanently revoked and deleted within a maximum of 30 days.

    – The backup copies with residual data are deleted automatically in the next maintenance cycle, no longer than 45 days.

    The user can verify the deletion by typing to or support@rembrr.com using /delete-data-request.

  7. User Control
    The user can revoke REMBRR's access to their Microsoft data at any time by visiting the permissions of their Microsoft account: https://account.microsoft.com/privacy

    You can also request access, portability, or deletion of data by writing to info@rembrr.com or through /user-data-rights.

  8. Transparency in the Connection Flow
    During sign-in with Microsoft or when connecting services such as OneDrive, Outlook, Calendar, or To Do, the user sees the following warning:

    “By logging in with Microsoft or connecting to a Microsoft service, you accept the REMBRR Privacy Policy and Terms of Use.”

    This message includes direct links to the privacy policy / terms / user-data-rights.

  9. Compliance Commitments
    REMBRR INC. certifies that:

    This policy is reviewed annually or whenever Microsoft updates its API policies.

    Security controls follow the NIST SP 800-53 and ISO/IEC 27001 frameworks.

    All staff with access to OAuth data receive training in privacy and sign confidentiality agreements.

    An Impact Assessment on Data Protection (DPIA) is maintained for the scopes used by Microsoft Graph.

    Users are notified of any substantial changes at least 7 days before they take effect.

  10. Microsoft Data Privacy Contact
    Privacy and Compliance Office – privacy@rembrr.com
    REMBRR INC. 23087 Langdon Avenue
    Port Charlotte, FL 33954 – United States
  11. Last update: October 14, 2025.
    This version replaces all previous versions and is consistent with the text presented during the OAuth consent and application review processes of Microsoft.