Grammarbar

Privacy

Last updated 15 October 2026.

Terms · Cancellation · Refunds · Privacy · Legal · GDPR · Contact

Who is responsible

The controller for Grammarbar account data and for the text you send to be corrected is POSADSKI SOFTWARE, programiranje in druge storitve, d.o.o., Mestni trg 10, 1000 Ljubljana, Slovenia. Email support@posadskiy.com. The business register, the tax number, and the share capital are on the legal page.

How to use your GDPR rights is on the GDPR page.

The sentence you select

When you press your shortcut, Grammarbar sends the selected text to OpenAI so it can return a correction. Grammarbar does not store the selected text or the rewrite. OpenAI receives the text only to produce that correction. OpenAI does not use API data to train its models. OpenAI may keep the request for up to 30 days to monitor abuse. That vendor retention is separate from Grammarbar’s own storage.

Where the app you are writing in shares the selection through Accessibility, Grammarbar reads it from there and does not copy it. Otherwise it copies the selection and puts your previous clipboard back as soon as it has read it, so a clipboard history app may still record that copy. The correction is pasted through the clipboard marked as transient, which clipboard history apps such as Maccy, Paste, Raycast, and Alfred do not record, and your previous clipboard is put back afterwards. Grammarbar does not read password fields.

Logs can include the account id, latency, status, and token counts. They do not include the sentence. Grammarbar also keeps a monthly count of rewrites and tokens per account, to apply the fair-use limit and to price the plans.

The legal basis is the contract: we cannot correct the selection without sending it. We do not use the selection to train a model, and we do not sell it.

Your account

Sign-in and registration go through the authentication service at api.posadskiy.com, operated for this company. You can use a username and password, or continue with Google. The Mac app keeps the access token, the refresh token, and the user id in the Keychain.

To move a browser sign-in to the Mac app, the app opens this site with a one-time challenge. The site asks Grammarbar for a code bound to that challenge and opens the app with only that code. The app redeems the code once, within five minutes, with a secret only it holds. Until then the tokens are stored encrypted, together with the email address the app shows. Tokens are never put in a link.

After Google sign-in, this site reads a one-time code from the address, exchanges it for a session, and opens the Mac app with a handoff code. A username and password sign-in does the same. The account page keeps that session in the browser for up to 30 days so it can show the plan, start checkout, cancel, and delete Grammarbar’s copy of the account. Sign out clears the browser session.

Grammarbar stores the user id, the plan, the subscription id and its status, the end of the paid period, and how many rewrites and tokens the account has used each month. The legal basis is the contract, and, for security logs, our legitimate interest in keeping the service reliable. You can object to processing that is based on legitimate interest. The objection is described on the GDPR page.

Payment

The seller of record named in the terms is a separate controller for the payment. They handle the card, tax, invoices, and refunds. Canceling stops the next charge and does not refund the period already paid. The plan keeps working until that period ends. The refund page states the 14-day withdrawal right. Grammarbar does not store the card number. Their notice is the payment privacy notice.

Cookies and storage

This site does not use advertising cookies. It sends the page address, how long the tab stays open, and browser errors to Grafana Labs so we can see how the site is used. That measurement keeps a session id for the open tab and does not set a cookie. The account page stores the session in the browser’s local storage under the key grammarbar.session for up to 30 days. That storage is required to show the plan and to cancel. When checkout opens, the payment page may set its own cookies to take the payment.

Who else receives data

We share data only with the services that run Grammarbar:

  • OpenAI, which receives the selected text and may retain it for up to 30 days.
  • The seller of record, which receives the user id and the plan you buy so it can charge and refund.
  • Google, only if you choose Google sign-in.
  • The host of the database that stores the plan and the rewrite and token counts.
  • Grafana Labs, which receives the page address, visit timing, and browser errors from this website. It does not receive the sentence you select.

The model provider, the seller of record, and Grafana Labs can process data outside the European Economic Area. Those transfers use the provider’s standard contractual clauses or another lawful transfer tool. You can ask us which provider is in use, and for a copy of the relevant safeguards.

How long we keep it

The selected text is not kept after the correction is returned. The browser session lasts up to 30 days, or until you sign out. The plan lasts while the subscription is running. Delete account on the account page turns Grammarbar off in the Mac app and removes the plan and the subscription id. The number of free rewrites already used, and the monthly rewrite and token counts, stay with the sign-in account. Opening Grammarbar again does not grant the free allowance a second time. An open sign-in handoff is gone after five minutes. Payment records stay with the seller of record for as long as tax law requires that record to be kept. Security logs are kept only as long as they are needed to operate and protect the service.

Children

Grammarbar is not directed at anyone under 16. We do not knowingly create accounts for children.