Support & Help — NexArchive

Start here — self-serve

The fastest way to an answer. Most questions are resolved here without writing to us.

Install NexArchive

Add it from the Chrome Web Store, pin it, open a supported AI chat, and click the icon. No account or sign-in.

Read the FAQ

Deployment, exports, data-on-uninstall and formats are answered on the home page FAQ.

Browse the source

NexArchive is open source under the MIT License. Read the code or check open issues.

Report a bug / request a feature

Open a public GitHub issue with your browser version, the AI platform, and steps to reproduce.

Privacy & data

What's stored and where (locally, in your browser), plus how to delete it. See the Privacy Policy.

Billing & refunds

Pricing, payment models, and your 14-day right of withdrawal are detailed in the Terms.

Troubleshooting & FAQ

Common issues and how to resolve them yourself.

How do I install NexArchive?

Install from the Chrome Web Store (Chrome or any Chromium-based browser such as Edge, Brave or Arc). After installing, pin the icon to your toolbar, open a supported AI chat, and click the NexArchive icon. The free version works immediately — no account, login, or server connection. If the icon doesn't appear, fully restart the browser and confirm the extension is enabled at chrome://extensions.

A platform is no longer detected after the AI site updated its layout

AI platforms change their page layout from time to time, which can temporarily break extraction. First, reload the chat page and update NexArchive to the latest version (chrome://extensions → Update). If it still doesn't work, open a GitHub issue or email anfrage@flowent.de with the platform name and a screenshot. This is a one-person project, so there's no guaranteed turnaround — but layout breakages are the top priority and fixes ship through the Chrome Web Store as soon as they're ready.

Where are my exports saved?

Exports are written to your computer's normal browser download location as a local file (a Markdown ZIP, or a Context Bridge JSON file). Nothing is uploaded — there are no cloud copies. If you can't find an export, check your browser's download history (Ctrl+J) and your Downloads folder. You can change the destination in your browser's download settings.

How do I delete my data?

NexArchive stores its data locally in your browser (chrome.storage.local) — not on any server. To remove it: clear the extension's data via chrome://extensions, or simply uninstall the extension, which makes Chrome delete its local storage automatically. Files you already exported live on your own disk and are deleted by you like any other file. Because there is no server account, there is no backend record to request deletion of.

Do you offer enterprise deployment, SSO, a DPA or an SLA?

NexArchive runs entirely locally and is maintained by a single founder, so there's no staffed enterprise desk and no contractual uptime SLA today. That said, the extension can be deployed via Google Workspace Admin Console or Microsoft Intune using a policy file, and because processing is local there is generally no data processing on your behalf. For team licences, deployment help, or compliance paperwork (including a DPA), email anfrage@flowent.de — these are handled personally on a best-effort, case-by-case basis.

How does billing work, and can I get a refund?

The free version is free, with no payment obligation. The Pro version is paid (a monthly subscription you can cancel monthly with 7 days' notice before the billing period ends, or a one-time lifetime licence). Payment is processed by Stripe; we don't see your full card details. Refunds follow the Terms: as a consumer you have a 14-day right of withdrawal and are reimbursed within 14 days of notifying us. Note the legal exception — if you expressly asked to start using paid digital content immediately and acknowledged you'd lose the withdrawal right, the refund right no longer applies. For any billing question, email anfrage@flowent.de.

Who runs NexArchive, and how fast will I hear back?

NexArchive is built and maintained by Luis Ens (Flowent), Freiburg, Germany — one person, not a team. There's no phone hotline, live chat, or 24/7 desk. Email and GitHub are the support channels, and we aim to reply within about 2 business days. Complex issues may take longer; we'll be honest about timing when we respond.

Ways to get help

Two real channels — pick the one that fits your question.

Email · best-effort

The right channel for billing, refunds, licence questions, enterprise/deployment inquiries, and anything private. Typically within 2 business days. No phone line or live chat.

anfrage@flowent.de →

GitHub Issues · fastest

For bugs, platform-detection breakages and feature requests. Include your browser/version, the AI platform, and steps to reproduce. Public issues are usually the quickest path to a tracked fix.

Open an issue →

Contribute · open source

NexArchive is MIT-licensed. Pull requests and fixes are welcome — if you can solve a problem in the code, that's the fastest route of all. See the repo's contributing notes first.

View the repo →

What to expect

Honest about being small: these are best-effort targets from a solo maintainer, not contractual SLAs. Busy periods or holidays may add delay — we'll tell you when we reply.

Email replies

We aim to respond within ~2 business days. Best-effort, not a guaranteed SLA.

Bug fixes & platform breakages

No guaranteed turnaround. Layout/detection breakages are prioritized; fixes ship via the Chrome Web Store once built and reviewed. Tracked in public GitHub issues.

Feature requests

Logged and considered for the roadmap. No promised delivery date — roadmap items are aspirational and may change. Upvotes and PRs help prioritize.

Enterprise & licensing

Handled personally by email, case-by-case. DPAs and deployment support are arranged individually, not offered as a standing staffed service.

Resources & legal

Everything else you might need, in one place.