Skip to content

Privacy and data

Submissions are stored in Basin, not Craft. The plugin reads them from Basin’s API when someone views them, and doesn’t save any personal data in Craft’s database.

Basin is where submissions are kept, so its retention settings and data-processing terms are the ones that apply. Each form’s retention period is shown on its page in the Control Panel, and can be changed there or in Basin.

What Where Personal data? How long
Submission lists and individual submissions Craft’s data cache Yes 1 minute
Recent submissions and the unread count (dashboard widget, menu badge) Craft’s data cache Yes 2 minutes
Background CSV exports storage/runtime/basin/exports/ Yes Until downloaded, or 24 hours, then removed by garbage collection
Background export jobs Craft’s queue Possibly (see below) Until the job finishes
Your Basin forms and their settings Craft’s data cache No The Cache duration setting, plus a last known copy kept so your site still works when Basin can’t be reached
Form Studio embed IDs and reCAPTCHA versions Craft’s database No Until you remove them, or 30 days after the form leaves your Basin project, then removed by garbage collection
The error log Craft’s database No: form IDs and page paths, without query strings Until dismissed, the form is back in the project or its embed code is saved, or 30 days after it last happened
The last form you viewed Your Craft session No Your session

Before anything from Basin’s form settings is cached, the plugin removes the notification and auto-reply email addresses, webhook URLs and the Turnstile secret key.

When someone edits a form’s settings, its notification and auto-reply addresses are read from Basin for that page only. They’re never cached or logged. The plugin never reads the Turnstile secret key or webhook URLs.

The plugin never writes submission content, email addresses, IP addresses or your API key to Craft’s logs.

Some cleanup depends on things outside the plugin.

Expired exports are deleted by Craft’s garbage collection. An export can’t be downloaded after 24 hours, but the file stays in storage/runtime/basin/exports/ until garbage collection runs. By default, Craft runs garbage collection at random on about 1 in 100,000 requests, so on a quiet site that can take days or weeks. To make it predictable, run it daily with a cron job:

Terminal window
php craft gc

Garbage collection also removes a form’s saved settings (its Form Studio embed ID and reCAPTCHA version) once the form has been missing from your Basin project for 30 days. It checks Basin’s current list of forms first, so it never removes settings for a form that still exists, and does nothing if Basin can’t be reached. The 30 days allow for a form that’s only gone for a while, such as one moved to another project and back.

Expired cache entries are deleted by your cache. Once they expire, cached submissions can’t be read. Removing them from disk is up to your cache:

  • Craft’s default file cache (storage/runtime/cache/) leaves expired files until they’re overwritten, or until its own occasional cleanup. To remove them straight away, use Utilities → Clear Caches → Data caches.
  • Redis and Memcached delete expired entries themselves.
  • A database cache keeps expired rows until its own occasional cleanup.

Utilities → Clear Caches → Basin data makes all the plugin’s cached data unreadable at once, whichever cache you use.

Exports of more than 1,000 submissions, and bulk actions on more than 50, run in Craft’s queue.

By default, Craft only runs the queue while someone has the Control Panel open. Since you start these jobs from the Control Panel, that’s usually fine. If you’ve turned off runQueueAutomatically, they wait until your queue runner picks them up.

Bulk action jobs only hold submission IDs. Export jobs also hold the search you exported with, which could include something like an email address you searched for. Craft removes a job once it finishes. A failed job stays in Utilities → Queue Manager until it’s retried or released, so release any failed export jobs you don’t need.

Attachments download through Craft, and only for users who can view submissions. They’re passed through to the browser, not kept on your site. Basin’s public attachment links, which work for anyone who has them, are never shown.

Values passed to hiddenFields are in the page’s source, where anyone can see them. Don’t use them for anything private.