PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Checkbox option to not save entries to database

  1. LumpySimon

    There have been a few support posts by people asking how to not store database entries for a form (e.g. here and here).

    I'd like to request this as a feature due to the following situation: I am using Gravity Forms to create a 'tell a friend' form, but the privacy policy of my client specifically states that they do not store the email addresses of either the sender or the receiver.

    Luckily there is code that achieves this (, but it would be great if there could just be a simple "Store entries in database?" checkbox when you create the form.

    Many thanks

    Posted 11 years ago on Monday April 25, 2011 | Permalink
  2. vtisix

    I would like to support this request. One slight change would be to store entries by default, and the checkbox would disable this feature. So, it would say something like: "Do not store form entries in the database."

    I have no personal problem with implementing the auto-delete function as described in the other thread. However, this gets tricky for a multisite installation and admins of sub-sites can create their own forms. The form id, then, would obviously change from site to site and cause all kinds of issues.

    Posted 11 years ago on Friday July 29, 2011 | Permalink
  3. occupy_gravity

    I strongly support this request, too. Why?

    The ever-growing popularity of WordPress makes it a popular target among hackers, too. There should be an option to not store entries, in case visitors send confidential info.

    Please consider privacy as a top priority.

    Posted 10 years ago on Friday November 18, 2011 | Permalink
  4. Carmello

    I also support this feature. To tie us over until the feature hopefully makes it into a release can someone from the gravity forms team provide a solution?? I really need this functionality.

    Just for clarity this is my situation... I'd like to allow people to submit sensitive info that will get emailed to the admin notification but not submitted to the database. There's no way in the world that I would want to be storing hundreds of peoples SSN in my wp database.


    Posted 10 years ago on Sunday November 27, 2011 | Permalink
  5. You can delete the entry immediately after it's stored, but there is no way to prevent storing it in the first place. The notification emails are based on the stored entry, so it's required first. There are solutions posted in the forum that explain how to delete the entry immediately after storage. I can link to them for you if you have access to the support forums vs. the pre-purchase forums.

    Posted 10 years ago on Thursday December 1, 2011 | Permalink
  6. jeroenlh

    Indeed, it would be nice to be able to prevent the data from being stored in the DB.
    I want it because I am building UI forms with GF for a WP webapp, so storing does not make any sense at all. It would be silly.

    One (dirty way) to prevent storage is to make sure there is nothing to store :).
    This can by done by deleting the $_POST data before GF is able to store it.

    This seems to work OK in the gform_pre_submission_filter: handle the data in there and then destroy it. I use unset($_POST) for it.

    The only thing left after that is to delete the entry in the wp_rg_lead table.

    Posted 10 years ago on Monday January 23, 2012 | Permalink