bagobs.com is the website through which visitors can request information about drawing and painting classes in Columbus, Ohio.
This version was published on November 19, 2026. It describes what this website actually does with information. It is not a promise about a different product, a mobile app, or a future registration system.
- Who operates this website
- What this policy covers
- Information you choose to send
- Technical information
- Why contact details are collected
- How the form works
- Where requests are stored
- Why requests are not emailed
- Who can see a saved request
- Hosting and other companies
- Analytics and advertising
- Selling or sharing information
- How information is protected
- How long requests are kept
- Correction and deletion
- Privacy rights
- Children and parents
- Cookies
- Changes to this policy
- How to reach us
Who operates this website
The site is operated for in-person drawing and painting instruction in Columbus, Ohio. Drawing & Painting is the name shown on this website. Reach the studio by phone at +1 614 237 5750.
What this policy covers
This policy covers information processed by this website: the class-information form, the server that receives it, and the private database where a request is stored. It also covers technical data that a normal web server may create in order to deliver a page. It does not describe a student portal, a payment processor, a mailing list, or a classroom camera system, because none of those are part of this website.
Information you choose to send
If you use the form, you are asked for your full name, an email address or a phone number (or both), the class subject you want to ask about, and a short message. You are also asked to confirm that you have read this policy. If the subject is kids’ classes, the form asks the sender to confirm that they are the parent or legal guardian. Those fields are voluntary in the sense that you decide whether to submit the form, but the server will not save a request that is missing a name, a way to reply, a subject, a usable message, or the privacy confirmation.
Please do not include a child’s name, birth date, school, medical information, or photograph. The form is not designed to collect that information, and a message that contains it is still stored as text if the rest of the form is valid. Leave those details out.
Technical information
Delivering a page requires the server to receive the usual connection data, such as the requested address, the time, the browser type, and the IP address of the connection. Whether those details are written into a hosting access log depends on the host that is chosen later. This application does not copy the raw IP address into the inquiry record. For abuse control, it stores a salted hash of the IP address in a separate rate-limit table, together with the hour window and a hit count. That hash cannot be used as a phone number or an email address. The inquiry record itself contains the form fields, the time the request was saved in UTC, a yes-or-no flag for the guardian confirmation, and a hash used to recognize a repeated submission.
Why contact details are collected
The only purpose of the form is to let the studio reply about drawing and painting classes using the email address or phone number you supply. The message gives context, such as whether you are asking about watercolor, a private lesson, or a child’s class. The information is not used to create an account, to show you targeted ads, or to build a public profile.
How the form works
Your browser sends the form to the address /api/contact.php on this same website. The server checks that the request is a POST, that the body is not unreasonably large, and that it is either JSON from the page script or a normal form submission if JavaScript is unavailable. It checks that the request comes from this site, using the Origin or Referer header. It checks a hidden form token that was written into the page when the site was built. It then checks each field. If the checks pass, the server writes one row to a SQLite database. The page shows a thank-you only after that write succeeds. If the write does not happen, the page says so.
Where requests are stored
Saved requests live in a SQLite file that the application refuses to place inside the public website folder. The path is set in a private configuration file or with the INQUIRY_DB_PATH environment variable. The file is meant to be readable only by the server account that runs PHP and by an administrator using the private command-line tools. It is not linked from any page, and it is not listed in the sitemap.
Why requests are not emailed
The form does not send email. The PHP mail function is not used. There is no SMTP connection, no third-party form inbox, and no copy of the request forwarded to a teacher by email from this website. A reply, if one is made, is a separate phone call or email that a person sends later using the contact details you provided. This page does not promise how quickly that reply will happen.
Who can see a saved request
Access is limited to people who administer the server and the private storage folder. There is no public admin screen. The command-line tools that list or export requests are not routed as website pages. A hosting provider can also access the server if its staff or systems operate the machine. Requests are not sold and are not handed to an advertising network.
Hosting and other companies
The host that serves this website processes the connection in order to deliver the pages. That can include short-lived connection data and access logs kept by the host. This website does not add an analytics vendor, tag manager, font host, map embed, payment service, or email-delivery service. Fonts and photographs are files on this site.
Analytics and advertising
Pages do not load analytics scripts, advertising pixels, or social media plugins. There is no advertising profile built from your visit. If that ever changes, the cookie policy and this policy have to be updated first, and any optional script has to stay off until the site has a real consent control for it.
Selling or sharing information
Inquiry information is not sold. It is not shared for cross-context behavioral advertising. It is not traded for other data. A disclosure that is required by law, or access by the hosting company as part of running the server, is different from a sale. The form does not offer a list of partners because there is no partner list.
How information is protected
The public site and the database are separated by the server’s folder layout. Database writes use parameterized queries. Visitor-facing errors do not include database messages, file paths, or the text you typed. The application does not encrypt the SQLite file at rest. Protection depends on server permissions, on keeping the file outside the document root, and on restricting who can log in to the machine. No website can honestly promise that stored information is immune to misuse, loss, or a hosting incident.
How long requests are kept
An inquiry record is kept for 90 days. Each time the form handler opens the database, it deletes inquiry rows older than that period, and it deletes rate-limit rows older than 48 hours. The same inquiry deletion can be run with the private command tools/inquiries.php purge. Deployment instructions tell the operator to run that command once a day so an old row does not wait around during a stretch when nobody submits the form. This policy does not control how long a hosting company keeps its own access logs.
Correction and deletion
You may ask for a correction or deletion of a request that is still on file. Call +1 614 237 5750 or email [email protected]. The operator needs a reasonable way to tell that the caller controls the email address or phone number on the row before changing or deleting it. That check is done by a person. There is no self-service deletion button, because an open button would let someone else try to erase your request. After a match is confirmed, the row can be removed with the private delete command. Deletion from this database does not automatically erase a copy that may exist in a host access log or in a backup the host controls.
Privacy rights
People in the United States have different privacy rights depending on federal law and the state where they live, including Ohio. This policy does not restate every statute and does not claim that a particular state portal has been built into the site. What the operator will do, regardless of the label a statute uses, is respond to a verified request to see, correct, or delete an inquiry that this website still holds, and will not sell that inquiry. Some records may need to be kept for a short time when the law requires it. If a request cannot be completed, the operator should say why.
Children and parents
The kids’ class page is written for parents and legal guardians. Children are not asked to create accounts, enter a chat, upload drawings, or register themselves. The form does not ask for a child’s name or age. A request about a children’s class must come from a parent or legal guardian, and the form asks that adult to confirm their role. That confirmation is a statement by the adult. It is not, by itself, a complete answer to every duty under the Children’s Online Privacy Protection Rule or later FTC guidance. If the site later collected personal information directly from children under 13, the operator would need a separate legal review and a verifiable parental consent process before doing so. A sentence telling children not to use the form would not be enough for that different design.
The FTC explains the rule at ftc.gov. This link is provided as a public reference. The FTC site has its own notices.
Cookies
Cookie use is described in the Cookie Policy. In short, the pages do not set cookies and do not use browser storage. Read that page before assuming a banner or an advertising cookie exists. It does not.
Changes to this policy
When the policy text changes, the published date above is updated and the pages are rebuilt from the site configuration. The previous text is replaced on the site. Continuing to browse does not, by itself, sign you up for a class. If a change affects how a request already on file is used, the operator should not quietly expand that use beyond the reply you asked for.
How to reach us
You can ask a privacy question by email at [email protected] or by phone at +1 614 237 5750. Please say that your question is about privacy, and include the email address or phone number you used on the form so the right row can be found. Do not send sensitive documents by an unsolicited channel.
