Legal Information

gro.now Platform Subprocessor Register

Version 1.0 · Published May 27, 2026

This Register is Annex 3 to the Data Processing Agreement (DPA) of the gro.now platform and is published as a section of the DPA page. The Register contains the list of subprocessors engaged by Pwron LLP for the processing of personal data of Clients and Respondents of the gro.now platform in its capacity as a Processor.


1. General Provisions

1.1. This Register constitutes a list of subprocessors engaged by Pwron LLP (hereinafter the "Company") for the processing of personal data of Clients and Respondents of the gro.now platform in its capacity as a Processor, and forms Annex 3 to the Data Processing Agreement (DPA) concluded by the Company with the Clients of the platform.

1.2. The Register shall apply as the current list of subprocessors as of the date of its publication. Changes to the list of subprocessors (engagement of a new one, removal, replacement) shall be carried out in the manner prescribed by the "Subprocessors" section of the DPA, and shall be reflected in the Register by publishing a new version.

1.3. In the event of a discrepancy between this Register and the provisions of the DPA or instructions of the Clients (Controllers), the DPA and the instructions shall prevail to the relevant extent.


2. Principles of Maintaining the Register

2.1. The Company includes in the Register third-party services that:

  • store, transmit, process, or have access to the personal data of Clients or Respondents of the gro.now platform;

  • are engaged by the Company to process data on behalf of Clients in its capacity as a Processor under the DPA.

    2.2. The Company does not include in the Register (see also Section 4 "Services Outside the Scope of the Register"):

  • services used by the Company as an independent Controller for its own operational activities (accounting, HR, Company's corporate marketing, hiring)—these are governed by the gro.now General Personal Data Processing Policy and a separate internal register of personal data recipients;

  • services that the Client connects independently through the platform interface ("Subprocessors" section of the DPA);

  • development and operational tools without access to production and to the data of Clients / Respondents;

  • one-time contractors without continuous access to the data of Clients / Respondents.

    2.3. The categories of subprocessors correspond to the categories established by the "Subprocessors" section of the DPA:

  • hosting and cloud infrastructures;

  • analytics, monitoring, and event logging;

  • authentication and security systems;

  • notification, mailing, and communication services;

  • technical support and disaster recovery;

  • large language models (LLMs);

  • integrations used on the instruction of the Client (Controller).

Additionally included in the specified categories is a payment processor—applied regarding the billing data of Clients processed by the Company when paying for subscription plans.


3. Register of Subprocessors

3.1. Google Cloud Platform (GCP)

FieldValue
Legal EntityGoogle LLC (US) / Google Ireland Limited
CategoryHosting and cloud infrastructure
PurposeCompute (hosting the backend part of the application and database), persistent disks, IAM, networking, cloud storage
Data RegionFrankfurt, Germany (europe-west3)
Categories of processed dataAll categories of platform data (identification, contact, Activity responses and content, technical, metadata, data of Client's representatives)
Contractual BasisGoogle Cloud Terms of Service + Google Cloud Data Processing and Security Terms
DPA / Privacy / CertificationsDPA: cloud.google.com/terms/data-processing-addendum · Privacy: cloud.google.com/terms/cloud-privacy-notice · Certifications: ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, SOC 1/2/3, PCI DSS, HIPAA-aligned

3.2. Vercel

FieldValue
Legal EntityVercel Inc. (US)
CategoryHosting and cloud infrastructure (application hosting, file storage, CDN, deployment)
PurposeHosting of the gro.now application (frontend / backend functions), edge network, deployment
Data RegionFrankfurt, Germany + Washington DC, USA (multi-region edge). The persistent database of Clients is not stored in Vercel
Categories of processed dataTechnical data, metadata, temporary application data; content passes through edge functions / serverless
Contractual BasisVercel Terms of Service + Vercel Data Processing Addendum
DPA / Privacy / CertificationsDPA: vercel.com/legal/dpa · Privacy: vercel.com/legal/privacy-policy · Certifications: SOC 2 Type II, ISO/IEC 27001

3.3. Firebase Authentication

FieldValue
Legal EntityGoogle LLC (US) — as part of Google Cloud / Firebase
CategoryAuthentication and security systems
PurposePlatform user authentication (including password hashing by the provider); JWT tokens; support for login via Google OAuth
Data RegionGoogle Cloud global infrastructure (Firebase Auth is not region-bound in the standard configuration)
Categories of processed dataIdentification data (email, phone, hashed password, account ID), technical session data
Contractual BasisGoogle Cloud Platform Terms + Firebase Terms of Service + Google Cloud DPA
DPA / Privacy / CertificationsSame as Google Cloud Platform

3.4. Google Gemini API

FieldValue
Legal EntityGoogle LLC (US)
CategoryLarge language models (LLMs)
PurposeAI processing for platform features: generation, translations, sentiment analysis, aggregation of insights
Usage ChannelPaid Gemini API via a Google Cloud project with an active billing account (not Unpaid Services / not the free Google AI Studio quota)
Data RegionGoogle Gemini Developer API does not guarantee regional data localization. In accordance with the Gemini API (Paid Services) terms, Google may store and cache data transitively or temporarily in any country where Google or its agents maintain facilities. Regional data residency guarantees are available for the separate Google Cloud Vertex AI / Gemini Enterprise lineup, which the Company does not use as of the date of approval of this Register
Categories of processed dataActivity content (briefs, questions, responses); limited context for analytics; identification data is transmitted only if it is present in the actual content of the responses
Contractual BasisGemini API Additional Terms of Service (Paid Services) + Google Cloud Data Processing Addendum (business.safety.google/processorterms)
Use of data for model trainingNot used. In accordance with the Gemini API terms regarding Paid Services, Google does not use Company prompts and responses to improve its products or train models; processing is governed by the Google Cloud DPA
DPA / Privacy / CertificationsDPA: business.safety.google/processorterms · Privacy: cloud.google.com/terms/cloud-privacy-notice · Certifications: Same as Google Cloud Platform (ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, SOC 1/2/3)

3.5. Brevo

FieldValue
Legal EntitySendinblue SAS (France)
CategoryNotification, mailing, and communication services
PurposeSending transactional emails to Clients and Respondents
Data RegionSt. Ghislain, Belgium
Categories of processed dataIdentification and contact data of recipients (email, name), content of transactional notifications
Contractual BasisBrevo Terms of Use
DPA / Privacy / CertificationsDPA: brevo.com/legal/termsofuse · Privacy: brevo.com/legal/privacypolicy · Certifications: ISO/IEC 27001:2022

3.6. Rollbar

FieldValue
Legal EntityRollbar, Inc. (USA)
CategoryAnalytics, monitoring, and event logging
PurposeCollection and monitoring of errors in the backend and frontend of the gro.now application
Data RegionUSA (primary infrastructure — AWS)
Categories of processed dataTechnical data (logs, stack traces), limited personal data (if it appears in logs as part of a debugged event)
Contractual BasisRollbar Terms of Service
DPA / Privacy / CertificationsDPA: docs.rollbar.com/docs/data-processing-agreement · Privacy: docs.rollbar.com/docs/privacy-policy

3.7. Stripe

FieldValue
Legal EntityStripe, Inc. (USA) / Stripe Payments Europe, Ltd. (Ireland)
CategoryPayment processor
PurposeProcessing of online payments by Clients, billing, subscriptions
Data RegionUSA
Categories of processed dataIdentification and contact data of payers (name, email); payment data (including card details) — processed by Stripe; Pwron does not store, transmit, or process card data directly; transactional links and references
Contractual BasisStripe Services Agreement
DPA / Privacy / CertificationsDPA: stripe.com/legal/dpa · Privacy: stripe.com/privacy · Certifications: PCI DSS Level 1, SOC 1 Type II, SOC 2 Type II, ISO/IEC 27001
Note (PCI DSS)The processing of payment card data is fully outsourced to Stripe (PCI DSS Level 1). The PCI DSS scope for Pwron is limited to integration controls (transmitting non-sensitive data via a secure channel, storing transaction references without card data).

3.8. Google Workspace

FieldValue
Legal EntityGoogle LLC (US) / Google Ireland Limited
CategoryCorporate communications of the Company; regarding the processing of personal data of Clients and Respondents — used for receiving inquiries at functional addresses legal@gro.now, privacy@gro.now, security@gro.now, abuse@gro.now
PurposeCorporate email, video conferencing, calendar, documents for internal work; receiving inquiries from external parties via the Company's functional channels
Data RegionGoogle Cloud global infrastructure
Categories of processed dataInquiries from external parties via functional addresses (may contain personal data of the sender and third parties); internal corporate correspondence
Contractual BasisGoogle Workspace Agreement + Google Cloud DPA
DPA / Privacy / CertificationsSame as Google Cloud Platform

4. Services Outside the Scope of the Register

The following categories of services and contractors are not included in this Register. This does not indicate their absence from the Company's infrastructure, but rather reflects their legal model.

4.1. Development tools without access to data of Clients / Respondents

GitHub (GitHub, Inc., part of Microsoft Corporation) — used by the Company to store the source code of the gro.now platform, dependency scanning, and security advisories. It contains source code, not Client data or the personal data of Respondents. Under the DPA model, it is not classified as a subprocessor of Clients' personal data; it is mentioned in this section for transparency purposes.

4.2. Services used by the Company as an independent Controller

Services engaged by the Company for its own operational activities (and not on the instruction of the Client)—including accounting and HR services, the Company's corporate marketing, and applicant tracking services during hiring—are not subprocessors within the meaning of the DPA. They process the personal data of the Company's employees, contractors, and counterparties, are governed by the gro.now General Personal Data Processing Policy, and are subject to a separate internal register of personal data recipients, which the Company maintains separately from this Register.

4.3. Services connected independently by the Client

Services that the Client connects independently via the platform interface ("Subprocessors" section of the DPA) are not included among the Company's subprocessors; the responsibility for their compliance with applicable requirements is borne by the Client as a Controller.

4.4. One-time contractors without continuous access

One-time contractors and consultants engaged by the Company without continuous access to the data of Clients / Respondents are not included in the Register. Their interaction with data (if necessary as part of a one-time assignment) is formalized through a separate NDA / contractor agreement with applicable processing requirements.


5. Changes to the Subprocessor List

5.1. The engagement of a new subprocessor, the removal of an existing one, or a replacement shall be carried out in the manner prescribed by the "Subprocessors" section of the DPA. Notifications to Clients regarding such changes shall be sent by the Company in the manner and within the timeframes stipulated by the DPA.

5.2. This Register shall be updated upon any change in the list of subprocessors. The version and date of the update are indicated in the header of the document; previous versions are retained in the Company's archive.

5.3. The Director of the Company is responsible for maintaining the Register up to date. The physical inventory of subprocessors is conducted with the assistance of the Company's development team.


6. Validity and Revision

6.1. The Register enters into force on the publication date indicated in the header of this document.

6.2. The Register shall be revised:

  • upon changes to the list of subprocessors;

  • upon material changes to the Company's DPA requiring an update to Annex 3;

  • based on the results of an internal review of the data's relevance.

    6.3. The version and publication date of the current edition of the Register are specified in the header of this document. Previous editions are retained in the Company's archive and, if necessary, provided to Clients upon request.