{"id":858,"date":"2025-10-22T19:38:44","date_gmt":"2025-10-23T00:38:44","guid":{"rendered":"https:\/\/payments.rembrr.net\/?page_id=858"},"modified":"2025-12-20T16:25:42","modified_gmt":"2025-12-20T21:25:42","slug":"politica-de-datos-google-api","status":"publish","type":"page","link":"https:\/\/payments.rembrr.net\/en\/politica-de-datos-google-api\/","title":{"rendered":"Google API Data Policy"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t
\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

COMPLIANCE WITH THE GOOGLE API SERVICES USER DATA POLICY<\/strong><\/p>

Google API Services User Data Policy Compliance
REMBRR INC. \u2013 Port Charlotte, Florida, USA.
Privacy and Compliance Office \u2013\u00a0privacy@rembrr.com<\/a><\/p>

  1. General Statement<\/strong>
    This policy describes how REMBRR INC. accesses, uses, stores, and protects Google user data through OAuth 2.0 integrations.

    The text published in\u00a0https:\/\/rembrr.com\/politica-de-datos-google-api\/<\/a>\u00a0it is exactly the same as the one shown on the OAuth consent screen and in Google brand verification.<\/p>

    REMBRR fully complies with the Google API Services User Data Policy, the Google Workspace Developer Policy, and all steps of the OAuth Verification and Brand Verification process required for the Gmail, Drive, and Calendar APIs.<\/p><\/li>

  2. Accessed Data<\/strong>
    With the user's explicit consent, REMBRR INC. may request the minimum OAuth 2.0 scopes necessary to provide synchronization and productivity features between the user's Google account and the REMBRR platform.
    The data categories accessed are strictly limited to:
    Basic profile: name, email, and profile picture, used solely for authentication.

    Google Drive: view, create, and update files and metadata exclusively within the REMBRR workspace chosen by the user to link.<\/p>

    Google Calendar: read and create events for calendar synchronization.
    Gmail (metadata only): subject, sender, recipient, and time, used exclusively for notifications or user-requested automations. REMBRR never reads, stores, or analyzes message content.
    Google Tasks \/ Google Keep (metadata only): titles and timestamps of notes or tasks if the user voluntarily connects them.<\/p>

    No other Google user data is accessed, stored, or analyzed, including message content, attachments, or contacts.<\/p><\/li>

  3. Data Usage<\/strong>
    The data obtained from Google is used exclusively for:
    Authenticate the user and manage secure sessions.

    Synchronize Drive files, Calendar events, Tasks, and notes within the user's workspace.<\/p>

    Provide the requested functions and maintain service reliability.
    Google API data is never used for advertising, behavioral profiling, or resale.<\/p><\/li>

  4. Data Sharing<\/strong>
    REMBRR does not share Google user data with third parties, except:
    With infrastructure or authentication providers that support the secure operation of the system and are subject to strict confidentiality agreements.
    When required by law or a court order.
    All treatment is carried out in strict compliance with the Google API Services User Data Policy and the OAuth Limited Use Requirements.<\/li>
  5. Storage and Protection<\/strong>
    Encryption in transit (TLS 1.3) and at rest (AES-256).
    Stored exclusively on secure servers located in the United States.

    Protected using multi-level controls: RBAC, MFA, audit logs, and account-level isolation.<\/p>

    REMBRR does not export Google data to external analytics or advertising systems.<\/p><\/li>

  6. Retention and Disposal<\/strong>
    Data from Google integrations is retained only as long as the user maintains an active connection.
    When the user disconnects or requests deletion:
    OAuth tokens and all associated information are revoked and permanently deleted within a maximum of 30 days.
    Backup copies with residual data are automatically deleted in the next maintenance cycle, no later than 45 days.
    The user can verify the deletion by writing to\u00a0    support@rembrr.com<\/a>\u00a0or via \/delete-data-request.<\/li>
  7. User Control<\/strong>
    The user can revoke REMBRR's access to their Google data at any time by visiting     https:\/\/myaccount.google.com\/permissions<\/a>.
    You may also request access, portability, or deletion directly at\u00a0    info@rembrr.com<\/a>\u00a0or through \/user-data-rights.<\/li>
  8. Transparency in the Connection Flow<\/strong>
    During Google sign-in or when connecting Drive, Calendar, Gmail, Tasks, or Keep, the user sees the following notice:
    \u201cBy signing in with Google or connecting a Google service, you accept REMBRR's Privacy Policy and Terms of Use.\u201d
    The message includes links to \/politica-de-privacidad, \/terminos, and \/user-data-rights.<\/li>
  9. Compliance Commitments<\/strong>
    REMBRR INC. certifies that:
    This policy is reviewed annually or whenever Google updates its API Services User Data Policy.
    Security controls follow the NIST SP 800-53 and ISO\/IEC 27001 frameworks.
    Every engineer with access to OAuth data receives privacy training and signs confidentiality agreements.
    A Data Protection Impact Assessment (DPIA) is maintained for the Gmail, Drive, and Calendar scopes.
    Users are notified of any substantial changes at least 7 days before they take effect.<\/li>
  10. Google Data Privacy Contact<\/strong>
    Privacy and Compliance Office \u2013\u00a0    privacy@rembrr.com<\/a>
    REMBRR INC.
    23087 Langdon Avenue, Port Charlotte, FL 33954, USA.<\/li>
  11. Last updated October 14, 2025.
    This version supersedes all previous ones and is identical to the text submitted for OAuth verification in the Google Cloud Console.<\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

    CUMPLIMIENTO DE LA POL\u00cdTICA DE DATOS DE USUARIO DE LOS SERVICIOS DE API DE GOOGLE Cumplimiento de la Pol\u00edtica de Datos de Usuario de los Servicios de API de GoogleREMBRR INC. \u2013 Port Charlotte, Florida, EE. UU.Oficina de Privacidad y Cumplimiento \u2013\u00a0privacy@rembrr.com Declaraci\u00f3n GeneralEsta pol\u00edtica describe c\u00f3mo REMBRR INC. accede, utiliza, almacena y protege los […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"elementor_header_footer","meta":{"footnotes":""},"class_list":["post-858","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/pages\/858","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/comments?post=858"}],"version-history":[{"count":16,"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/pages\/858\/revisions"}],"predecessor-version":[{"id":1923,"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/pages\/858\/revisions\/1923"}],"wp:attachment":[{"href":"https:\/\/payments.rembrr.net\/en\/wp-json\/wp\/v2\/media?parent=858"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}