If it's just a single page and that's all you want to do, you might consider just writing data to some kind of flat file. E.g., assuming you had some array, $data of users and their choices or whatever, you could always just store this array in a flat file:
// assuming $data is an array of users and YES or NO data
// write it to a file
if (!file_put_contents("/path/to/some/file/on/the/server", serialize($data))) {
throw new Exception("Could not write data to the file!");
}
// read data from the file
$serialized_data = file_get_contents"/path/to/some/file/on/the/server");
if (!$serialized_data) {
throw new Exception("Could not fetch serialized data from file");
}
$data = (unserialize($serialized_data);
if (!$data) {
throw new Exception("fetched data did not unserialize correctly");
}
This would introduce a variety of other considerations: performance, for example. DBMS systems are constructed to store and retrieve data efficiently and use caching mechanisms, etc. If you have to read and parse the data file for each page request, this is not ideal. Another question is how to control who gets to write the file. Access control usually requires user athentication which is usually accomplished by having a database of users with their passwords, etc.