Who is responsible
PlainBilling is run by Jan. The previously listed address, hello@plainbilling.com, is unverified and is not a reliable contact route. A working privacy contact and complete operator details must be published before collection resumes.
Waitlist and enquiry data
The intended pilot form asks for an email address, current email tool, approximate list size, main migration problem, planned switch timing, number of active automations, ecommerce platform and privacy acknowledgement. The form remains closed and the proposed pilot is not accepting enquiries. Do not submit customer lists, account passwords, API keys or billing documents through it.
Tally
The Tally-hosted enquiry form is closed and is not embedded on the homepage. If you separately visit its URL, your browser connects to Tally. A separate internal test form accepted one synthetic submission and delivered a notification to the operator's Google mailbox on 2026-09-28. This did not test submission through the original enquiry form, which remains closed. Tally's privacy policy describes its own processing. Retention settings, processing terms and the public privacy contact still require review before the pilot accepts enquiries.
Contact collection is paused
A DNS check on 2026-09-27 found no published MX records for plainbilling.com. A domain mailbox is not required for the tested Tally-to-Google notification route. The website offers no email submission button or replacement form. Contact collection will resume only after the original form and the required privacy information are verified.
Visitor measurement
No client-side visitor analytics currently run because the previously configured GoatCounter site does not exist. PlainBilling does not use Google Analytics, ad tracking or cross-site marketing profiles. Google Search Console provides aggregate search performance data; the hosting provider may process request logs for security and delivery. This notice will be updated before visitor analytics are activated.
Retention and provider settings
A fixed retention period and the final provider configuration have not yet been published. The proposed contact address remains unverified; it must not be relied on for requests. Customer-data access for a migration requires a separate agreed scope and privacy review.
Your GDPR rights
You may ask for access, correction, deletion, restriction, portability or an objection where the law provides it. A verified route for privacy requests must be provided before waitlist collection resumes. You may also complain to your local data-protection authority.