datawriteupBack to DataWriteup

Privacy

Your data, in plain language

This page explains how DataWriteup handles account data, uploads, AI processing and sharing during the beta.

Private by defaultYour files, datasets and draft write-ups are limited to your account unless you choose to share.
AI at a clear boundaryUploading and reading a file does not send its content to OpenAI. If AI is needed, DataWriteup asks before generating or updating tables.
You review the resultGenerated tables remain editable. Nothing becomes a reusable dataset until you save it.

When you add data

DataWriteup stores uploaded files in private storage associated with your account and reads them to identify text and tables. Access controls protect the original files and the structured evidence produced from them.

When AI is used

When you choose Generate tables, DataWriteup first checks whether it can preserve an already structured file directly. When AI interpretation is needed, it asks you before sending your instruction and bounded, relevant text or table excerpts to the OpenAI API. Updating tables with another prompt uses the same boundary. The original files remain in private DataWriteup storage.

OpenAI states that data sent through its API is not used to train OpenAI's models by default unless the customer opts in. OpenAI may retain API content in abuse-monitoring logs for up to 30 days by default.

Read OpenAI's API data controls

Your choices

  • Choose Not now at the processing notice to avoid the OpenAI request.
  • Review and edit table columns and cells before saving a dataset.
  • Keep work private, or share a write-up only when you deliberately create a share link.