Task Pulse ยท Data Handling
HOW TASK PULSE
HANDLES YOUR DATA
Plain-English answers to the questions an office manager or owner asks before approving a new tool. Written for a non-technical audience.
Section 1
What Task Pulse records, and what it does not
It records
- A count of how many times each staff member taps each task category
- The date each tap was made
- The role of the person tapping (front desk, sales, etc.)
- Custom task labels a user creates, as short generic text
- Sign-in events for security auditing
It never records
- Customer names, account numbers, or any personal identifier
- Order details, invoice numbers, or anything tied to a specific person
- Anything typed into your other business systems
- Content of emails, letters, or documents
- Photos, files, attachments, or any customer media
Task Pulse is a counter, not a content tool. The user interface does not have a field where customer or personal information could be typed. The only free-text input accepts a short task-category label, which staff are instructed to keep generic.
Section 2
Where data lives and who can see it
Hosting
Cloudflare Pages with Cloudflare Workers and Cloudflare KV. Data is stored in Cloudflare's global edge network under ByteFlowAI's account.
Tenant isolation
Every office has its own office code. Every request is validated against that office code before any data is read or written. A request carrying office A's sign-in token can never read or write office B's data. Any attempt triggers an audit-log entry.
Staff visibility
A staff member sees only their own taps. They do not see co-workers' activity.
Admin visibility
Only the office admin (usually the business owner) sees the office-wide roll-up, per-person activity, and the final report.
ByteFlowAI visibility
ByteFlowAI has operational access to the Cloudflare account and can query data for support and report generation. ByteFlowAI does not redistribute, sell, or use office data for any purpose outside of the specific engagement.
Section 3
Authentication and access control
Sign-in
Each user enters the office code plus a personal six-digit PIN. PINs are hashed with a salt derived from the office code and never stored in plain text.
Session tokens
On successful sign-in, the server issues a cryptographically signed session token valid for 30 days. Every subsequent request is verified against that signature. Tokens cannot be forged to impersonate another tenant.
Revocation
The office admin can revoke any PIN instantly from the admin panel. The next request from the revoked user receives an unauthorized response and the session is rejected immediately. The revocation itself is recorded in the audit log.
Rate limiting
Failed sign-in attempts are throttled per office and per connection, and every failure is logged. To do this without storing anyone's IP address, the connection is identified by a short salted fingerprint (a one-way hash), never the raw IP. Successful sign-ins are never throttled, so a whole team signing in at kickoff is unaffected. Brute-force guessing of PINs is blocked and logged.
Audit log
Every sign-in, tap, PIN reset, PIN revocation, user creation, and any rejected access attempt is logged with a timestamp. The admin can view the log at any time.
Section 4
Retention and deletion
During the pilot
Data is retained for the duration of the pulse window and held for report generation.
After the pilot
If no follow-on engagement is started within 30 days of the pulse ending, the tenant record and all logs are deleted on request from the office admin. ByteFlowAI can also delete on demand at any time.
Audit log retention
Audit log entries expire automatically after 90 days.
Export
The office admin can export all counts as CSV from the admin panel at any time during or after the pilot. The office owns its data.
Section 5
Contact information (owners who request a pulse)
When you submit the setup form on the TaskPulse site, we store your name, work email, company, and your answers (Cloudflare KV, ByteFlowAI's account) and email them to ByteFlowAI so Matthew can reply. That information is used to set up and run your pulse and to follow up about your results. It is never sold or shared, and it is deleted on request. Staff never provide email addresses or personal contact details.
Section 6
Site analytics
The TaskPulse site keeps anonymous daily counters (for example, "the landing page was viewed N times today"). No cookies, no stored IP addresses, no per-visitor tracking of any kind. The public demo runs entirely in your browser; real pulses store task counts server-side exactly as this document describes.
Section 7
What Task Pulse is not
Task Pulse is not designed to store personal or customer information. It should not be used to record anything that could identify a specific person. The tool is intentionally built so that the ability to enter that kind of data does not exist.
If a future tool scoped after the pilot needs to handle sensitive or regulated data, that build is scoped separately with an appropriate compliant architecture.
If your compliance officer has specific questions that are not covered here, please reach out. ByteFlowAI will answer directly and revise this document if anything material is missing.
🎓
AI for Life Community
Practical AI automation lessons and a community of operators putting AI to work in real businesses.
Join →
🚀
Free Website Audit
A genuinely useful, no-strings review of where AI and automation fit your business. Matthew reviews it personally.
Get the audit →
📅
Book a Call
Have a specific question? Walk through it with us directly. No pitch, no pressure.
Schedule Now