COORDUS PRIVATE LIMITED operates CO-ORD US, a platform for personal and business coordination. This policy explains how we handle personal data through our website and application. It supplements the privacy notices and permission prompts shown when you use particular features.
1. Who to Contact
For privacy questions, access or correction requests, consent withdrawal, deletion requests or complaints, contact support@co-ordus.com. Please identify the account and the request. Do not email your password, complete payment card details or unnecessary identity documents. We may need proportionate information to verify your identity before disclosing or changing personal data.
2. Information We Handle
Account information includes your name, email address, mobile number, account identifier and profile details. If you choose Google sign-in, Google supplies the account identity and available name, email address and profile photograph. Firebase Authentication manages sign-in credentials.
Activity information includes connections, group membership and messages, invitations, appointments, service requests, events, attendance, quotations, follow-ups and information you choose to upload. Professional and organisation features may include credentials, verification submissions, organisation details, membership, roles, team assignments, contracts and related records.
Where enabled, we handle notification preferences and device notification tokens. Website and application delivery may involve technical information such as IP addresses, browser or device information and service logs. The browser or device may store sign-in state and preferences such as language and appearance. Optional device information is handled as described below.
If you verify with Singpass Myinfo or Myinfo Business, we receive only the data items you consent to on the Singpass or Corppass screen, such as your name and employment details or, for an organisation, its registration details and your appointment. The retrieved result is kept on our servers for verification and review. It is not copied to your profile, except that your verified name may become your profile name.
When you set up a business, we estimate the country of your internet connection from its IP address to apply features available only in Singapore. The estimate is made on our servers using a country database and does not use your device location. We do not store your IP address or the estimated country.
If you verify with a photo ID instead of Singpass, we read your card once to confirm its type and that the name matches your profile, and we compare a live video selfie with the card photo using Amazon Web Services. The video is processed in Japan and the comparison in Singapore. The card photos, the selfie and the video are deleted as soon as the result is known. We keep only the result, the card type and the card details you use for your profile (company, role and licence number). We never keep your NRIC or FIN number, date of birth or address. Documents you upload for verification are read once and not kept.
An organisation may upload, with consent, its ACRA BizFile business profile or screenshots of it for verification. We read the company status, the document date and the officers’ names and positions. NRIC and FIN numbers in screenshots are covered before anything is stored, and an upload is refused if a number cannot be covered. If an upload verifies the organisation, its files are deleted and only the outcome is kept. Otherwise the files are kept privately with the organisation for up to 7 years for verification reviews and can be opened only by COORDUS reviewers. Each upload and each viewing is recorded.
3. Why We Use Information
We use information to provide and maintain accounts; coordinate the plans, services and communications you request; manage organisation workspaces; assess professional eligibility and verification; deliver requested notices; and provide support. We also use information where needed to protect accounts and private records, investigate misuse, resolve disputes and meet applicable legal obligations.
The relevant feature and notice explain the intended activity. A privacy acknowledgement is not permission for every optional feature, device permission or marketing activity. Where consent is required, we seek it for the relevant purpose. We may also handle information where applicable law permits or requires it.
4. Connections, Invitations and Groups
An exact-email search for a registered user can reveal whether that email is registered and the saved name. Ordinary personal connections require mutual acceptance. Connection sharing can include your name, email and permitted phone number. Your phone visibility settings and the relevant sharing prompts apply. Being connected does not give another person access to all your private plans.
Close Groups have a distinct joining consent: agreeing to join makes you a personal connection with every current and future member, sharing your name, email and permitted phone number with them. Leaving a Close Group does not remove those connections; you can remove them through Connections.
Other group membership allows members to see your name and messages without automatically granting access to private plans or other members’ connections. Event and organisation access also depends on the person’s role and the relevant record permissions. Review a group’s joining notice before joining or sharing its invitation link.
Invitations and contact sharing use the relevant confirmation steps. Provide another person’s details only with their permission or another valid basis, and share only what the activity requires. An invitation or public link is not blanket permission to disclose someone’s private information.
5. Plans, Organisations and Public Profiles
Plan information is shared according to the activity, participation and permissions. Private appointment addresses and notes are restricted to the creator, assigned provider and authorised members of the assigned organisation team. Explicitly invited people may see the relevant title, time and location without access to private follow-up conversations.
Matching requests may show service categories, times and a masked location. A street or venue may remain visible; postal codes may be reduced to the first three digits and unit details hidden. Do not put confidential details in a public request, listing or profile.
Organisation members see records according to their authorised role and the acting workspace. Contract and quotation records are shared with authorised parties. Private commercial allocations are not a public directory record; access is limited to the relevant parties and their permissions.
Public profiles, service listings and information you deliberately make public can be visible to other people. Directory and phone visibility settings affect the relevant profile; they do not retract copies already received by another person.
An organisation may send you forms through a booking. When a form is marked as containing personal details, COORDUS’s copy in the booking is deleted 24 hours after you first open it, or 72 hours after it is sent if it is never opened. The signed copy is kept in the organisation’s records, where you can still open it. Each opening of such a form is marked with the viewer’s name and the time. Copies that a person has downloaded or shared outside COORDUS are not affected.
6. Device Permissions, Location and External Services
Location, camera, calendar and notification access depend on the feature you choose and the permissions you grant. You can change device permissions through your browser or device settings. Some features may not work without the relevant permission.
When a provider taps I’m on my way for a job, their position is shared with that customer and their organisation until they check in, for at most 90 minutes. It is sent only while COORDUS is open or showing its location notification; COORDUS never asks for background location. While it is shared, the phone’s motion sensor checks for a possible accident; if one is detected and the provider does not answer within 30 seconds, their organisation’s Admins and work team are alerted with the last position, and the customer is told only that the provider is delayed. Sensor readings are not stored. The arrival estimate is calculated from the distance, without a routing service.
The route of each trip is kept for 7 days, then deleted. If a possible accident, a dispute or a complaint about the visit is recorded within those 7 days, that trip is kept for 3 years as evidence; only the provider and their organisation’s Admins can open it, and the customer cannot. Check-in uses the provider’s location once to confirm that they are at the address and does not store it. A location search or external map action may send the selected location or search to the map provider. External services have their own terms and privacy practices.
Live in-app payment collection is not yet active. We will provide relevant information and obtain any required permissions before introducing new processing through it.
7. Service Providers and Overseas Processing
We use Firebase services for functions such as authentication, cloud records, hosting and notifications. Supporting technology providers process information needed to operate those services. Their infrastructure may process information outside Singapore. Applicable data protection requirements apply to overseas transfers.
We also use: Singpass Myinfo and Myinfo Business (with Corppass) for identity and organisation verification; Google Cloud Vision to read uploaded verification documents and to check listing images for prohibited content; Amazon Web Services for the photo ID face check; OneMap to find the map point of a postal code; Resend to send emails; and Stripe to process card and PayNow payments made through COORDUS checkout. COORDUS does not receive or store full card numbers.
We may disclose information when reasonably required for authorised support, safety or security investigations, dispute handling, or legal obligations. We do not make private records public merely because a person is an administrator. Routine administrative access is limited, although privileged project owners and backend service accounts can technically access stored information.
An independent provider or organisation may be separately responsible for information it receives to deliver services or manage its own relationship with you. Contact that party for its own privacy practices and records.
8. Security and Retention
We use authentication, role permissions and access controls to protect information and restrict private records to authorised users and systems. No online service can guarantee absolute security. Keep your credentials private and contact us promptly if you suspect unauthorised access.
We keep an audit log of security and permission actions, such as verification decisions, changes to organisation roles and memberships, account links, BizFile uploads and viewings, and the keeping or deletion of trip records. Each entry records the accounts involved, the action and the time, and may include a name or email address where needed to show what changed. It does not record message text, document contents or positions. The audit log is written only by our servers, cannot be changed from the app and can be read only by authorised COORDUS staff (Moderators).
We retain information for as long as necessary for its purpose and relevant business or legal requirements, including recordkeeping, disputes and security. Specific periods apply where stated in this policy: trip routes for 7 days, or 3 years when kept as evidence; forms containing personal details in a booking for 24 hours after first opening, or 72 hours if unopened; and BizFile documents for up to 7 years unless deleted earlier on verification. The audit log has no fixed retention period and is kept for as long as needed for security, dispute and legal purposes. Otherwise, retention depends on the type of record and the circumstances; this policy does not promise immediate deletion of all records or backups.
Deactivating an account is not the same as deleting its data. Contract, transaction-related, consent and shared coordination records may need to be retained after an account or membership ends. A deletion request does not automatically delete copies lawfully held by other parties.
9. Your Choices and Requests
You can edit available profile details, manage visibility, review connections and change device permissions. Contact support@co-ordus.com to request access or correction, withdraw consent, request deletion, or raise a privacy concern. We will consider the request under applicable law and explain relevant limitations or information we reasonably need.
Withdrawing consent may affect the services we can provide. We will explain the likely consequences and any applicable retention requirements. Withdrawing a device permission does not by itself delete information already lawfully collected.
10. Policy Updates
This policy was last updated on 11 November 2026. We may update it as the service changes. Material changes will be communicated where required, and a new purpose requiring consent will not be authorised solely by publishing an amended policy. Existing feature-specific permission and consent controls continue to apply.