Skip to content
Loading — 00%
Argo
AssistantToolkitMobileSecurityPricing
ENPTES
Log inCreate accountGo to Dashboard
AssistantToolkitMobileSecurityPricing
ENPTES
Log inCreate accountGo to Dashboard
Legal

Privacy Policy

Last updated: August 1, 2026

This Policy explains what personal data Argo collects, why, who we share it with, how long we keep it, and the rights you have over it. It applies wherever you use Argo, and is written to meet both Brazil's Lei Geral de Proteção de Dados (LGPD) and the EU/UK General Data Protection Regulation (GDPR), since Argo is used by people in both regions.

Who we areWhat we collectWhy we use itLegal basisWho we share it withInternational transfersHow long we keep itYour rightsSecurityCookiesChildren's privacyChanges to this PolicyContact us

Who we are

Argo is operated by Taurus Technology ("Argo", "we", "us"). For the purposes of LGPD and GDPR, Taurus Technology is the data controller for the personal data described in this Policy. You can reach us at [email protected] for anything related to your data or this Policy.

What we collect

Account information

When you create an account: your email address, full name, and a password, which we never store in readable form — it's hashed with Argon2id (the current OWASP-recommended algorithm for password storage) before it ever touches our database. We also record login timestamps, failed-login counts, and IP address on login attempts, purely to detect and block credential-stuffing/brute-force attempts.

Trip content

Everything you put into a trip: destinations, dates, itinerary items, flights, ground transport, accommodations, budget categories and expenses, packing and shopping lists. This is the core of what Argo stores on your behalf, and it's yours — see Your rights below for how to export or delete it.

AI copilot conversations

If you use the AI assistant, we store the full text of your messages and its replies, scoped to the trip and conversation you had them in, so you can come back to a conversation later and so the assistant can refer back to earlier context. See Who we share it with for how this data reaches our AI provider.

Information about people you invite

If you invite someone to collaborate on a trip, we store their email address and the role you gave them (editor or viewer) — even before they create an account. If they never accept the invitation, this is the only data we hold about them, and it's deleted if you cancel the invitation or delete the trip.

Payment & AI credit information

When you purchase a Plus or Premium trip tier, or an AI credit pack, payment is processed by Stripe — your card details go directly to Stripe and never touch our servers. We store the resulting transaction record (amount, currency, what you purchased, status, and Stripe's own reference ids) linked to your account, along with your AI credit balance and the history of what added to or removed from it (a free signup bonus, a tier purchase, a credit-pack purchase, AI usage, or a refund).

Information collected automatically

For every request to our servers, we log: IP address, user agent (browser/device string), the endpoint called, and a user/trip identifier where you're authenticated. We do not log request or response bodies — passwords, tokens, AI conversation text, and trip content never appear in these logs. This data stays on infrastructure we operate ourselves; it is not sent to a third-party analytics or logging vendor. We do not use any advertising, analytics, or behavioral-tracking scripts anywhere in Argo.

Why we use it

  • To create and secure your account, and to authenticate you.
  • To provide the core product — storing and organizing your trip content.
  • To power the AI copilot's answers and the actions it takes on your trip when you ask it to.
  • To process payments and keep an accurate record of what you've paid for.
  • To send transactional email: verification, password reset, and trip-invitation emails. We do not send marketing email.
  • To detect and prevent abuse, fraud, and unauthorized access.
  • To meet legal and accounting obligations (for example, retaining transaction records for tax purposes).

Legal basis for processing

Depending on what we're doing with your data, we rely on one of the following:

  • Performance of a contract — most of what Argo does: storing your trip content, running the AI copilot when you use it, processing payments you request.
  • Legitimate interests — securing the service (rate-limiting, fraud/abuse detection, the security logging described above), where this doesn't override your own rights and interests.
  • Legal obligation — retaining transaction records for accounting and tax compliance.
  • Consent — where we ask for it explicitly (for example, if we ever add optional marketing communications — we don't send any today).

Who we share it with

We do not sell your personal data, and we do not share it for advertising purposes. We share it only with the service providers ("sub-processors") that Argo actually depends on to function:

ProviderWhat it's forWhat it receives
OpenAIPowers the AI copilotYour messages to the assistant and the trip context needed to answer them
StripePayment processingBilling details you enter at checkout (handled entirely on Stripe's own systems)
ResendTransactional email deliveryYour email address, name, and the content of verification/reset/invite emails
Open-MeteoDestination geocoding and weatherPlace names and country you enter — no personal data
AwesomeAPICurrency exchange ratesCurrency pair codes only (e.g. "USD-BRL") — no personal data

We may also disclose data where required by law, to comply with a valid legal process, or to protect the rights, property, or safety of Argo, our users, or the public.

International data transfers

OpenAI and Resend process data outside Brazil (primarily in the United States). Where we transfer personal data internationally, we rely on the transfer mechanisms those providers make available for their business customers (such as Standard Contractual Clauses) and on their own published data-processing and security commitments. If you'd like more detail about a specific transfer, contact us at [email protected].

How long we keep it

  • Account and trip data: kept while your account is active. When you delete your account or a trip, it's soft-deleted immediately (recoverable by you for 30 days), then permanently and irreversibly deleted.
  • Shared trips: if you own a trip shared with collaborators and you delete your account, the trip — and every collaborator's access to it — is deleted along with it once the 30-day window passes. Consider transferring ownership or exporting shared content first if this matters to you.
  • Payment records: kept after account deletion, but with the link to your identity removed, so we can meet accounting/tax record-keeping obligations without retaining data that identifies you.
  • Login attempt records (used for abuse detection): kept for 24 hours only.
  • Server logs: kept for 30 days on our own infrastructure, then deleted.
  • Webhook event records (Stripe idempotency guard): kept for 7 days.

Your rights

Under LGPD and GDPR, you have the right to:

  • Access the personal data we hold about you.
  • Correct inaccurate data — most of this you can already do directly in your account settings.
  • Delete your account and data — self-service, from your account settings, no need to contact us. Deletion is reversible for 30 days, then permanent.
  • Export your data in a portable format.
  • Object to or restrict certain processing, and withdraw consent where we rely on it.
  • Lodge a complaint with your local data protection authority — in Brazil, the Autoridade Nacional de Proteção de Dados (ANPD).

For anything not available directly in the product, email [email protected] and we'll respond within the timeframe required by applicable law.

Security

  • Passwords are hashed with Argon2id — we cannot see or recover your actual password, ever.
  • Authentication uses a short-lived access token plus a refresh token stored in an HttpOnly, Secure, SameSite cookie — never in a place JavaScript (or an XSS attack) could read it.
  • Login is rate-limited and lockable to slow down credential-stuffing and brute-force attempts.
  • Stripe webhook events are cryptographically verified before we act on them, and processed exactly once even if delivered more than once.
  • Every request is scoped server-side to the authenticated user and the trips they actually belong to — access isn't just "logged in," it's checked against real ownership/membership on every request.
No system is perfectly secure. If we ever become aware of a data breach affecting your personal data, we will notify affected users and the relevant authority (ANPD and/or the applicable EU supervisory authority) within the timeframe required by law.

Cookies

Argo uses exactly one cookie: refresh_token, which keeps you logged in. It's strictly necessary for the service to function, HttpOnly (JavaScript cannot read it), Secure (HTTPS only), and scoped SameSite=Lax. We do not use advertising cookies, analytics cookies, or any third-party tracking cookies — there is nothing else to opt in or out of.

Children's privacy

Argo is not directed at, and is not intended to be used by, anyone under 18. We do not knowingly collect personal data from children. If you believe a child has created an account, contact us at [email protected] and we will delete it.

Changes to this Policy

If we make a material change to this Policy, we'll notify you by email and/or an in-product notice before it takes effect. The "Last updated" date at the top always reflects the current version.

Contact us

Taurus Technology — [email protected]

Argo

Plan less. Travel more.

AssistantToolkitMobilePricingPrivacy PolicyTerms of Service
© 2026 Taurus Technology. All rights reserved.An AI copilot that keeps its receipts — nothing charged twice, nothing forgotten.