SERPAION Privacy Policy

This Privacy Policy explains how SERPAION processes personal data in connection with its B2B/professional website, application, subscriptions, support and AI Snapshot service (the Service ).It concerns natural persons; an organization or other legal entity is not itself a data subject merely because it is a Customer. SERPAION is established in Spain in the European Union. The EU GDPR applies where applicable, and other mandatory data-protection law applies where its own territorial scope requires it.

1. Controller and contact

SERPAION is the controller of the personal data processed for the purposes described in this Privacy Policy.

Professional address:

SERPAION - MB44832,
CC Cita, Planta Bajo, Locale 305
Avenida de Francia
Playa Del Ingles 35100
Spain

For privacy, data-protection, legal and support enquiries, including requests from former users or individuals who cannot access their account, contact:

support@serpaion.com

2. People covered and SERPAION's role

This Policy covers personal data relating to self-employed or professional Customers, representatives of organizational Customers, authorized users, prospective B2B customers, support contacts, website/application users, and people appearing in professional or business information processed by the Service.

SERPAION is an independent controller when it determines its own purposes and means, including signup; account, organization and user administration; authentication and security; subscription, billing and accounting administration; contract acceptance and evidence; transactional communications; support; cancellation and refund administration; payment-dispute handling; commercial-integrity and minimal meaningful-use evidence; legal compliance; and the establishment, exercise or defence of legal claims.

SERPAION acts as processor only to the extent a Customer submits personal data that SERPAION processes solely on that Customer's documented instructions to provide the Service. If the Customer is a processor for its own client, SERPAION may be the corresponding subprocessor. The Data Processing Terms apply only to processing within that processor/subprocessor scope. An AI Snapshot execution does not automatically involve processor-scope Customer Personal Data: the standard service analyses a business/brand, domain, services, market, SEO visibility and visibility/positioning in LLM responses. It does not intentionally analyse, score or profile natural persons or process special-category personal data.

3. Data we process and sources

Depending on the relationship and feature used, SERPAION may process:

  • Account and relationship data: the business signup/login email is the account identity, together with organization membership and role and authentication/security/signup/activation state. SERPAION does not maintain a separately stored professional or natural-person profile name as product identity.
  • Commercial data: subscription, plan and product information; Stripe identifiers; purchase/payment references; cancellation, refund and dispute facts; and business billing identity where applicable.
  • Authentication and security data: session/authentication state, access-control data and bounded technical security information actually generated.
  • Support data: requester name and email, selected support/contact category, message, and authenticated account information needed to handle the request.
  • Contracting data, where supported contracting flows collect it: Terms version, acceptance statement/version, B2B declaration/version, timestamp, accepting actor, contracting Customer, transaction/Checkout linkage and bounded transactional-confirmation evidence.
  • AI Snapshot analytical inputs: business/brand name, domain/URL, services/category, market/geographic context, SEO/visibility and LLM-response positioning/context, including SERPAION-generated analytical context and relevant public business/domain sources. Incidental identifiability of a sole trader acting professionally does not change the analytical subject into a natural person.

Ordinary AI Snapshot prompt construction does not add a SERPAION account email, user/account identity, organization ID, billing identity, Stripe identity, payment identity/details, credentials, or the fact that the analysed brand is a SERPAION Customer.

Data may come from the individual, Customer administrators, Stripe/payment services, SERPAION's Service operations, support communications, Customer-provided brand/domain information, public/professional business information, and authoritative payment/dispute sources.

Where personal data is required to enter into or perform a contract, comply with an applicable legal requirement, secure the Service, or provide a requested feature, SERPAION identifies the relevant requirement in the applicable collection flow. Failure to provide required data may prevent or delay the corresponding signup, contracting, payment, account activation, security verification, support handling, or Service functionality, as applicable. Data identified as optional is not required merely because the Service can accept it.

Public sources are used for business/domain analysis. The current Service does not intentionally target or analyse natural persons through public-data workflows. Public availability is not a blanket GDPR exemption. Where Article 14 applies to indirectly obtained personal data, its transparency requirements remain applicable.

Where indirect-collection transparency rules apply, SERPAION provides the required transparency within the applicable statutory timing unless a lawful processing-specific exception applies. Public availability is not, by itself, a blanket transparency exemption. Publishing this Policy does not automatically satisfy every individual-notice obligation. Any reliance on impossibility or disproportionate effort is assessed for the relevant processing and accompanied by the safeguards required by applicable law.

For processing governed by the EU GDPR, the applicable Article 6 basis depends on the purpose and circumstances:

Purpose Legal basis
Contracting and pre-contract steps Article 6(1)(b) where the natural person contracts or requests steps in a professional capacity.
Organizational representatives and users Article 6(1)(f), SERPAION's legitimate interest in administering the B2B relationship where the Customer is an organization.
Billing, accounting and tax Article 6(1)(b), 6(1)(c) and/or 6(1)(f), according to the precise purpose and any concrete obligation.
Authentication, security and abuse prevention Article 6(1)(f), and 6(1)(c) only where a concrete legal obligation applies.
Support Article 6(1)(b) and/or 6(1)(f).
Contract acceptance and evidence Article 6(1)(b) where necessary to evidence the professional contract; 6(1)(f) for contractual/commercial evidence and claim defence; and 6(1)(c) where specific recordkeeping applies.
Payment disputes and claims Article 6(1)(f), and 6(1)(c) where preservation or disclosure is legally required.
Bounded automated payment-dispute service-control processing For a natural-person professional, freelancer or sole trader who is the contractual Customer, Article 6(1)(b) applies only to personal-data processing objectively necessary to perform that Customer's contract through the bounded automated service-control mechanism described in section 9A. The qualifying solely automated decision relies separately on Article 22(2)(a). This Article 6(1)(b) basis does not apply to an employee, representative or authorized user merely because their employer or another legal person is the Customer.
Minimal meaningful-use evidence Article 6(1)(f): SERPAION's legitimate interest in minimal evidence of actual paid-Service delivery/use for commercial accountability, payment/dispute handling, and establishment, exercise or defence of contractual/commercial claims.
AI Snapshot analytical processing where the analytical subject matter itself identifies an individual professional, sole trader, personal-name brand or other identifiable professional Article 6(1)(b) where the processing is necessary to provide the contracted Service to an individual professional who is the Customer; Article 6(1)(f) where SERPAION acts as controller for limited processing of relevant professional/public business information necessary to provide the requested B2B analytical functionality; where SERPAION acts as processor, the Customer determines the lawful basis.

Where EU GDPR processing relies on Article 6(1)(f), the relevant legitimate interests may include operating and securing the B2B Service, administering the customer relationship and support, preventing abuse or fraud, preserving bounded commercial evidence, handling claims or disputes, and providing requested limited professional/public business analysis. These interests remain subject to necessity, proportionality, data minimization and the rights and freedoms of the affected individual.

Meaningful-use evidence is not authorized for advertising, behavioural profiling, customer scoring, clickstream or generalized usage analytics, or data sale.

For processor-scope Customer Personal Data, the Customer determines the lawful basis where it is controller; SERPAION processes under documented instructions and the Data Processing Terms. Consent is not the default basis for the core Service. It will be used only for an optional future activity that legally requires it.

5. AI/LLM analytical execution

SERPAION uses third-party AI/LLM services as technical execution providers for AI Snapshot. A normal analytical request contains business/brand, domain, services/category, target market, SEO/visibility and LLM-response positioning or analysis context. SERPAION's provider account makes the API request and SERPAION is billed for it.

Ordinary prompts exclude the account email, user/account identity, credentials, billing identity and Stripe/payment identity. The provider does not need to know that the analysed business is a SERPAION Customer. Standard AI Snapshot does not intentionally analyse or profile natural persons. Incidental identifiability of a sole trader does not change the business/domain analytical subject or purpose. Special-category personal data is prohibited and not intended in current scope.

SERPAION does not itself use Customer account personal data to train a general- purpose AI model. Provider retention, model-training/data-use and geographic terms are not necessarily identical, zero-retention, or EU-only. Available provider categories and execution paths are not a contractual entitlement.

Before enabling an AI provider for production analytical processing, SERPAION verifies that the applicable provider account, configuration and contractual framework permit the intended API use and the categories of analytical information sent. Where an execution contains personal data, any processor, subprocessor or international-transfer safeguards required by applicable law must be in place before that data is sent.

Provider use is subject to the applicable contractual and data-use settings. If a category of personal data cannot lawfully be sent through a particular provider path, that category must not be sent through that path.

6. Payments, email and support

Stripe handles payment/billing processing and invoice documents. SERPAION retains only existing bounded transaction, subscription, provider and commercial evidence and does not intentionally collect raw card numbers or CVC in normal application inputs. Depending on the purpose and applicable Stripe terms, Stripe may act as processor and/or an independent controller. SERPAION may retain bounded Stripe identifiers and commercial evidence necessary for subscription administration, reconciliation and claims; Stripe is not characterized as SERPAION's subprocessor for every purpose.

Transactional and support communications may use authorized email infrastructure. A support submission may contain the requester's name, email, category and message, with authenticated account information used where needed to handle the request. SERPAION does not represent that a separate CRM is used.

7. Cookies and local storage

Current cookie and local-storage use is limited to strictly necessary authentication, session continuity and security, and functional or requested preferences such as language, theme, accent and equivalent user-selected UI settings. It does not authorize advertising cookies, cross-site tracking, behavioural advertising, tracking pixels or generalized marketing analytics.

If non-essential analytics, advertising or other consent-requiring storage is added in the future, valid prior consent will be obtained where required by law.

8. Recipients and international transfers

Only where relevant, recipient categories may include hosting/infrastructure, database, transactional-email, billing/payment and AI/LLM API providers; legal, accounting or security advisers; and competent authorities where law requires. Stripe is specifically identified where it handles the Customer-visible payment, billing or Managed Payments Merchant-of-Record relationship. No recipient necessarily receives every category.

Data is not represented as remaining exclusively in Spain or the EEA. Where a restricted international transfer is governed by applicable data-protection law, SERPAION must use the lawful mechanism required for that transfer. This may include adequacy where applicable; EU Standard Contractual Clauses or another applicable GDPR Article 46 mechanism; supplementary measures or a transfer assessment where legally required; or another legally applicable safeguard. Derogations are not the normal production model.

Information about the safeguards applicable to a relevant international transfer, and the means to obtain a copy of those safeguards where applicable, may be requested through support@serpaion.com .

9. Retention

There is no universal retention period; each category is retained only for its own purpose and period. The 12-month post-relationship boundary is only a residual commercial cleanup checkpoint: it neither extends shorter 30-day or 90-day commitments nor shortens longer 24-month, six-year, or matter-specific periods, and it creates no basis to keep personal data that is no longer lawfully necessary. Processor-scope data remains governed by the Data Processing Terms and is not extended to 12 months. An applicable statutory preservation rule, live dispute, litigation/preservation requirement, or documented legal hold controls only the necessary bounded category and only as long as necessary. Six years is not SaaS-wide retention authority.

Category Ordinary policy
Signup intents Functionally valid 24 hours. If abandoned/unconverted, delete or anonymize no later than 30 days after expiry, absent a specific security/legal preservation reason.
Activation/password-reset token records Functional expiry is separate. Delete/anonymize expired or consumed records within 30 days after expiry/use unless specifically preserved for security investigation or legal hold. Plaintext tokens are not retained.
Session/auth records Authentication sessions ordinarily remain valid for up to 7 days and refresh sessions for up to 14 days. Expired or revoked operational records are retained for no more than 90 days after invalidation absent a specific security or legal-preservation reason.
Active account/organization personal data While needed for the active relationship; after termination, delete/anonymize unnecessary operational data within 90 days. Required evidence moves to its specific category.
Customer-controlled processor data At the Customer's choice under the Data Processing Terms, return or delete Customer Personal Data after the processor-scope Service ends, with active-system deletion ordinarily completed within 90 days and existing copies deleted unless Union or Member-State law requires storage or a documented legal-preservation requirement applies. This is not a label for normal public-brand facts merely because an LLM was used.
AI Snapshot analytical content that itself constitutes personal data Retained only while needed for the relevant active project, report or Service purpose. After termination of the relevant Service, ordinary copies no longer required for that purpose are deleted or irreversibly anonymized within 90 days unless the processor-scope rule, a separate bounded legal/evidence category, applicable law, or a documented preservation hold independently requires otherwise. Public availability does not authorize indefinite retention.
Residual non-personal Customer/project/report operational data Data that is neither personal data nor independently governed evidence is ordinarily reviewed for deletion 12 months after the end or non-renewal of the relevant paid relationship. Shorter, longer, processor-specific, and preservation rules take precedence.
Support correspondence Maximum 24 months after case closure. Necessary dispute material moves to the applicable evidence category.
Minimal meaningful-use facts 24 months from the recorded event , subject only to a matter-specific dispute, legal or preservation hold.
Contract acceptance/confirmation evidence Retained while necessary as the governing evidence of an active contractual relationship. After the relevant relationship ends, the ordinary six-year evidence period runs from the later of the authoritative relationship end and the last relevant business/accounting entry associated with that relationship or transaction. For a one-off transaction with no later relationship-end or accounting event, the period runs from authoritative completed purchase/transaction success. A different mandatory rule or documented legal hold may control. This category remains limited to bounded contracting evidence and does not include unrelated Customer content. No tracking pixels, open/click tracking, device fingerprint, geolocation or IP are retained merely to prove acceptance.
Billing/accounting/subscription records Where the applicable Spanish commercial-document preservation rule applies, minimum necessary records are retained for six years from the authoritative last relevant business/accounting or book entry for the affected record. A later relevant entry may supersede the earlier start for the affected record set where applicable. This is not authority to retain all SaaS content for six years.
Payment-dispute/claim evidence Bounded, narrowly accessed case evidence: ordinary maximum six years after final resolution or later relevant commercial record where applicable, subject to live litigation/preservation.
Transactional-email metadata Ordinary delivery/support metadata: 24 months. A minimal provider message identifier, status or timestamp that forms part of contract acceptance or confirmation evidence inherits the same deterministic retention-start event as its linked contract or transaction evidence. Whole message bodies do not inherit six years merely because minimal delivery evidence is preserved.
Security/audit personal identifiers Maximum 12 months, longer only for a specific active investigation, claim, authority request or documented preservation requirement.

A SERPAION SEO/company/public-web analytical report is not personal data merely because the report exists. Where specific report content actually contains personal data, the applicable personal-data category and period control.

The six-year Spanish commercial-document policy is bounded to the books, correspondence, documentation, and supporting business evidence to which that rule actually applies; it is not SaaS-wide retention authority.

Where Spanish law requires preservation for potential legal responsibilities after operational use must cease, SERPAION will block the data: identify and reserve it, remove it from ordinary operational use and ordinary visualization, restrict access to the legally permitted authority path, preserve it solely for the legally permitted liability/preservation purpose, and delete or destroy it when the applicable limitation/prescription period ends. Blocking is restricted preservation, not indefinite retention or ordinary continued processing.

9A. Automated service controls and human review

For the payment-dispute flow, the trigger is an authoritative payment-provider or card-network dispute, chargeback, or equivalent formal payment contest tied to a SERPAION-owned payment. The system reacts to that authoritative payment-dispute state; it is not behavioural advertising, credit scoring or general profiling of the Customer.

The initial automated restriction pauses new cost-bearing, provider and commercial activity, including new AI Snapshot/provider execution, retries, new report generation, purchases, upgrades and Checkout. It does not itself disable future subscription renewal. Existing authorized/materialized content remains readable, and already-incurred provider work completes its accounting. This automated restriction does not itself create the broader final service restriction; a human authorized to change the result reviews the case and can allow or restrict subsequent service.

EU / EEA

For a natural-person professional, freelancer or sole trader where this automated restriction is capable of producing legal or similarly significant effects, SERPAION conservatively treats it as within EU GDPR Article 22(1). SERPAION uses Article 6(1)(b) as the lawful basis only for the specific personal-data processing objectively necessary to perform the natural-person contractual Customer's contract through this bounded automated payment-dispute service-control processing. Separately, Article 22(2)(a) contractual necessity is the applicable exception permitting the qualifying solely automated decision; Article 22(2)(a) is not itself an Article 6 lawful basis. Necessity is established by the bounded purpose and assessment described here, not by the mere existence of a restriction clause in the Terms. The dispute places the contractual consideration supporting paid service in formal dispute, and the bounded immediate pause prevents additional provider cost and contractual value from being consumed against that disputed consideration. Permitting unrestricted new cost or value consumption until the first human review would not be an equally effective less-intrusive alternative.

Separate payment-dispute evidence, claims administration or defence, and legally required preservation retain their separately stated Article 6(1)(f) and Article 6(1)(c) bases where their respective requirements apply. They are not moved wholesale to Article 6(1)(b). Article 22(2)(a) does not extend to a future-renewal decision: renewal suppression requires the authorized human decision described below.

The GDPR Article 22(3) safeguards include meaningful human review by a person authorized to change the outcome. The affected person may contact support@serpaion.com to request human intervention, express their point of view, provide relevant information or evidence, and contest the restriction. The reviewer may allow or restrict service after review. SERPAION makes a reasonable direct-contact attempt. A human-review request does not itself automatically restore service.

The direct-contact attempt tells the appropriately authorized Customer contact, in plain language, that SERPAION received an authoritative formal payment dispute or chargeback associated with the Customer payment; that it triggered an automated temporary restriction; that new paid activity is paused while existing authorized/materialized content remains readable; and that the person may explain their position, provide relevant evidence, request meaningful human intervention, and contest the restriction. Customer-related payment identifiers are communicated only through an appropriately authorized support or review context.

10. Rights

Subject to statutory conditions and exceptions, individuals may request access, rectification, erasure, restriction, objection and portability where applicable; withdraw consent where consent is actually used, without affecting the lawfulness of processing carried out before withdrawal; exercise applicable rights regarding qualifying automated individual decisions; complain to an applicable supervisory authority; and seek judicial remedies.

For Spain and processing connected with SERPAION's EU establishment, the Spanish Data Protection Agency (AEPD) is the relevant Spanish authority. Other applicable supervisory authorities may also be competent where applicable law provides.

Contact support@serpaion.com . A data-protection complaint may be sent directly to that address without authentication; authenticated Customers may also select the dedicated Privacy / Data Protection option in Contact / Support. A privacy complaint, a data-subject rights request and an ordinary technical support request remain distinct processes.

For data-subject rights requests governed by the EU GDPR, SERPAION applies the ordinary one-month response framework and any extension only where the law permits it and the required notice is given. Other requests are handled within the timing required by applicable law.

Reasonably necessary identity verification may be requested.

Where processing is based on an applicable GDPR Article 6(1)(f) legitimate-interest basis, an individual may object on grounds relating to that individual's particular situation. SERPAION will cease that processing unless applicable law permits continuation because compelling legitimate grounds override the individual's interests, rights and freedoms, or the processing is required for the establishment, exercise or defence of legal claims.

11. Automation, children and sensitive data

SERPAION may use technical automation for authentication, security, rate limits, entitlements/capacity, payment/provider state, abuse prevention and service integrity. This is not behavioural advertising or credit scoring. Direct refund requests remain subject to manual review under the Terms. Where GDPR Article 22 applies to a qualifying decision, mandatory safeguards remain available.

The Service is B2B/professional and not directed to children. The standard Service is not intended for special-category data; users must not intentionally place it in ordinary inputs unless an expressly authorized feature and lawful framework support it. Raw card/CVC or banking credentials must not be submitted through ordinary application inputs.

12. Changes to this Policy

Privacy notices operate prospectively. SERPAION will notify material changes where legally required or reasonably appropriate. Updating this Policy is not blanket consent. Where historical notice evidence matters, SERPAION must preserve the version actually presented.