FAQ

#Do I need to know SQL?

No. You ask in plain English. The SQL is there if you want to check it.

#Can Countdat change my database?

No. Jobs read through a read-only connection, in a read-only session, with a time limit - and a probe sends no query at all. See Read-only access.

#Where does my data live?

Each counter has its own database schema on Countdat's servers. Passwords for your own systems are encrypted and used only by the server.

#What if the answer is wrong?

Open Show the working and read exactly what it did. If a figure isn't in the data, the answer says so rather than inventing it.

#What happens when the data changes?

The answer is rewritten, and its History keeps each count it reached. A published name keeps the version you published.

#Who can tap my counter?

Whoever you choose - anyone with the link, or members you invite, who sign in. See Who can tap.

#Is anything ever deleted?

No. A correction is a new row pointing at the old one; a delete is marked, not erased.

#Is the data live?

Taps, sentences and forms add rows the moment they're made. Jobs run on a schedule you choose - hourly is typical - so job data is as fresh as the last run.

#What can I connect?

Files (CSV, spreadsheets, emails, PDFs and photos of documents), scheduled jobs reading MySQL databases, and - in pilot - signed probes. Google Sheets sync and SFTP aren't supported; export the file and import it.

#Can another system push data into a counter?

Not yet. Today rows come from people, files, jobs and probes.

#Can I ask a follow-up to an answer?

Each answer stands on its own. To take a different angle, ask a new question - be specific about the field, the time range, or what to leave out.

#How much does it cost?

For plans and pricing, see app.countdat.com or write to sales@countdat.com.