Company and privacy

Founder-led, legally clear, and easy to reach.

AgileHR is provided by Viacheslav Sidiachkin, an independent professional (trabalhador independente) registered in Portugal.

The public landing stays intentionally compact, but the trust layer is explicit: direct email contact, Portugal-based legal identity, and public privacy and terms pages that explain how the review, product, and payment path work.

Founder-led by default

AgileHR is provided directly by Viacheslav Sidiachkin, so discovery, diagnosis, and product direction stay close to the real delivery problem.

Portugal-based legal identity

AgileHR is operated from Portugal as an independent professional setup, with public legal identity and tax details available on the site.

GDPR-aligned handling

The current flow is intentionally data-light: CTA logs avoid raw personal data, lead capture is minimized, and product data handling follows GDPR-oriented constraints.

Privacy Policy

Privacy Policy

This Privacy Policy explains how AgileHR handles personal data across the public landing, the booking and lead flow, the product environment, and subscription or payment operations.

Last updated 2026-03-24English onlyPublic trust page

Controller identity and scope

Controller
Viacheslav Sidiachkin
Brand
AgileHR
Privacy contact
slava@agilehr.io
Registered address
1800-031, Lisbon, Avenida de Berlim, 23, apt. 201
NIF
323637825

AgileHR is provided by Viacheslav Sidiachkin, an independent professional (trabalhador independente) registered in Portugal.

This notice applies to the AgileHR public site, landing pages, bottleneck review booking flow, product access paths, support correspondence, and subscription/payment operations that reference AgileHR.

AgileHR does not currently designate a separate public Data Protection Officer. Privacy questions can be sent to the contact email listed below.

How AgileHR processes data in practice

AgileHR tries to keep public-site data collection narrow. For example, CTA logging does not store raw email addresses, and the lead capture integration hashes the submitted email before it is sent onward as an internal identifier.

Please avoid sending unnecessary sensitive or special-category personal data through the public booking path unless it is genuinely required and separately agreed.

Processing flow

Landing CTA interactions

Lawful basis: our legitimate interests in measuring B2B demand, improving the site, and protecting the service from misuse.

Retention approach: kept only as long as reasonably needed for operational analytics, debugging, and security review.

Categories of data

  • event names and CTA source labels
  • analytics identifiers such as GA client ID
  • basic timestamps and route context

Main purposes

  • understand which parts of the landing create interest
  • measure attribution and campaign performance
  • debug the booking path and keep the site reliable
Processing flow

Bottleneck review booking flow

Lawful basis: steps taken at the request of the data subject before entering into a contract, together with our legitimate interests in handling and qualifying business inquiries.

Retention approach: lead records and related correspondence are kept while we evaluate or manage the business relationship and then archived only as needed for legitimate business, tax, accounting, or legal purposes.

Categories of data

  • work email address entered in the booking flow
  • hashed email used as an internal user identifier
  • GA client ID and attribution data
  • booking source and selected slot context

Main purposes

  • respond to review requests
  • create lead and CRM records
  • link marketing attribution to qualified inbound interest
  • decide whether AgileHR is a fit for the requester
Processing flow

AgileHR product and workspace data

Lawful basis: performance of a contract with the customer and our legitimate interests in operating, securing, and improving the service.

Retention approach: kept for the life of the customer relationship, then retained only for backups, legal compliance, dispute handling, or documented deletion workflows.

Categories of data

  • account details such as email, name, and workspace membership
  • skills, assessments, survey responses, dependency maps, and organizational data entered by customers
  • support, security, and audit records needed to operate the product

Main purposes

  • provide the AgileHR product and authenticated access
  • generate skills, dependency, and bottleneck views for customers
  • support account administration, service security, and troubleshooting
  • maintain auditability and GDPR-related controls
Processing flow

Payments and subscriptions

Lawful basis: performance of a contract and compliance with legal obligations relating to bookkeeping, tax, and payment records.

Retention approach: kept for as long as required by accounting, tax, anti-fraud, or contractual record-keeping obligations.

Categories of data

  • billing and checkout details handled by the payment provider
  • subscription status, order identifiers, transaction amounts, and revenue events
  • customer support records related to payment issues or refunds

Main purposes

  • take payment for subscriptions
  • manage renewals, cancellations, refunds, and access state
  • keep accounting and tax records

Legal bases, data sources, and necessity

The lawful basis used for each processing context is documented in the flow cards above. Depending on context, AgileHR relies on pre-contract steps, contract performance, legal obligations, consent where relevant, and legitimate interests.

Most personal data is provided directly by you, your organization, or authorized workspace users. Some metadata is generated automatically by systems, such as security logs, technical events, and attribution identifiers.

When data marked as required is not provided, AgileHR may be unable to respond to a booking request, provide workspace access, process billing, or complete support and security workflows.

Recipients and processors

AgileHR uses a small set of infrastructure, analytics, attribution, and billing providers to operate the public site and the product path. The exact providers can change over time, but they are limited to categories needed to host, measure, support, and monetize the service.

Processors are expected to operate under appropriate contractual and security obligations, including data-processing terms where required.

Processor / provider

Hetzner

Purpose: hosting and infrastructure for core product services.

core product infrastructure is operated in the EEA, including Germany-based hosting where applicable

Processor / provider

Google Analytics

Purpose: website analytics and lead attribution.

used on the landing site to measure visits, CTA paths, and attribution context, including analytics identifiers such as the GA client ID, when analytics is enabled for the relevant region or consent state

Processor / provider

Rick.ai

Purpose: attribution and CRM-related event sync.

receives hashed user identifiers, client identifiers, transaction IDs, and revenue or lead event data rather than raw lead emails from the landing integration

Processor / provider

Lemon Squeezy

Purpose: checkout, billing, and subscription payments.

processes payment and subscription information as the payment merchant/provider for paid plans

Processor / provider

Google / Gmail SMTP

Purpose: business correspondence and transactional email infrastructure where used.

used for direct business communication and operational email delivery related to AgileHR

International transfers

Some service providers used by AgileHR may process personal data outside Portugal or the EEA/UK, including analytics, attribution, email, or payment providers.

Where a transfer outside the EEA or UK is relevant, AgileHR expects the provider to rely on an adequacy decision, standard contractual clauses, or another valid transfer mechanism where required by law.

Additional safeguards can include transfer risk checks, provider due diligence, and contract controls aligned with the transfer mechanism in use.

Retention

AgileHR retains personal data only for as long as needed for the stated purpose, for support and security needs, for backup integrity, or to meet contractual, tax, accounting, and legal obligations.

  • lead and contact records are kept only while needed to respond, qualify, onboard, or defend the related business relationship
  • account and workspace data are retained during the customer relationship and then reduced or deleted according to operational, backup, and legal requirements
  • payment and tax records are retained for the period required by applicable accounting and tax rules
  • technical logs are kept for the shortest period reasonably needed for security, troubleshooting, and service integrity
  • analytics data is retained according to provider settings and internal reporting needs, subject to future consent tooling changes

Your rights

Depending on the applicable law and your role in the relationship with AgileHR, you may have the following rights:

You can exercise rights by emailing the public contact address and describing the request scope. AgileHR normally targets a response within one month, with extensions where legally allowed for complex requests.

Where processing is based on consent, you can withdraw consent at any time for future processing. Withdrawal does not affect processing that happened before withdrawal.

  • access the personal data we hold about you
  • request correction of inaccurate or incomplete personal data
  • request deletion where there is no overriding reason to continue processing
  • request restriction of processing in the cases provided by law
  • object to processing based on legitimate interests
  • receive personal data you provided in a portable format where the right applies
  • lodge a complaint with your local supervisory authority or the Portuguese supervisory authority

Cookies, analytics, and current landing behavior

The public landing uses necessary cookies for core functionality and may also use analytics cookies or similar technologies to measure visits, CTA paths, and booking attribution.

Where analytics is active, AgileHR may store analytics identifiers, including the GA client ID used to connect landing activity with the booking flow. Necessary cookies remain available for the site and booking path to work.

You can use the cookie settings entry points on the site, where available, or your browser controls if you do not want analytics identifiers stored in your browser. This setup may change over time and this page is the reference point for those updates.

Automated decisions and children

AgileHR does not use fully automated decision-making that produces legal or similarly significant effects about individuals through the public landing or standard product operations.

The service is designed for professional users and organizations. It is not intentionally directed to children, and AgileHR does not knowingly collect children's data through the public business journey.

Security and complaints

AgileHR uses reasonable technical and organizational measures aimed at protecting personal data, including data minimization, restricted logging of raw personal data, and role-appropriate access controls within the product environment.

If you believe your personal data has been handled unlawfully, you can contact AgileHR first at the public email above. You also have the right to complain to your local supervisory authority or to the Portuguese supervisory authority, CNPD (Comissao Nacional de Protecao de Dados).