This policy describes how Ilaaliye handles personal information for DaynQor and this public website. It distinguishes current behaviour from retention targets that are not yet automated.
1. Operator and contact
DaynQor is a customer debt ledger operated by Ilaaliye. The public website is daynqor.ilaaliye.com and the customer app is app.daynqor.ilaaliye.com. Contact info@ilaaliye.com about privacy, access, correction or deletion requests. General support is available at info@ilaaliye.com.
2. Information we process
- Registration and account information: your name, email address, password hash, language, optional display timezone, email-verification status and sign-in times. Passwords are hashed with Argon2id rather than stored in readable form. Records of acceptance of a Terms version are also stored.
- Optional Google authentication: the Google account identifier and email address supplied for sign-in. DaynQor does not obtain your Google password or access to your Gmail, contacts or files.
- Business and team information: business name, contact details, address, logo, currency and timezone; membership, Owner/Staff roles, staff invitations and access status.
- Customer and financial records entered by a business: customer names, contact details and notes; debts (Owe), payments (Paid), reversals, amounts, descriptions, business dates, reasons and the person who recorded each action; imports, exports, archives and statement history.
- Support and Feedback conversations: subjects, messages, replies, feedback category, language, account and business context, sender roles, timestamps, read status and resolution status.
- Security and technical information: session-token hashes, IP addresses, browser user agents, sign-in and security events, rate-limit records, and an audit history of important account and business actions.
3. Why information is used
- To create accounts, authenticate users, manage business membership, calculate ledger balances and provide reports, statements, imports, exports and archives.
- To send account verification, password-reset, invitation and security emails, statement attachments chosen by a user, and notifications of conversation replies.
- To respond to support and feedback, protect accounts, investigate security events and maintain a record of important actions.
- To operate and recover the service, and handle privacy requests and applicable legal requirements.
DaynQor has no advertising or third-party analytics features. Personal information is not used for advertising or sold as a product.
We use information to provide the service you or your business asked for, to keep it secure, to respond to you and to meet legal obligations.
4. Business records and responsibilities
Each business chooses the customer information and debts or payments it records, who may access them and when a statement is shared. The business is responsible for accuracy, its authority to record and share information, and notices or responses it owes its customers under applicable law. Ilaaliye operates the platform, protects access and handles platform-related privacy requests, and processes customer records on the business’s behalf to provide the service.
If a business has recorded information about you, contact that business first about its ledger. You may also contact info@ilaaliye.com about Ilaaliye’s handling of information or a concern the business cannot resolve.
5. Membership, administrator and Support access
- Active business members can see customer and ledger records according to their role. The Owner manages membership, ownership transfer, full exports, archives and restore. Staff cannot administer the team or download complete exports. One business’s members cannot access another business’s records without membership there.
- Authorized platform administrators can view account and business metadata, membership roles and counts, security events and support conversations. Authorized Support personnel can read and reply to Support and Feedback conversations and see the submitting account and business context needed for that conversation.
- The administration and support interfaces do not expose business customer records, balances, transaction descriptions or statement contents. Information you voluntarily include in a support message is visible to personnel who can read that conversation; do not include passwords or unnecessary customer details.
- Hosting and email providers process information needed to operate their services. Google authentication is used only when you choose it. Disclosures may also be required by applicable law.
6. Hosting and third-party services
DaynQor runs on virtual private servers administered by Ilaaliye and provided by Contabo. Your information may be stored and processed in a country other than the one where you live.
Transactional email provider: Google Workspace. Account emails and explicitly requested statement attachments pass through that provider. A reply notification directs you to sign in to read a conversation; the reply itself remains in the app.
7. Statements, email, WhatsApp and SMS
Statements are generated or emailed when a user chooses to do so. “Accepted by mail server” confirms provider acceptance, not inbox receipt or reading. Failures and development-only email saving are distinct statuses.
WhatsApp and SMS open your own messaging app with the customer’s contact and no prefilled message. You decide what to attach and send. DaynQor records a handoff as “Prepared”; it does not confirm sending, receipt or reading in the other app. Information you send there is also handled under that service’s terms.
8. Support and Feedback conversations
Signed-in users can open separate Support and Feedback interfaces from Settings, submit a conversation, view stored replies, respond in an open conversation and reopen a resolved conversation. These conversations are account-private: ordinary members of the same business do not gain access to them. Authorized administrators and Support personnel share the service inbox.
We store the content and conversation metadata to handle the request. A read indicator means the other party opened the conversation; it is not an email-delivery confirmation. Automatic deletion six months after support resolution is a selected target, not a currently verified process. No response time or continuous staffing is guaranteed.
9. Cookies and browser storage
- The app uses essential session and CSRF cookies and a short-lived Google sign-in protection cookie. Sessions are managed on the server; only session-token hashes are stored there. Signing out or resetting a password revokes relevant sessions.
- Your device stores theme and language preferences. An invitation token may remain in the current browser tab while you use an invitation link. The installed app caches public assets and an offline notice; it does not cache financial records, statements or exports. Files you explicitly download remain your responsibility.
- This public website uses no cookies, advertising or analytics trackers. It stores theme and language choices locally in your browser and searches only its own public content. Its web server can record technical requests, including IP address, path, status and time; the supplied server configuration omits query strings.
Web server access logs for the website and the app are rotated daily and kept for 14 days. Application service logs are kept on the server for a limited, size-bounded period.
10. Security and its limits
DaynQor uses password hashing, server-side sessions, CSRF protection, rate limits, role checks and separation between businesses. Financial entries are immutable and corrections use reversals. DaynQor is served only over HTTPS, and recovery backups are designed to be encrypted. No system is completely secure: use a strong password and sign out on shared devices.
11. Account deletion and retained records
The current app includes My account → Delete Account. Permanent deletion requires an explicit confirmation and typing DELETE, plus your current password or a fresh reauthentication with your linked Google account if no password is set. On successful completion, the app clears the account’s profile contact details, password and linked sign-in methods, revokes sessions and removes conversations submitted by that account. The action cannot be undone through the app.
For every business you still own, first either transfer ownership to an eligible active member or permanently delete that business after reviewing its record counts and export options and confirming its exact name. Business deletion affects all of its staff and cannot be undone. Retention holds and remaining platform administration responsibilities can prevent deletion; contact info@ilaaliye.com if you need help.
Deleting an account does not delete an active business’s legitimate customer and financial history. Persistent actor references, audit records and some information in other people’s records may remain. A removed account name and email do not establish that every related record has become irreversibly anonymous. Records may also be kept where the law requires it.
Encrypted backups can contain earlier information until their expiry. They are not immediately rewritten or erased when an account is deleted. Backups are kept for up to 30 days (see the retention table below). Contact info@ilaaliye.com for deletion requests beyond the account controls.
12. Retention periods: policy targets and current behaviour
The following periods are Ilaaliye’s selected policy targets. A period labelled as pending does not promise automatic deletion at that deadline. Token and preview expiry limits use, while physical cleanup may happen later. Account sessions normally expire after 30 days or 14 days of inactivity; expiry of access is separate from deletion of security history.
| Information | Selected policy target | Current behaviour and limitations |
|---|---|---|
| Active accounts | While the account is active | Account information is kept while the account exists. Signing out or disabling access does not delete an account. |
| Eligible deleted-account personal data | Immediately removed or irreversibly anonymized in the live system after confirmed deletion | Confirmed account deletion clears profile contact details and sign-in credentials, revokes sessions and removes conversations submitted by the account. Persistent references and some security or business records remain; complete erasure of all related personal data has not been verified. |
| Encrypted database backups | 30 days | Policy target; expiry of all backup copies is pending implementation and operational verification. Earlier information may remain beyond the target until rotation is in place. Account deletion does not immediately erase backups. |
| Authentication and security logs | 90 days | Policy target; scheduled cleanup at this deadline is not implemented or verified. Session expiry ends access, but does not itself erase historical security records. |
| Detailed audit logs | 12 months | Policy target; scheduled cleanup is not implemented. Audit records preserve important actions and may contain an account reference and IP address. |
| Resolved support conversations | 6 months after resolution | Policy target; automatic expiry is not implemented. Conversations and replies remain stored after resolution. Feedback also remains stored without a verified automatic deletion schedule. |
| Email verification tokens | 24 hours | Expiry is enforced at the default setting; expired links cannot be used. This is not a confirmed physical-deletion deadline for token records. |
| Password reset tokens | 60 minutes | Expiry is enforced at the default setting; expired links cannot be used. Token-record deletion at this deadline is not verified. |
| Staff invitations | 7 days | Expiry is enforced at the default setting. Expiry prevents acceptance; invitation history is not automatically erased at that time. |
| Temporary imports | 30 minutes | Preview expiry is enforced. Staged contents are cleared after successful import; expired contents are cleaned during later uploads and may remain longer than this period. |
| Temporary restore previews | 15 minutes | Preview expiry is enforced. Staged contents are cleared after a successful restore; expired plans are cleaned during later uploads and may remain longer than this period. |
A business’s customer and financial records are kept while the business exists and are deleted only when its Owner permanently deletes the business. They are preserved separately from account-profile deletion. Information may be kept longer where the law requires it or to deal with an outstanding legal claim.
13. Privacy requests and applicable rights
You can update account preferences, change your password, manage linked sign-in methods, leave a business as Staff and request permanent account deletion subject to the safeguards above. Owners can transfer ownership and download bounded exports and archives. For privacy requests, write to info@ilaaliye.com with enough information to identify your request; do not send your password. We may need to verify identity without collecting unnecessary information.
Depending on the law that applies to you, you may have rights to access, correction, deletion, restriction, objection, portability, withdrawal of consent where relevant, or a complaint to a competent authority. These rights and their exceptions depend on that law and your circumstances. We respond to requests as soon as reasonably possible.
14. Eligibility and children
DaynQor is intended for businesses and their authorized staff, not for children. Users must be at least 18 years old.
15. Changes and contact
The version and dates above identify this policy; the DaynQor app shows the same version. We announce material changes in the app at least 14 days before they take effect, and continued use of business features requires accepting the new version. Questions: info@ilaaliye.com.