Jibber Privacy Policy

Effective date: August 15, 2026

This policy explains what Jibber does with your data. Jibber is a Discord application that translates, checks grammar, and summarizes text. It is operated by Halpie ("the operator", "we", "us"), which is the personal information controller for the purposes of the Philippine Data Privacy Act of 2012 (Republic Act No. 10173).

Contact for all privacy requests: jibber@halpie.com

The short version

Jibber does not store the text you submit, the results it returns, or any message history.
Jibber stores one row per user: your Discord user ID, your optional output language preference, and two timestamps.
Your text is sent to Google Gemini to produce the result. Jibber uses a paid Gemini service, under which Google does not use your prompts or responses to improve its products or train its models.
We do not train models on your text, sell it, share it with advertisers, or profile you.
Jibber never reads your message history. It sees only what you type into a command, or the one message you deliberately select.

1. What Jibber processes

Text you submit

When you run a command, the text you typed, or the single message you selected through a context menu command, is sent to Google Gemini together with a fixed instruction and the language you want the output in. The result is returned to you as an ephemeral Discord reply.

This text is held in memory only for as long as the request takes, which is at most twenty seconds. It is not written to Jibber's database, not written to logs, and not retained after the reply is delivered.

Jibber sends store: false with every Gemini request, which asks Google not to retain the interaction.

Your saved preference

If you use /settings to pick an output language, Jibber stores a single database row containing:

your Discord user ID, which Discord assigns publicly and which identifies you as the owner of the preference;
the canonical language tag you chose, for example ja or pt-BR, or no value at all if you asked Jibber to follow your Discord language; and
the timestamps for when the row was created and last updated.

That is the entire contents of the database. There are no other tables and no other columns.

Operational logs

When a command fails, Jibber writes a diagnostic record. These records contain only fixed technical fields: the interaction type, the command name, an error category, how long the request took, which component failed, an error code, the AI provider name, the HTTP status it returned, the model that was used, and how many models were tried. Jibber also logs when it falls back from one model to another, and when the rate limiting service is unavailable.

No submitted text, no generated output, and no Discord interaction payload appears in these records. Jibber's request router goes further and logs nothing at all when it hits an unexpected error, rather than risk capturing content in an error message.

Cloudflare separately records standard invocation metadata for the Worker, such as timing and status, as part of hosting it.

What Jibber does not receive

Jibber uses Discord's HTTP interactions model. It has no Gateway connection, no Message Content privileged intent, and no bot token at runtime. It cannot read your channels, your message history, your direct messages, or your member list. It never calls Discord's API to fetch a message. When you use a context menu command, Discord includes that one message in the interaction it sends, and that is the only message Jibber sees.

2. Why we process it

Data	Purpose	Legal basis under RA 10173
Text you submit	To produce the translation, correction, or summary you asked for	Performance of a service you requested
Discord user ID and language preference	To remember your output language across commands	Performance of a service you requested
Operational logs	To detect and fix failures, and to prevent abuse	Legitimate interests of the operator

We do not process your data for advertising, profiling, scoring, or any purpose unrelated to running the command you invoked.

3. Who else processes your data

Running a command necessarily involves three providers:

Google LLC (Gemini API). Receives the text you submit and returns the result. Jibber uses a paid Gemini service. Under Google's current terms for paid services, Google does not use your prompts or responses to improve its products, and does not use them for training. Google retains limited data to detect abuse and to meet legal obligations. See the Gemini API Additional Terms.
Cloudflare, Inc. Hosts the Worker that runs Jibber and the D1 database that holds preferences, and records standard invocation logs. See the Cloudflare Privacy Policy.
Discord, Inc. Delivers your command to Jibber and hosts the reply. Your use of Discord is governed by the Discord Privacy Policy.

We do not sell, rent, or license your data. We do not disclose it to data brokers, advertising networks, or any monetization service.

Because these providers operate outside the Philippines, your data is transferred internationally when you use Jibber. We rely on each provider's own contractual and technical safeguards for those transfers.

4. One thing to be aware of about long results

Discord limits how much text a reply can hold. When a result is too long to fit in the messages available, and the app has permission to attach files in that context, Jibber uploads the result as a plain text file named jibber-result.txt so you still receive it.

That attachment is stored by Discord, not by Jibber, and it follows Discord's own retention practices for message attachments. This is the only situation in which any output of yours persists anywhere after the command finishes.

5. Retention

Submitted text and generated output: not retained by Jibber. Held in memory during the request only.
Your preference row: kept until you ask us to delete it, or until Jibber is permanently shut down.
Operational logs: retained by Cloudflare according to its log retention for the account, and used only for debugging and abuse prevention.

6. Your rights

Under the Data Privacy Act of 2012 you have the right to be informed, to access your data, to correct it, to object to processing, to have it erased or blocked, to data portability, to damages for a violation, and to complain to the National Privacy Commission.

Because the only thing Jibber stores is your preference row, most requests resolve quickly.

To delete your stored preference, email jibber@halpie.com from an address you can be reached at, and include your Discord user ID. You can copy your user ID in Discord by enabling Developer Mode in Advanced settings, then right clicking or long pressing your own name and choosing "Copy User ID". We will delete the row and confirm within thirty days, usually much sooner.

To see what is stored, ask using the same method. The answer will be your user ID, your language preference, and two timestamps.

You can also clear your language override yourself at any time by running /settings and choosing to follow your Discord language. That sets the override to empty but keeps the row. Only a deletion request removes the row entirely.

Removing Jibber from a server, or uninstalling it from your account, does not delete your preference row. Ask us if you want it gone.

If you are not satisfied with our response, you may complain to the National Privacy Commission of the Philippines at https://privacy.gov.ph.

7. Security

Every request from Discord is verified with an Ed25519 signature before Jibber processes it, so forged requests are rejected. Traffic to Google and Discord uses HTTPS. The Gemini API key is held as an encrypted secret and is never exposed in responses. Replies are ephemeral by default, and Jibber disables mentions in everything it sends so its output cannot ping anyone.

No service can promise perfect security, and we make no such promise here.

8. Children

Jibber is not directed at children. You must meet Discord's minimum age requirement for your country to use Discord, and therefore to use Jibber. We do not knowingly process data from anyone below that age. If you believe a child has submitted data to Jibber, contact us and we will delete it.

9. Changes to this policy

We may update this policy. The effective date above will change, and the full revision history is public in Jibber's repository. Where a change materially affects how your data is handled, we will announce it through Jibber's support channel where one exists.

10. Contact

Operator: Halpie Email: jibber@halpie.com