Skip to content
QuillOak

Your unpublished words

Privacy for poetry tools

A poem can contain names, grief, school work, relationships, or writing you have never published. QuillOak separates local-only tools from model-assisted tools and tells you before text leaves your browser.

Reviewed 18 July 2026

Local-only tools

The rhyme finder and form checker load a committed pronunciation index and run in your browser. The line or poem you type into those tools is not sent to QuillOak or an AI provider. Saved rhyme shortlists stay in your browser storage.

Model-assisted tools

The poem generator and analyzer send the fields you submit to a QuillOak server route, then through Vercel AI Gateway to the Google model named on the tool. QuillOak has no account history or poem database and does not intentionally store prompts or outputs. Responses are marked no-store and routine errors log only an error category—not poem text.

Requests enforce AI Gateway's no-prompt-training routing filter. Vercel says its gateway does not use prompts or responses for training; eligible providers are filtered by Vercel's current agreements. Providers may still retain limited safety data under their applicable terms. Read Vercel's current no-training documentationand Google Gemini API terms.

Analytics & operational data

Vercel Web Analytics and Speed Insights measure page visits and performance. QuillOak does not send form fields, poem text, prompts, or outputs as analytics events. The AI route uses a one-way hash of a network address for short-lived abuse controls; it does not place the address or poem into the shared cache.

Limits & safer use

Inputs are length-limited and rejected when the request is too large. Do not submit passwords, medical or financial information, a child's identifying details, or a protected full poem you do not have permission to process. For school work, follow your teacher's rules and treat generated feedback as a second opinion.

Deletion & contact

QuillOak cannot delete a saved poem because it does not offer server-side saved history. Clear your browser storage to remove a local shortlist. For a rights or text concern, follow the corrections and takedown checklist.