LEGAL
Privacy Policy
Effective: October 31, 2026
1. Who We Are and Scope
Zuko is a trading name of Ibis General Services Limited, located at 25A Spring Bank Avenue, Cascade 160403, Trinidad and Tobago. References to “Zuko,” “we,” “us,” or “our” mean Ibis General Services Limited. This Privacy Policy explains how Zuko collects, uses, shares, stores, protects, and retains information when you use the Zuko mobile application, public website, account portal, secure sharing pages, support services, campaigns, or related services. This version is effective October 31, 2026 and is identified as version 2026-10-31.1. It is subject to applicable privacy and data-protection laws, including the applicable provisions of the Data Protection Act, Chap. 22:04 of the Laws of Trinidad and Tobago.
2. People Covered by This Policy
This policy applies to registered Zuko users, people invited to join a Zuko workspace, external recipients who receive items through Zuko One, campaign participants, website visitors, support contacts, and other people whose information is processed through the service. A “user” is a person with a registered Zuko account. An “external recipient” is a person who receives selected information through Zuko One without necessarily creating a Zuko account. An “organizer” is the user who creates or manages a workspace or initiates sharing with another person.
3. Information We Collect
Zuko collects information needed to provide and protect the service. This may include your name, email address, telephone number, preferred language, timezone, profile information, authentication information, communication preferences, physical addresses you choose to enter, co-parent connection information, workspace roles, subscription status, transaction references, and support communications. Zuko also processes information that users create, enter, upload, receive, or manage through the service. This may include messages, notices, requests, responses, decisions, calendar events, parenting-time information, pickup or handover outcomes, expenses, contribution requests, accountability records, documents, photographs, child profiles, reports, audit history, notification settings, and related records.
4. Child-Related and Sensitive Information
Co-parenting records can contain sensitive personal information. Information entered into Zuko may include children’s names, dates of birth, schools, schedules, addresses, photographs, medical or health-related information, financial information, family circumstances, parenting arrangements, supporting evidence, and records connected to legal or safety matters. Child medical information and other protected records may be subject to additional authentication, visibility, or access controls. Users should only enter information they are authorised to provide and should avoid adding information that is unnecessary for the intended co-parenting purpose.
5. Technical, Device, and Security Information
Zuko may automatically process technical information needed to operate and secure the service. This may include IP address, device and operating-system information, browser type, app version and build, language, timezone, approximate region derived from network information, session identifiers, request identifiers, login activity, notification tokens, security events, diagnostic reports, synchronization status, error information, and timestamps. This information is used for authentication, fraud and abuse prevention, troubleshooting, service reliability, compatibility checks, security monitoring, and support.
6. Mobile App Permissions
Depending on the features you use, Zuko may request device permissions for notifications, camera access, photographs, files, storage, biometric authentication, or similar capabilities. Permissions are used only for the feature for which they are requested and can generally be managed through your device settings. Denying a permission may prevent the related feature from working but should not prevent unrelated parts of Zuko from being used.
7. How We Use Information
Zuko uses information to create and authenticate accounts, establish and manage workspaces, connect authorised co-parents, synchronize records across devices, deliver selected information to external recipients, maintain communication and request workflows, manage schedules and parenting-time records, process expenses and contribution requests, generate user-requested reports, deliver notifications, verify subscriptions, provide support, prevent misuse, investigate safety concerns, maintain audit records, and improve service reliability. Zuko may also use information to comply with legal obligations, enforce its Terms of Use, protect users and the service, resolve disputes, detect fraud, maintain backups, and respond to lawful requests.
8. Reasons for Processing Information
Depending on the feature and applicable law, Zuko processes information because it is necessary to provide the service requested by a user, because a person has given consent, because processing is necessary for legitimate operational or security interests, or because processing is required to comply with legal obligations or protect rights and safety. Where processing depends on optional consent, such as optional marketing communications or website analytics, that consent may be withdrawn through the available settings or controls. Withdrawal does not affect processing that occurred before consent was withdrawn or processing required for another lawful purpose.
9. Shared Workspaces and Information Visibility
A shared Zuko workspace allows authorised participants to access information according to the record type, connection status, role, and visibility rules applied by the service. Shared requests, responses, discussions, calendar events, contribution requests, shared documents, and other collaborative records may be visible to both authorised parents. Not every record is automatically shared. Private accountability notes remain scoped to their creator and are not automatically disclosed to the co-parent. Personal expense records remain private until the user deliberately creates and shares a contribution request. Personal pickup or handover notes and supporting evidence remain private, while the applicable event outcome or reconciliation status may be shared. Documents are governed by their assigned visibility and protection level. Users should review the sharing status of an item before submitting or attaching sensitive information.
10. Zuko One
Zuko One allows a registered user to organise a workspace without requiring the other parent to create a Zuko account. The user may enter an external recipient’s name and email address and deliberately share selected requests, notices, calendar events, and eligible documents through secure email links. An external recipient receives access only to the individual item selected for sharing. The recipient does not receive access to the organizer’s complete workspace, private accountability notes, private expenses, unrelated documents, or other records that were not deliberately shared. Where supported, the recipient may submit a response, acknowledge an item, or take another action through the secure page. The action, response content, status, and timestamp are stored with the relevant item and made available to the organizer.
11. Zuko One Recipient Information
To operate Zuko One, Zuko may process the recipient’s name, email address, relationship or connection reference, preferred language where known, delivery status, bounce or complaint status, secure-link status, link-access activity, acknowledgements, responses, opt-out status, and account-connection requests. An external recipient’s email address is used to deliver and manage the items selected by the organizer. Receiving a Zuko One item does not create a Zuko account, enrol the recipient in marketing, or grant workspace membership. If the recipient later signs in or creates a verified Zuko account and asks to connect it to the relationship, Zuko processes the account reference and connection-request status. The organizer must confirm the request before workspace access changes.
12. Secure Email Links
Zuko One links are bearer links intended for the recipient named in the email. A person who obtains a valid link may be able to access the item until the link expires or is revoked. Recipients should not forward secure links and should protect access to their email account and device. Links may expire, be regenerated, or be revoked. Replacing a recipient, stopping external sharing, recording a hard bounce or spam complaint, or converting the relationship to a shared Zuko connection may invalidate existing links and cancel pending deliveries. Zuko records information necessary to operate and protect these links, which may include creation, expiry, delivery, first access, acknowledgement, response, regeneration, and revocation timestamps.
13. Recipient Controls and Opt-Outs
An external recipient can use the available secure sharing controls to stop future Zuko One emails to their address. When this occurs, Zuko disables external delivery for that relationship, revokes active Zuko One links, cancels eligible pending deliveries, and records the opt-out so that the preference can be respected. A recipient may contact Zuko if the email address is incorrect, the sharing appears unauthorised, or the recipient needs assistance exercising an available privacy choice. Limited suppression or audit information may be retained after an opt-out to prevent further delivery, investigate misuse, and demonstrate that the request was honoured.
14. Expenses and Contribution Requests
A user may record child-related expenses privately. A personal expense is not automatically shared with a co-parent. If the user creates a contribution request, Zuko shares the information deliberately included in that request, which may include the amount, currency, description, child reference, due date, supporting document, and relationship to the private expense. The private expense record and the shared contribution request remain separate records with different visibility.
15. Documents, Attachments, and Reports
Documents and attachments may be marked private, shared with workspace participants, protected by additional controls, or attached to an item deliberately shared through Zuko One. Zuko applies the visibility rules associated with the document and the item to which it is linked. Generated reports may contain records selected by or available to the requesting user. Zuko stores report status, generation history, access information, and delivery information needed to create and provide the report. Users are responsible for deciding where and with whom downloaded or exported reports are shared after leaving Zuko.
16. AI-Assisted Message Review
If AI-assisted message review is enabled, the text of an outgoing message draft may be sent through Zuko’s authenticated API to OpenRouter and a selected AI model provider to produce tone guidance or a suggested rewrite. Zuko requires zero-data-retention routing for these requests and does not send message drafts to Firebase Analytics. Zuko records limited operational information about the review, such as the account and workspace involved, provider and model, character counts, risk level, success or failure, and related audit information. The draft text is not stored in Zuko’s AI usage log. AI guidance is optional, may be incomplete or inaccurate, does not make legal or parenting decisions, and never sends a message without the user’s action. Automatic tone checks can be managed through available app settings.
17. App Analytics
The mobile app uses Google Firebase Analytics to understand general app usage, screen activity, feature engagement, performance, and reliability. Firebase Analytics may process a pseudonymous app-installation identifier, app and device information, app opens, screen views, feature events, session activity, and an approximate geographic area derived from network information. Zuko clears account-level analytics association and does not intentionally send names, email addresses, telephone numbers, authenticated Zuko user IDs, message text, document contents, child information, workspace identifiers, record identifiers, secure-link tokens, or authentication credentials to Firebase Analytics. Analytics information is used for service improvement and is not used by Zuko for cross-company behavioural advertising.
18. Website Cookies and Analytics
Zuko uses essential cookies and similar technologies for website and portal authentication, account security, session management, routing, language preferences, fraud prevention, and other functions necessary to provide the service. With the visitor’s consent, the public website may use Google Analytics to understand general website activity such as pages visited, traffic sources, browser or device type, approximate location, and performance trends. Optional analytics can be accepted or declined through the website cookie controls. Blocking essential cookies may prevent authenticated website features from working. Zuko does not use advertising cookies or third-party behavioural advertising cookies on its website.
19. Push Notifications
If push notifications are enabled, Zuko uses Firebase Cloud Messaging and, on Apple devices, Apple Push Notification service to deliver them. Zuko stores a registration token identifying the app installation, the device platform, notification preferences, delivery-related information, and the associated Zuko account so notifications can be routed correctly. Notification tokens are security-sensitive and are not used for advertising. The visibility of notification previews may be controlled through device settings.
20. Email and Service Communications
Zuko may send verification messages, password-reset messages, security alerts, billing notices, account-closure messages, co-parent invitations, Zuko One deliveries, report notifications, campaign communications, and other service messages necessary to operate the platform. For eligible operational emails, Zuko and Postmark may record submission, delivery, bounce, suppression, and spam-complaint events. Sensitive operational emails are not configured for provider open or link-click tracking. Zuko One records access to its own secure pages when necessary to show whether a shared item has been accessed, acknowledged, or answered. Optional product news, resources, and offers are sent only where the user has opted in. Optional marketing preferences do not affect service, security, billing, account, or user-requested sharing communications.
21. Payments and Subscriptions
Subscriptions and payments may be processed through Apple App Store, Google Play, or an available web-payment provider. The payment provider processes the payment credentials according to its own privacy policy. Zuko may receive and store transaction identifiers, purchase tokens, provider, product or plan, amount and currency where applicable, payment or subscription status, promotion information, purchase and expiry dates, refund status, and related verification information. Zuko does not receive or store complete app-store payment-card credentials.
22. Service Providers
Zuko uses service providers for hosting, databases, file and document storage, content delivery, security, email delivery, analytics, push notifications, AI-assisted processing, payment processing, subscription verification, holiday or calendar information, and operational support. These providers process information only as needed to supply their services to Zuko and are subject to their own contractual, privacy, and security obligations. Providers may include Postmark for email delivery, Google Firebase for analytics and notifications, OpenRouter and selected AI model providers for optional AI-assisted review, Apple and Google for mobile subscriptions and notifications, and the payment providers displayed during web checkout.
23. When Information Is Shared
Zuko does not sell personal information, communication records, schedules, documents, expenses, child information, or user-generated content. Information may be shared with an authorised co-parent according to workspace visibility rules, with an external recipient when a user deliberately shares an item through Zuko One, with service providers needed to operate the platform, with campaign partners as described in a campaign-specific notice, or where disclosure is required by law or reasonably necessary to protect users, legal rights, or platform integrity. If Zuko undergoes a merger, acquisition, restructuring, financing, or transfer of business assets, information may be transferred as part of that transaction subject to appropriate confidentiality and legal safeguards.
24. Safety Reports, Blocking, and Abuse Prevention
Users may report received messages, suspected misuse, harassment, threats, unauthorised sharing, or other safety concerns. Zuko may process the report category, submitted details, relevant message or item content, account and connection references, timestamps, technical information, review notes, findings, decisions, and enforcement actions. Authorised safety personnel may access information reasonably necessary to assess a report while limiting unrelated disclosure. Safety information is used to investigate concerns, prevent misuse, enforce the Terms of Use, protect users, and maintain platform integrity. Zuko may also process IP addresses, account activity, delivery failures, spam complaints, rate-limit events, authentication attempts, audit history, and other security signals to detect fraud, prevent abuse, and protect accounts and secure links.
25. Legal Requests and Compliance
Zuko may preserve or disclose information when required by applicable law, court order, subpoena, regulatory requirement, or other lawful process. Zuko may also preserve or disclose information where reasonably necessary to establish, exercise, or defend legal rights; investigate fraud or misuse; protect the safety of a person; respond to an emergency; enforce agreements; or protect the operation and security of the service.
26. Storage and Security
Zuko uses authentication controls, role and relationship checks, encrypted communications, access restrictions, audit records, monitoring, secure infrastructure, expiring or revocable links, and other safeguards intended to reduce unauthorised access, alteration, disclosure, or loss. Some sensitive features may require biometric authentication, a device credential, or another privacy control. No technical or organisational measure can guarantee absolute security. Users remain responsible for protecting account credentials, devices, email accounts, authenticated sessions, and secure links.
27. International Processing
Zuko and its service providers may store or process information outside the country where a user or recipient lives. This may include processing in countries where hosting, email, analytics, notification, AI, payment, or support providers operate. Where required, Zuko uses contractual, organisational, and technical safeguards appropriate to international processing. By using the service, information may be processed in Trinidad and Tobago and in other countries necessary to provide the selected features, subject to applicable law.
28. Data Retention
Zuko retains information for as long as reasonably necessary to provide the service and maintain synchronization, workspace continuity, auditability, document and report access, subscription records, security, fraud prevention, backups, support, dispute resolution, and legal compliance. Retention depends on the type of information and its purpose. Shared workspace records may remain where needed to preserve an accurate history for authorised participants. Private records remain subject to their applicable visibility rules. Secure-sharing records may remain until expiry or revocation and for a limited period afterward for security, audit, support, and dispute purposes. Zuko One delivery payloads are retained only for the applicable delivery or limited recovery period and are then removed or scrubbed according to the configured retention policy. Limited terminal delivery metadata may be retained for a longer configured period. Opt-out, suppression, bounce, complaint, security, and audit information may be retained where necessary to honour preferences and prevent repeated or abusive delivery. Backups may retain information for a limited additional period before being overwritten. Information subject to a legal hold, safety investigation, fraud investigation, dispute, or legal obligation may be retained for longer.
29. Account Closure
A registered user may request account closure through the available platform procedure. A 10-day review window begins when the request is submitted, during which the user may sign in and cancel the request. After the review window, Zuko revokes account access and anonymises or deletes eligible profile and authentication information. Closing a Zuko account does not automatically cancel a subscription purchased through an app store or another payment provider; the subscription may also need to be cancelled through that provider. Shared workspace records, responses, documents, requests, calendar events, expenses, billing records, legal acceptances, safety records, audit history, and information required for security, legal compliance, dispute resolution, or the rights of another authorised participant may be retained. Information that cannot be deleted immediately may be restricted, anonymised, or retained only for the applicable purpose.
30. Your Rights and Choices
Subject to applicable law, registered users and external recipients may request information about how their personal information is handled, ask for access to or correction of eligible personal information, object to or restrict certain processing, withdraw optional consent, manage communication preferences, or request deletion where applicable. Users may manage notification permissions, optional marketing preferences, account information, connections, sharing settings, and account closure through available app or portal controls. External recipients may stop future Zuko One sharing through the secure recipient controls or contact Zuko for assistance. Certain shared, legal, security, billing, safety, suppression, or audit records may not be immediately deletable where retention is necessary for another person’s rights, platform integrity, or a legal obligation. Zuko may need to verify the identity or authority of a person making a privacy request before acting on it.
31. Children’s Privacy
Zuko is intended for use by adults and is not directed to children. Children should not create accounts or submit information directly to Zuko. Child-related information must be entered by an adult who is authorised to provide and use it for legitimate co-parenting, scheduling, care, documentation, or record-management purposes. If Zuko learns that a child created an account or directly submitted personal information without appropriate authority, Zuko may take steps to restrict or remove that information.
32. Partner Campaigns and Trial Programmes
Zuko may operate partner campaigns, sponsored-access programmes, and trials. These programmes may process eligibility information, participant names and email addresses, phone platform, invitation activity, account links, enrolment status, co-parent participation, benefit status, feedback, testimonials, optional name attribution, and campaign email delivery or engagement information. A campaign-specific privacy notice explains the additional information, sponsor involvement, eligibility rules, disclosures, retention period, and choices applicable to that programme. The campaign notice supplements this Privacy Policy. Submitting testimonial text gives Zuko permission to use the testimonial as explained at submission. Whether the participant’s name may accompany the testimonial is handled as a separate choice. Campaign information is not used to expose private workspace content, messages, records, or feedback to a sponsor unless the applicable notice and consent expressly permit it.
33. Changes to This Policy
Zuko may update this Privacy Policy to reflect changes in features, processing, service providers, security practices, legal requirements, or business operations. When a revised version is published, Zuko updates its version and effective date. Where a change is material or acknowledgement is required, registered users may be shown a plain-language summary and asked to review or acknowledge the updated policy. Published legal versions and acknowledgements are retained for audit and compliance purposes.
34. Contact
Questions, privacy requests, correction requests, deletion requests, or concerns about this Privacy Policy may be sent to [email protected]. Safety concerns, reports of harassment or threats, and concerns about abusive or unauthorised use of Zuko may be sent to [email protected]. Billing questions may be sent to [email protected]. Postal correspondence may be addressed to: Ibis General Services Limited Trading as Zuko 25A Spring Bank Avenue Cascade 160403 Trinidad and Tobago
