Legal

Privacy Policy

Last updated: October 15, 2026

1. Data Controller

Napsix Corp (Delaware, USA) and Napsix S.A.S. (Argentina, Mendoza) are joint controllers of the personal data collected through the Platform. We apply the corresponding local regulations according to the data subject's jurisdiction:

  • 🇦🇷 Argentina: Personal Data Protection Act No. 25,326 (AAIP).
  • 🇧🇷 Brazil: LGPD — Lei Geral de Proteção de Dados (ANPD).
  • 🇲🇽 Mexico: LFPDPPP — Federal Law on the Protection of Personal Data Held by Private Parties (INAI).
  • 🇨🇴 Colombia: Law 1581 of 2012 (SIC).
  • 🇨🇱 Chile: Law 19,628 on the Protection of Private Life.
  • 🇪🇺 European Union / United Kingdom: GDPR / UK-GDPR.
  • 🇺🇸 USA: CCPA (California) and applicable federal regulations.

Privacy officer contact: privacy@napsix.com.

2. Data We Collect

  • Registration data: legal business name, local tax ID (CUIT/CNPJ/RFC/RUT/NIT), email, phone, country, province/state.
  • Usage data: interactions on the platform, listings, quotes sent, XIA agents created, automations configured.
  • Technical data: IP address, browser, device. The IP address is stored as a truncated SHA-256 hash (16 characters), never in plain text.
  • Conversations with XIA Assistant: messages you send to the assistant, together with session metadata (model used, tokens, optional satisfaction). These conversations are stored associated with your user.
  • Feedback content: bugs, ideas, and reports you submit through XIA Assistant or the Quick Report widget (page, browser, message, estimated severity, optional attachments).
  • Data originating from third-party e-commerce and SaaS integrations (see section 13).

3. Purpose of Processing

  • Manage your account and commercial profile.
  • Operate your integrations and XIA agents for you.
  • Operate your online store (Tiendanube/Nuvemshop, Shopify, etc.) through XIA agents according to the OAuth permissions you explicitly grant.
  • Send notifications related to quotes, messages, and operational events of your store.
  • Improve the user experience and the security of the Platform.
  • Process and follow up on the feedback you submit to improve the product. The XIA conversations associated with a report are visible to Napsix administrators to understand the context of the issue. They are NOT visible to other users nor shared with third parties.

4. Legal Basis

Processing is based on (a) the consent given when registering and when approving each OAuth integration, (b) the performance of the contracted service, and (c) the legitimate interest in improving the platform and preventing fraud. The specific legal basis depends on the data subject's jurisdiction (see section 1).

5. Data Sharing

  • Your public profile data (legal business name, sector, province, rating) is visible to other users of the Platform.
  • We do not sell or share personal data with third parties for commercial purposes unrelated to the Platform.
  • Active sub-processors (with signed DPA agreements): Supabase (database + storage + auth), Vercel (hosting), Anthropic + OpenAI + Google (AI models), Resend (transactional email), a SaaS integrations provider (1,000+ apps), Pusher (push notifications), Cloudflare (CDN + DNS), Commet (billing).
  • We may share data when required by a competent judicial authority.

6. Data Subject Rights

You may exercise your rights of access, rectification, erasure, objection, portability, and restriction of processing by writing to privacy@napsix.com. We process requests within a maximum of 30 days. The applicable supervisory bodies by jurisdiction are: AAIP (AR), ANPD (BR), INAI (MX), SIC (CO), Council for Transparency (CL), GDPR Supervisory Authorities (EU), Privacy Rights Clearinghouse (USA).

7. Security

We implement technical and organizational measures to protect your data:

  • Encryption in transit (TLS 1.3) and encryption at rest (AES-256).
  • Integration OAuth tokens stored in Supabase Vault with AEAD encryption and access restricted by SECURITY DEFINER functions. The plaintext is NEVER accessible from the frontend.
  • Row-Level Security (RLS) on all tables: each tenant sees only its own data.
  • Full auditing: an audit_log table with all sensitive operations traced.
  • Optional MFA for accounts with elevated privileges.
  • Daily automatic backups with 7-30 day retention depending on the plan.
  • 24/7 monitoring of security and availability.

8. Cookies and measurement technologies

We use cookies and similar technologies of three kinds: technical (essential for the site to work), analytics, and marketing.

For analytics and marketing cookies we apply consent mode (Google Consent Mode v2). In regions where prior consent is required by law (European Union / EEA, United Kingdom, and Switzerland) they remain DENIED by default until you accept them in the cookie banner; in other regions they are enabled by default and you can reject them. You can change your choice at any time or by writing to privacy@napsix.com.

  • Technical (always on): session, authentication, and preferences required for the site to work.
  • Analytics: Google Analytics 4 (via Google Tag Manager) and Vercel Analytics, to measure traffic and usage in aggregate.
  • Marketing: Meta Pixel (Facebook/Instagram) to measure conversions and ad campaigns.

We do not load these technologies inside the private app panel (/dashboard); only on the public pages of the site.

9. Public Feedback (Roadmap)

When the Napsix team decides to publish a piece of feedback on the public roadmap (/dashboard/feedback), we publish ONE rewritten title and a response from the team. We do NOT publish any identifying data of the original author (email, name, IP, the literal content of the original message). Other tenants can vote on public items.

If at any time you want a specific feedback submission to be completely deleted from our systems, write to us at privacy@napsix.com indicating the report ID and we will proceed with permanent deletion within a maximum of 30 days.

10. Data Retention

  • Account and profile data: for the duration of your account + 12 months after closure (legal audit).
  • XIA Assistant conversations: maximum retention of 24 months from the last interaction.
  • Submitted feedback: retained for the duration necessary to process the report + an additional 12 months (internal audit). Feedback marked public on the roadmap is kept as long as it is published.
  • Admin internal comments on a piece of feedback: deleted when the feedback is deleted.
  • Data originating from e-commerce integrations (Tiendanube, Shopify, etc.): deleted or anonymized according to section 14 when you uninstall the app.
  • Audit logs: 12 months (operational logs), 5 years (financial / billing logs).

11. Modifications

We reserve the right to update this policy. We will notify you of significant changes by email at least 30 days in advance.

12. General Contact

info@napsix.com — Mendoza, Argentina · Delaware, USA.

13. Data Accessed via Third-Party E-commerce and SaaS Integrations

When you connect an OAuth integration (Tiendanube/Nuvemshop, Shopify, Gmail, HubSpot, Slack, Google Drive, etc.) through the Integraciones catalog, you grant explicit consent for Napsix to access certain data from the third-party service with the permissions (scopes) you approve in the OAuth flow.

13.1 Tiendanube / Nuvemshop

When you connect your Tiendanube/Nuvemshop store to Napsix, we access the following data according to the approved scopes:

  • read_products / write_products: catalog (products, variants, prices, stock, images, categories).
  • read_orders / write_orders: orders (status, items, totals, shipping, billing).
  • read_customers / write_customers: customers (name, email, phone, shipping and billing address).
  • read_coupons / write_coupons: discount coupons.
  • read_shipping / write_shipping: shipping and carrier configuration.
  • read_scripts / write_scripts: scripts injected into the storefront.
  • read_content / write_content: pages, blog posts, redirects.
  • read_store / write_store: general store configuration.

This data is processed exclusively to perform the tasks that your XIA agent decides or that you explicitly request from the chat. It is not shared with third parties, not sold, and not used to train general-purpose AI models.

The personal data of your end customers (buyers from your store) is processed by Napsix solely as a data processor following the instructions of the merchant (you), who is the data controller for that data with respect to its own customers.

13.2 Other Integrations (Gmail, Slack, HubSpot, etc.)

The same principle applies: we only access data according to the OAuth scopes you approve, and we only use it to perform the tasks that your XIA agent or you request.

14. GDPR Webhooks and Data Deletion upon Uninstall

We comply with the privacy requirements of the e-commerce platforms we connect to. Specifically, Tiendanube/Nuvemshop subscribes us to three mandatory GDPR webhooks:

  • app/uninstalled (POST /api/webhooks/tiendanube): when you uninstall the XIA by Napsix app from the Tiendanube admin, we receive the event, delete the OAuth token from Supabase Vault, mark the connection as revoked, anonymize the analytics snapshots, and delete the associated scheduled jobs. Any raw data (products, orders, customers) we may have cached is deleted within a maximum of 30 days.
  • store/redact (Tiendanube removes you as a merchant): we receive the event and delete all information about your store from our systems within 30 days.
  • customers/redact (one of your end customers requests deletion): we receive the event and anonymize any personal data of that customer we have cached.
  • customers/data_request (one of your end customers requests access to their data): we forward the request to you so that you, as the data controller, respond within the legal timeframe.

If you want to manually request the complete deletion of all your data (not just the data originating from an integration), write to us at privacy@napsix.com and we will proceed within a maximum of 30 days, with a confirmation by email.

15. Connected AI clients (MCP)

With the Napsix connector (https://www.napsix.com/api/mcp) you can connect an AI client you choose (for example Claude, ChatGPT or Claude Code) to your Napsix account. You authorize it by signing in to Napsix and approving the permissions (scopes) and the organizations it may reach. Documentation: https://www.napsix.com/en/developers/connector.

  • Data the client receives: only what the tools it calls return, within the permissions you granted, in the organizations you chose and as far as your role lets you see. By permission: projects, tasks and their conversations; AI agents; forms and, with forms:responses, their responses; documents; Drive files and the knowledge base; mail metadata and delivery status; your calendar and bookings; customer conversations; team chat; CRM contacts and deals; email campaigns; social media posts; automations; organization profile and members; plan and usage; product catalog; and billing clients and invoices of the ERP, which include tax IDs. Sensitive permissions (mail, Drive, calendar, customer inbox, form responses, CRM, catalog and ERP, among others) are off unless you turn them on.
  • Recipient: the provider of the client you connect (Anthropic for Claude and Claude Code, OpenAI for ChatGPT, or the provider of another client) receives that data and processes it as an independent controller, under its own terms and privacy policy. Napsix does not control what the client does with the data it receives.
  • ChatGPT connections never get the tools of the ERP (billing clients and their tax IDs, invoices) or of the plan and usage.
  • Actions: what the client does, it does as you, with your role, and every write is recorded in the organization's audit log. Sending email, replying to customers, sending campaigns, publishing posts and emitting or sending invoices need your confirmation.
  • What Napsix keeps: the connection (client name, permissions, organizations and dates) and its tokens, stored only as hashes. Access tokens expire after 1 hour and refresh tokens after 30 days; every connection, personal access tokens included, ends at most 90 days after it was authorized. Expired or revoked tokens are deleted a day later; the record of write operations (used to retry them safely) is kept for 90 days, and the audit log as stated in section 10. Revoked connections stay in your connection history while your account exists.
  • Control: you can revoke a connection at any time in Napsix, under My account → AI connections, or change its permissions there. Revoking it stops its access at once, cancels the agent runs it requested that have not started and leaves its pending approvals unexecuted.

Questions about the connector and your data: privacy@napsix.com.

Your next step

From evaluation to a concrete integration.

Start with an account or talk to us about the scope of your team and application.

XIA
public