How Gherkinizer handles your data

Your requirements are not written to our logs

The requirement you paste and the feature file you get back are never written to our application logs. What we record is the shape of each request: how long the input was, which model answered, how long it took, and whether the output parsed. The content itself stays out of our logging system entirely.

What is stored, and where

• Feature files you save. Held in your account so you can come back to them. Deleting one deletes it.
• Your account. Email address, plan, and usage counts.
• Requirements you do not save. Not stored. They are sent to the model to answer that one request, and we keep no copy once it is answered.
• Uploaded documents. Passed to Google's Gemini Files API to be read for that generation. Upload requires a signed-in, verified account.

The model

Generation runs on Google's Gemini models through the Google AI API, under Google's terms for that API rather than the consumer terms that apply to a free chat product. Your requirements and your feature files are not used to train any model.

If your review needs the formal wording, the Google AI API terms are the governing document. We have summarised them here in good faith, and we would rather you check them than take our word for it.

Retention

Operational logs, meaning the metadata described above, are retained for 30 days and then deleted. Saved feature files and account data are kept until you delete them or ask us to.

Deletion

Delete a saved feature file from your saved features page at any time. To have your account and everything in it removed, email info@gherkinizer.com and we will confirm when it is done.

Scope of this page

This describes how the product handles your data today. It is not a data-processing agreement and not a security certification. If your procurement process requires either, email us and we will tell you exactly what we can provide.