Privacy Policy

1. Who We Are

Taxller is a product of Andivano LLC, a Florida limited liability company with a principal address at 800 SE 4th Ave, Ste 101, Hallandale Beach, FL 33009, USA. In this Privacy Policy, "Taxller," "we," "us," and "our" mean Andivano LLC. You can reach us at info@taxller.com.

2. Scope of This Policy

This Privacy Policy explains how we collect, use, and share information in two contexts: (a) the taxller.com marketing website, and (b) the Taxller product itself, live at app.taxller.com — a SaaS bookkeeping and US tax-compliance cockpit for Amazon sellers. The two are separate systems with different privacy footprints, and we describe them separately throughout this policy: what happens when you read a marketing page is not what happens when you sign in to the dashboard.

This policy applies to visitors to taxller.com and to registered users of the Taxller product. It does not apply to services offered by third parties, including Amazon, Google, Cloudflare, Resend, and Stripe, whether we link to them or integrate with them. Those companies have their own privacy policies governing their own handling of your information.

3. Information We Collect

The marketing website (taxller.com). Here we collect only what you choose to send us: if you email info@taxller.com, we receive your email address and whatever you include in your message. Like virtually all websites, our hosting provider automatically records standard technical data for every request — such as IP address, browser type, and access timestamps — in server logs used for security and operational purposes, for example detecting abuse. This routine logging is not used to track you across sites, build an advertising profile, or personalize content, and it is separate from the cookies described in Section 4.

The product (app.taxller.com). When you register for and use the Taxller dashboard, we collect the following categories of information:

• Account data — the email address you register with, the display name on your profile, your interface language and theme preference, and, if you sign in with Google, the email address, name, profile picture, and Google account identifier that Google returns to us. We never receive your Google password.
• Authentication and security credentials — your password, stored only as an argon2id hash and never in readable form; your multi-factor authentication secret and single-use recovery codes; active session records; and logs of sign-in attempts, email verifications, and password resets.
• Consent records — when you accept our legal documents, and when you confirm billing terms before a checkout, we store the dated versions of the Terms of Service and this Privacy Policy associated with that record, a SHA-256 hash of those document versions, how you accepted or confirmed, your interface language, your IP address, your browser user-agent string, and the timestamp. For a billing confirmation, the record is also tied to the relevant Stripe Checkout session. We keep this as evidence of the acceptance or confirmation recorded through that screen.
• Company and questionnaire data — the answers you give in the onboarding questionnaire and in company settings: business entity details such as company name, EIN, state of formation, fiscal year, ownership and residency profile, and the marketplaces and sales channels you tell us you sell on.
• Documents and files you upload — reports, settlement files, and supporting documents you upload to the report archive, together with their metadata (file name, size, period covered, upload time and the account that uploaded them). They are stored encrypted in Amazon S3 in the us-east-1 region.
• Billing data — when you start a subscription or token checkout, Stripe processes any resulting payment on its hosted pages and sends us billing-event data. In our product database we store the limited metadata needed to administer the checkout and any resulting purchase: Stripe customer, checkout-session, subscription, invoice, and event identifiers; the selected plan or token quantity; subscription status, billing-period end, and cancellation status; wallet entries tied to a checkout session or invoice; and a checkout-specific confirmation record associated with the then-current Terms of Service and Privacy Policy versions. For each paid purchase and each successful refund we also issue our own invoice or credit note. To do that we store, in our product database, a billing snapshot taken at the time of the document — the company name, contact name, contact email address, billing address, and any tax ID you provided at checkout or in your billing settings — together with the amounts and a limited payment-method summary (the card brand and the last four digits of the card, or the name of the payment method, such as Link); the generated PDF itself is kept in our encrypted document storage on AWS (Section 6), with only its storage key and checksum recorded in the database. We use charge amounts and billing-period details to prepare confirmation emails but do not store the Stripe event payload itself. We never store or have access to your full card number or card security code.
• Amazon financial and settlement data via SP-API — once the Amazon connection becomes available, and with your authorization, we will connect to your Amazon Seller Central account through Amazon's official Selling Partner API (SP-API), using OAuth authorization that you grant on Amazon's own consent screen. On your seller account we will exercise four non-restricted data roles and no others: Finance and Accounting, Inventory and Order Tracking, Amazon Fulfillment, and Selling Partner Insights. We will request no restricted roles at all, and will not request or receive buyer personally identifiable information — no buyer names, addresses, or contact details. Our handling of Selling Partner API data will comply with Amazon's Data Protection Policy.
• Anti-bot verification data — when you register, sign in after repeated failed sign-in attempts, request a password reset, resend a verification email, or use demo sign-in, Cloudflare Turnstile runs a challenge in your browser and returns a token that we verify with Cloudflare. Cloudflare receives your IP address and technical signals about that browser session as part of the check. Turnstile exists to tell humans from bots; it is not an advertising or profiling tool, and we receive only the pass/fail result.
• Support communications — the content of any message, attachment, or information you send us when you contact support.
• Technical and security log data — standard technical data such as IP address, browser type, device information, and access timestamps, collected automatically as part of operating the Taxller dashboard securely, including authentication logs and abuse-detection logging, consistent with the security practices described in Section 8.

Sources: we collect information directly from you; from Google, only if you choose to sign in with a Google account, and limited to the profile fields listed above; from Cloudflare, limited to the result of the anti-bot check; and from Stripe, billing-event data for checkout sessions, subscriptions, invoices, refunds, and cancellations, from which we retain the limited billing metadata described above. Once the Amazon connection becomes available, we will collect the SP-API data you authorize.

4. Cookies and Tracking

The marketing website. taxller.com sets zero cookies and loads zero third-party scripts. We self-host our fonts. We run no analytics, no advertising pixels, and no third-party trackers of any kind there. If you only read our marketing pages, we store nothing on your device, and no tracking script runs in your browser. This is distinct from the routine, non-tracking server logs described in Section 3 — every website automatically generates basic technical records (such as IP address and timestamps) as part of serving pages and keeping them secure; that is not a cookie, and it does not track you across sites or build an advertising profile.

The product: a small number of strictly necessary cookies only. Signing in to app.taxller.com requires them, and we use them only for that: an opaque session token; a signed session cache; app.dont_remember, set only when you clear the Remember me checkbox; and a locale preference. The session token and session cache are HttpOnly and, in production, Secure and scoped to app.taxller.com. During registration confirmation, sessionStorage holds taxller:pending-verify-email, the email address temporarily used to prefill the verification screen; your theme preference (light, dark, or system) is held in localStorage. None of this is an advertising cookie, none tracks you across other websites, and there is no analytics in the product either. The necessary cookies cannot be switched off without breaking sign-in.

The product: third-party scripts on the authentication screens. Two, and only there. Cloudflare Turnstile (challenges.cloudflare.com) runs the anti-bot check that protects registration, sign-in after repeated failed sign-in attempts, password reset, resend-verification, and demo sign-in from automated abuse. Google Identity Services (accounts.google.com) is loaded where sign-in with a Google account is offered, and only for that purpose. Each of those providers may set its own cookies or similar browser storage while performing that function, under its own privacy policy; we do not control that storage and we do not read it. Neither script is loaded anywhere else in the product, and neither is an analytics or advertising tag.

What we still do not do — anywhere, on the website or in the product — is analytics, advertising pixels, cross-site tracking, or profiling. This will not change silently. Before we introduce any cookie beyond the strictly necessary ones described above, or any analytics or tracking technology, we will update this Privacy Policy to describe what is being introduced and why, and we will obtain your consent before any such technology is activated where consent is required by law.

5. How We Use Information

• Provide the service — to run your Taxller account, store and organize the reports you upload, and power the dashboard. Once the Amazon connection becomes available, we will sync the Amazon data you authorize and maintain your double-entry books.
• Prepare books and tax forms — to prepare bookkeeping records and tax filings you request, including Form 5472 and pro-forma Form 1120 for foreign-owned single-member US LLCs, and Schedule C data packs for US resident filers.
• Track deadlines — to calculate and remind you of federal and state filing deadlines relevant to your business.
• Support — to respond to your questions and provide customer support.
• Security and abuse prevention — to authenticate you, verify your email address, enforce multi-factor authentication, run the anti-bot check on sign-up, sign-in, and password reset, rate-limit and lock out repeated failed attempts, and detect and block abuse of the service.
• Proof of consent — to keep a record of which dated versions of our Terms of Service and Privacy Policy you accepted, and when.
• Billing — to create and administer Stripe checkout sessions for subscriptions and token purchases; to maintain plan, billing-status, token-credit, and cancellation records; to issue invoices for paid purchases and credit notes for successful refunds and make them available to you in the Billing section; to send confirmations for subscription starts, token purchases, and renewals with the related invoice attached, refund confirmations with the related credit note attached, and scheduled-cancellation notices without any attachment; to maintain the accounting records of Andivano LLC, including copying invoice and credit-note PDFs and register data into our internal accounting workflow; and to keep a checkout-specific record of the billing confirmation and the dated Terms of Service and Privacy Policy versions associated with it.
• Account, security, and billing communications — to send transactional notices such as email-verification and password-reset messages, security alerts, subscription and token-purchase confirmations, renewal invoices, refund confirmations, and cancellation confirmations. Messages generated by Taxller are delivered through Resend, our transactional email provider; when a message carries an invoice or credit note, the PDF is included as an attachment and therefore passes through Resend as part of the message. Advance annual-renewal reminders are sent from Stripe's billing systems under our Stripe configuration.
• Legal compliance — to comply with applicable law, respond to legal process, and enforce our Terms of Service.

We never use client data to train AI models. This is a firm commitment, not a marketing line: your data is used to provide the service to you — it is not used to train, fine-tune, or otherwise improve any machine learning or AI model, ours or any third party's.

Where Taxller prepares a tax return or tax return information on your behalf, we use and disclose that tax return information only as permitted under Internal Revenue Code §7216 and its implementing regulations. Where §7216 requires your consent for a particular use or disclosure, we collect that consent separately, in the product, at the relevant point in the filing workflow — not buried in this Privacy Policy or in our Terms of Service.

6. How We Share Information

We do not sell personal information. We do not share personal information for cross-context behavioral or targeted advertising.

We share information only with the active providers below and, once the Amazon connection launches, with Amazon as described separately below. Each is engaged under contract with us. Most process information solely on our behalf as service providers. Google is the exception: when you choose to sign in with a Google account, Google also acts on its own behalf for the authentication it performs on its own systems, under its own privacy policy.

• Hostinger — hosting for the taxller.com marketing website.
• Amazon Web Services (AWS) — encrypted storage in the us-east-1 region holding the documents you upload and the invoice and credit-note PDFs we generate, and Amazon Bedrock (US regions only) for the Taxller AI assistant. Bedrock model-invocation logging is switched off, and your data is not used to train models.
• ExtraVM LLC — the dedicated United States server that has run the Taxller application and its database since September 8, 2026. The provider is not given access to the application, its database, or its secrets.
• Google LLC — sign-in with a Google account on our authentication screens, for users who choose it. Google tells us the email address, name, profile picture, and account identifier on the Google account you sign in with.
• Cloudflare, Inc. — Turnstile, the anti-bot check on our registration, sign-in after repeated failed sign-in attempts, password-reset, resend-verification, and demo sign-in screens.
• Resend — delivery of transactional email such as verification, password-reset, security, and billing notices. Billing messages may include your invoice or credit note as a PDF attachment, which Resend processes as part of the message content. Resend processes the recipient email address and the contents of those messages on our behalf.
• Stripe, Inc. — hosted checkout, payment processing, automatic tax calculation, subscription billing, invoices, and the customer billing portal. When you start checkout, we send Stripe your account email address, an internal account identifier, the selected Stripe price and quantity, and the current Terms-version label; for a token purchase we also send the token quantity. You enter payment details, billing name, billing address, and any tax ID directly on Stripe's hosted checkout pages; under our configured customer portal, billing address and tax ID can also be updated there. Stripe sends billing-event payloads back to Taxller, but our product database persists only the limited billing and consent metadata described above. Taxller does not store your full card number or card security code. Stripe handles information in its systems under its own privacy policy.
• Have I Been Pwned (HIBP) — password breach screening. At registration and when a password is changed or reset, our server sends HIBP only the first five hexadecimal characters of the password's SHA-1 hash in a k-anonymous request; neither the password, email address, nor IP address is sent to HIBP.

Once the Amazon connection launches, we will also share information with the following provider:

• Amazon — the SP-API connection, once it becomes available, to sync your financial, inventory, fulfillment, and insights data at your direction and authorization.

We may also share information: with our professional advisers (accountants, auditors, attorneys), under confidentiality obligations, to the extent needed for them to advise us; in response to a valid subpoena, court order, or other legal process, or where we believe disclosure is necessary to comply with law or protect our rights or the safety of others; and in connection with a merger, acquisition, financing, or sale of business assets, in which case we will require the recipient to honor the commitments in this policy.

7. Retention

Website enquiries: if you email us from the marketing website, we keep that correspondence for up to 24 months, or until you ask us to delete it, whichever comes first.

Amazon Selling Partner API data: once the Amazon connection becomes available, reports and financial events we retrieve under your authorization will be stored encrypted and deleted within 30 days of your deletion request, de-authorization of the connection, or account closing — whichever comes first — except where your own tax-recordkeeping obligations lawfully require us to keep derived records longer, as described in the next paragraph.

Books and tax records: we retain your books and tax-related records for as long as US tax law generally expects business records to be kept — typically up to seven years — or until you request deletion and we have no independent legal duty to retain the data, whichever is later.

Documents you upload and questionnaire answers: kept while your account is active, and deleted within 30 days of your deletion request or of your account closing, except where the books-and-tax-records rule above independently requires us to keep a derived record longer.

Account, authentication, and billing data: we keep account and billing metadata for as long as your account is active, and for a reasonable period afterward to meet our legal, tax, and accounting obligations and to resolve disputes. Invoices and credit notes are accounting records of Andivano LLC: we keep them — the billing snapshot, the limited payment-method summary, and the PDF — for seven years after they are issued, even if you delete your account; after deletion they are no longer accessible from your account. Sessions expire on their own and are cleared when you sign out. Authentication and abuse-detection logs are kept for up to 12 months.

Consent records: kept for as long as your account exists and for four years after it closes. A consent record is the evidence of the agreement between us, so it deliberately outlives the rest of your account data; it contains only the fields listed in Section 3 and no product data.

8. Security

We take reasonable, industry-standard steps to protect information, including: encryption in transit using TLS; encryption at rest for data stored on AWS, including the documents you upload; passwords stored only as argon2id hashes; multi-factor authentication (MFA) available on every Taxller account and required for sensitive operations such as connecting a sales channel or disabling MFA; least-privilege access controls, so that only personnel who need access to a given system have it; and MFA required on our own infrastructure accounts.

At registration and when you change or reset a password, we check the password against Have I Been Pwned's breach database using a k-anonymous, server-to-server request. We send only the first five hexadecimal characters of the password's SHA-1 hash; we do not send the password, your email address, or your IP address to Have I Been Pwned.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If we become aware of a breach affecting your information, we will notify you as required by applicable law.

9. Your Choices and Rights

You can ask us to access, correct, delete, or receive a portable copy of your personal information at any time by emailing info@taxller.com. We honor these requests regardless of whether a specific state privacy law applies to you or to us — this is our practice, not just our legal floor.

How that works in practice: these requests are handled manually by our team. Email info@taxller.com from the address on your account; we verify that the request really comes from you, acknowledge it, and complete it within 30 days, telling you if we need longer and why. An export is delivered as a machine-readable copy of your account data, your questionnaire and company answers, the documents you uploaded, and the invoices and credit notes, including their PDFs, that are still associated with your account. There is no self-serve export or delete button inside the product yet — we say so plainly rather than implying a one-click option that does not exist. Deletion removes your data on the schedule in Section 7, except where we have an independent legal duty to keep it, such as tax-recordkeeping obligations and the consent record described in Section 7.

For transparency: Taxller does not currently meet the revenue or data-volume thresholds that trigger the California Consumer Privacy Act (CCPA) or similar state privacy laws. We note this so you understand our current legal posture, not to suggest we treat your requests any differently — we honor access, correction, deletion, and portability requests either way.

10. Do Not Track and Global Privacy Control

Some browsers send a "Do Not Track" (DNT) signal, and some send a Global Privacy Control (GPC) signal. These signals exist to opt you out of cross-site tracking and of the sale or sharing of personal information for targeted advertising. We do neither: we run no analytics, no advertising, and no cross-site tracking on either taxller.com or app.taxller.com, and the only cookies we set are the strictly necessary sign-in and language cookies described in Section 4, which cannot be disabled without breaking the product. There is therefore nothing for a DNT or GPC signal to opt you out of, and we do not currently process or respond to these signals. If we introduce analytics, advertising, or tracking technology in the future, we will update this section to describe how we honor DNT/GPC signals at that time.

11. Audience

Taxller is a business-to-business (B2B) service. We offer our services only to businesses registered in the United States, including US limited liability companies owned by non-US residents. We do not offer our services to consumers, and our services are not directed to, and should not be used by, anyone under the age of 18. If we learn that we have collected personal information from an individual under 18, we will delete it.

12. Where We Process Data

Our own product infrastructure runs in the United States. Since September 8, 2026 the application and its database run on a dedicated server operated for us by ExtraVM LLC; Amazon Web Services (AWS) holds the encrypted storage for the documents you upload and the invoice and credit-note PDFs we generate, in the us-east-1 (Virginia) region, and provides Amazon Bedrock (US regions only) for the AI assistant. Copies of those PDFs and the related register data are also processed in Andivano LLC's internal accounting workflow on a virtual private server operated for us by a third-party VPS provider in the United States. The taxller.com marketing website is hosted by Hostinger. Our sub-processors — Google (sign-in), Cloudflare (anti-bot verification), Resend (transactional email), Have I Been Pwned (password breach screening), and Stripe (hosted checkout, payment processing, subscription billing, invoices, and the customer billing portal) — are independent companies that operate their own infrastructure under their own privacy policies; we do not control, and do not represent, where their systems store or process data. Once the Amazon connection launches, Amazon (SP-API) will also be a sub-processor. Like most cloud-based service providers, these companies may use secondary infrastructure — such as backups, content-delivery networks, or fraud-prevention systems — that can, in the ordinary course of business, involve processing outside the United States. We encourage you to review those providers' own privacy policies for details on how they handle data.

13. AI Assistant Data Processing

When you use Taxller AI, your questions and the organization context needed to answer them are processed through Amazon Bedrock within Taxller’s protected AWS infrastructure under a US inference profile. This processing takes place in the United States.

We retain assistant conversations indefinitely until you delete the thread. Deleting a thread deletes the messages in that thread.

When Taxller searches official sources, it sends an external search service only closed-vocabulary topic parameters, such as the form, topic, jurisdiction, and year. It never sends that service the text of your question, names, or identifying organization data.

Assistant answers may include quotations from official sources, including the IRS and state authorities, with links to the applicable source.

Model providers do not use your questions, organization context, conversations, or other Taxller data to train models.

14. Changes to This Policy

We may update this Privacy Policy from time to time, as the Taxller product develops and as our practices evolve — for example, if we introduce any cookie beyond the strictly necessary ones, or any analytics. The "Effective Date" at the top of this policy reflects when it was last updated. Where a change is material, particularly one involving new use of cookies, tracking, or personal information, we will provide notice and, where required by law, obtain your consent before the change takes effect.

15. Contact

Questions about this Privacy Policy, or requests regarding your information, can be sent to info@taxller.com, or by mail to Andivano LLC, 800 SE 4th Ave, Ste 101, Hallandale Beach, FL 33009, USA.