Privacy notice
This notice describes DeniFlow’s current account, business-record and support workflows. Contact us before uploading data if your organization has specific hosting, retention or contractual requirements.
Your information, at a glance
- Account data supports sign-in, security and support.
- Your organization controls the customer records it adds.
- Website analytics are optional; customer ledger data is excluded from analytics.
In this document
- Who decides how data is used
- Account and business information
- Why we process it
- Sources and processing purposes
- Service providers
- Regional prices and password safety providers
- Public traffic and location choices
- Manual WhatsApp drafts
- International processing and contractual requests
- Access and support
- Cookies and security information
- Optional website analytics
- Retention and deletion
- Personal-data rights and complaints
- Changes and appropriate data
- Your requests
1. Who decides how data is used
DeniFlow administers its own account, security, service and inquiry workflows. A business using a workspace decides which customer information it uploads, why it uses that information and which team members may access it. For that business-record processing, DeniFlow provides the service on the business’s behalf. Contact DeniFlow through the contact form about account or website data, and contact the relevant business about its customer records. Confirm the contracting operator and any required data-processing agreement before entering a regulated or specially negotiated arrangement.
2. Account and business information
Account details include your email, display name and optional contact phone. Workspace information includes business details, team memberships, customer contact details, credit invoices, manually recorded receipts, allocations, collection notes and correction history. Your organization decides which customer records it enters and who may access them.
3. Why we process it
We use account information to authenticate you, protect sessions and administer access. Business records provide the receivables workflow you request. Audit events and bounded abuse counters support accountability, safe retries and security. Registration submissions also record the policy version, time and a hashed email reference for the agreement and notice acknowledgment; a submission record is not proof of verified identity. Contact inquiries are used to review and respond to your request; the form does not subscribe you to marketing.
4. Sources and processing purposes
Information comes from your registration and settings, your organization’s entries and imports, your support or contact messages, and technical requests made while using the service. Account and workspace processing is used to deliver the requested service. Security and audit processing supports abuse prevention and accountability. Optional analytics follows your choice. Legal obligations and valid requests may require some records to be preserved. Acknowledging this notice does not amount to blanket consent for every use or optional marketing.
5. Service providers
Supabase provides authentication, including password and authenticator verification. Cloudflare Workers and D1 run the application and store workspace records; configured object storage holds encrypted application snapshots. Resend handles authentication email through the configured SMTP service and application messages when application delivery is configured. Providers may process information outside your country. No country-specific data residency guarantee is currently offered.
6. Regional prices and password safety providers
Frankfurter supplies daily currency reference rates. The application requests the selected currency pair; it does not send account or customer records to this rate service. The Pwned Passwords service receives a five-character prefix of a password hash for signup and password-change checks, not the full password or full hash. DeniFlow stores salted, peppered slow-derived password-history proofs to prevent reuse of observed passwords. These proofs are excluded from downloadable application snapshots.
7. Public traffic and location choices
Public pages report page paths and approximate country information from the hosting edge for aggregate traffic counts. Private sign-in, invitation, workspace and staff routes are excluded. These counts do not use a persistent visitor cookie or identify unique people. When you allow optional analytics, this application can also retain the request IP in encrypted form for up to seven days for consented visitor analysis. Share device location is a separate optional action: your browser asks permission, and only after that action are browser-supplied coordinates and their accuracy estimate retained for this visit for up to 24 hours. Location may be unavailable or inaccurate and is not proof of residence. You can use the service without sharing it. Administrators need fresh MFA and an audited reason to view personal visitor details; developers receive aggregate metrics only. Declining analytics or Remove this visit’s details removes the current visit’s IP and coordinates. Previous visits without a persistent identifier remain subject to their retention window. Contact us for a broader verified privacy request.
8. Manual WhatsApp drafts
A permitted workspace user can review a customer phone number and message, affirm permission to contact the customer and explicitly open WhatsApp. That action shares the reviewed recipient and message with WhatsApp. Sending happens outside DeniFlow. Opening a draft does not record delivery; a user can separately log their manually reported contact. There is no inbound conversation sync or WhatsApp Business API delivery verification.
9. International processing and contractual requests
Service providers may process information outside Kenya. This notice is not itself a cross-border transfer safeguard, a signed DPA or a promise of regional hosting. Ask about the applicable provider terms, locations and transfer arrangements before a business uploads data with such requirements. A DPA must identify the parties, instructions, data categories, subprocessors, security obligations, assistance, incident notification and return or deletion arrangements. Do not assume a GDPR or other certification from use of these tools.
10. Access and support
Organization permissions control access to business records. Platform staff use a separate console; developer permissions exclude customer support cases and inquiry contents. Temporary support summaries require an authorized organization administrator’s consent to a named staff identity, scope and duration. Administrative changes and sensitive exports are audited.
12. Optional website analytics
Our public marketing pages load the Google Analytics tag with measurement disabled until you allow analytics. The tag request itself is received by Google. Your optional choice enables page visits, trial-button clicks, product-example interactions and a lead event after a contact request is saved. Google receives technical information such as browser and approximate location derived from network requests. Analytics cookies identify a browser, not an account. Advertising features are disabled. We do not install this tag in the customer workspace, sign-in, registration, confirmation, invitation or staff console. Event parameters exclude names, emails, phone numbers, messages and financial records. Unknown URL query parameters disable tracking for that document. Trial-button clicks are interest signals, not completed registrations or trials. Use Privacy choices to decline or change your preference; declining stops measurement and removes this site’s analytics cookies. The choice and permitted analytics cookies last up to 180 days. Declining does not erase data already processed by Google.
13. Retention and deletion
Canceling a subscription stops access according to its status; it does not automatically erase financial history. Issued financial records are corrected through an audited workflow. The core account and financial ledger has no automatic retention purge currently configured. New public-traffic aggregates have a 90-day window; per-visit records have a seven-day window and device coordinates a 24-hour window. Traffic ingestion removes expired records opportunistically, and staff reads exclude expired personal details even before cleanup runs. Saved billing quotes and receipts preserve financial evidence. Administrators can erase public inquiries from the live inbox; audit references and separately created accounts remain. Existing provider backups or independently exported copies are not removed by that inbox action.
14. Personal-data rights and complaints
Depending on applicable law, you may request information about use of your data, access, correction, objection to processing and deletion where available. Other rights, such as restriction or portability, may apply in particular jurisdictions. Requests are assessed against identity, the organization’s responsibilities and lawful retention requirements; deletion of an account does not automatically remove a business’s financial evidence. You may raise a concern with the relevant regulator, including Kenya’s Office of the Data Protection Commissioner. No statement here limits mandatory rights.
15. Changes and appropriate data
The date and version on this notice identify the current explanation. Product or provider changes may require an update. Use DeniFlow for business receivables, not as a repository for passwords, payment-card security codes, health information or unnecessary identity documents. Avoid including unrelated personal information in notes, support cases or exports.
16. Your requests
Use Contact DeniFlow to request access, correction or deletion of your personal account or inquiry information. We need to verify identity and understand the records concerned before making a change. For records uploaded by a business, contact that business’s authorized administrator as well. Describe the request without sending passwords, authenticator codes or unnecessary financial records.
Let’s clarify it.
For a policy question or personal-data request, contact DeniFlow. For customer records held by a business, also contact that business’s administrator.
Contact DeniFlowHow support works