What Forsive collects, why, and what happens to it.
Forsive is developed and operated by Golam Sarowar Jahan Rifat, an individual developer, not a company. This notice explains what information Forsive collects, why, and what happens to it, and applies to everyone who uses Forsive.
Forsive is a desktop application that reads, edits, and organizes files stored on your computer using an AI model. Most of what Forsive does happens entirely on your machine. A small amount of information is sent to a relay service that the developer operates, which forwards your requests to Google's Gemini API and returns the response. This notice covers both the desktop application and that relay service.
Information you provide
Information collected automatically
Information we do not collect
Forsive does not collect, transmit for storage, or retain the content of your chat messages, the names of files in your workspace, or the content of your files. The one exception: if you explicitly submit a thumbs-down feedback note (see above), a short snippet of that specific reply is stored along with your note. Everything else is used only transiently, as described below, to carry out the request you made.
Why we're allowed to use this information
Under GDPR, we need a valid reason for each way we use your information:
When you send a message, Forsive sends your message and the names of the files available in your workspace to the relay, which forwards them to Google's Gemini API and streams the reply back. This exchange is not saved by the relay.
If the assistant needs to read, edit, create, or organize a specific file to answer you, the content of that file is sent through the same path, for that request only. Forsive does not send file content that isn't relevant to the task at hand, and the relay does not retain it afterward.
Forsive never modifies your original files. Any edit or new document is written to a new file, and your source file is left untouched.
If you submit a thumbs-down feedback note, the note you write and a short snippet (up to 300 characters) of the reply it's about are sent to the relay and stored there, tied to your device identifier and email, so the developer can review it and use it to improve Forsive. This only happens when you explicitly click "Save feedback."
If you use Settings → Contact us, the email, category, and message you enter are sent to the relay and stored there, tied to your device identifier, so the developer can respond. This only happens when you submit the form.
If you buy credits, your purchase is handled by Paddle (see Section 4). Your email address and device identifier are sent to Paddle so the credits can be attributed to your account; your payment details go directly to Paddle and never pass through Forsive's own systems.
Forsive uses the Google Gemini API, operated by Google LLC, to process requests, through a paid API key that the developer holds and pays for. Under Google's terms for paid API usage (see ai.google.dev/gemini-api/terms), content submitted this way is not used to train Google's models and is not subject to routine human review. Google may retain data briefly for abuse detection and legal compliance, consistent with its own policies. Google's terms may change independently of this notice; refer to Google's published terms for the current, authoritative language.
If you buy credits, Forsive uses Paddle.com Market Ltd ("Paddle") to process the purchase, acting as merchant of record. Paddle collects your payment details directly — Forsive and its developer never see or store your card information — and separately receives your email address and device identifier so the purchase can be credited to your account. See Paddle's Privacy Policy for how Paddle handles your information.
Both Google and Paddle operate outside the EU/EEA for at least part of what they do, so using Forsive means some of your information leaves the EU. Paddle's UK entity is covered by the European Commission's adequacy decision for the UK, which lets data move there without extra safeguards. Transfers to Google's and Paddle's US operations rely on Standard Contractual Clauses, a standard EU-approved contract for this kind of transfer.
We do not use any advertising or analytics services, and we do not sell or share your information with third parties for marketing purposes.
On the relay:
On your computer, under your application data folder, Forsive stores:
None of the information stored on your computer is transmitted anywhere except as described in Section 3.
Under GDPR, you have the right to:
Forsive doesn't make automated decisions about you that carry legal or similarly significant effects, so the GDPR right relating to that doesn't apply here.
To exercise any of these, contact us using the details in Section 10.
In practice, day to day:
We take reasonable measures to protect the information described in this notice, including transmitting data over encrypted connections. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If a breach involving your information ever happens, we have a process for assessing and reporting it as required by law, including notifying the relevant authority and, where the risk to you is high, notifying you directly.
Forsive is not directed at, or intended for use by, children, and we do not knowingly collect information from children. If you believe a child has provided us with information, contact us and we will delete it.
We may update this notice as Forsive changes. If a change materially affects what information we collect or how it's used, we will present the updated notice to you again rather than applying it silently. The effective date below reflects the most recent revision.
Questions, concerns, or a data deletion request: Forsive team (hello@forsive.com)
Effective date: September 12, 2026