Skip to content

Development draft — not legally approved. Version 2.

dPakt Privacy Policy

Version 2 · effective 27 September 2026

DRAFT FOR REVIEW — NOT APPROVED FOR PUBLICATION. Operator details and the marked publication inputs must be completed and the policy checked against the live service before release.

Effective date: 1st October 2026

1. Who we are and how to contact us

dPakt is operated by dPakt Pty Ltd, trading as dPakt, [business registration details — to be confirmed]. In this policy, “we”, “us” and “our” mean that operator.

You can contact us about personal information, access, corrections or complaints:

  • Email: privacy@dpakt.io
  • Post: 3/85 Spring Street, Melbourne VIC 3000

This policy explains how we handle personal information through the dPakt website, app and related support services. It covers members, invited people, guest contact-card recipients, referred customers, people submitting enquiries and website visitors. You do not need a dPakt account to ask about information we hold about you.

2. Information we collect

The information we collect depends on your interaction with dPakt. It may include:

  • Account and sign-in information: your name, email address, verification status, profile image, identity-provider identifier and information needed to manage your sessions and account security. When you sign in through a provider, we receive the information needed for that sign-in; we do not receive your Google or Apple account password.
  • Profile and business information: information you choose to enter about yourself, your businesses, skills and services, location, business cards, images and contact methods.
  • Membership and community records: invitations, membership status and roles, accepted platform terms and community rules, meeting responses, attendance, and community activity you participate in.
  • Contact-sharing records: the sender, selected card fields, recipient details, verification and acceptance records, the relevant terms version, and records of authorized access, export, expiry and revocation.
  • Referral and agreement information: participants, opportunity details, customer information supplied for an introduction, consent records, proposals, accepted agreements, progress, outcomes, commission obligations and payment evidence entered by participants. dPakt records these activities; it does not itself process the payments described in those records.
  • Communication and feedback: messages you send through dPakt, reviews or ratings, reports, support correspondence, and information in an enquiry or interest form.
  • Technical and security information: connection and device information, session identifiers, request times, security events and diagnostic information. Some security and acceptance records use hashes of network or browser information. Hashing does not necessarily make information anonymous.
  • Notification information: notification preferences and, where you enable app push notifications, the device delivery token needed to send them.
  • Imported phone contacts: if you choose to import contacts from your phone, the name, mobile number, other phone number and email address of each contact — nothing else from your address book. We use them only to show you which of your contacts are on dPakt (by matching email addresses with verified dPakt accounts) and to let you reach them later if you choose. Only you can see your imported contacts; we do not contact them because of the import, and you can remove them all at any time.

Please do not put passwords, identification documents, health information or other sensitive information into card artwork, messages, profile descriptions or referral notes. If an interaction genuinely requires sensitive information, contact us first so that an appropriate process can be agreed.

3. Where information comes from

We collect information when you provide it, use a feature, contact us or respond to a share, invitation or referral. Our sign-in and delivery providers supply information needed to authenticate you and operate those services.

Other people may provide information about you when inviting you, proposing a permitted referral, reporting an interaction, or recording an agreement in which you are involved. People making introductions must have the authority and permissions required for the information they provide. We do not treat another member's agreement to commercial terms as the customer's permission to disclose their contact details.

We also collect limited technical information when your device communicates with the service. A notice at a collection point may explain that particular interaction in more detail.

4. Why we use information

We use information to operate your account and the features you choose, authenticate access, manage invitations and communities, deliver contact shares and referrals, preserve agreement and acceptance records, send service notifications, respond to enquiries, and handle complaints or reports.

We also use information reasonably needed to prevent misuse, investigate faults, maintain security, meet applicable legal obligations and establish or respond to legal claims. We restrict these uses to what is appropriate for the purpose.

Signing in, receiving a card or submitting an enquiry does not by itself create community membership, subscribe you to a paid plan, or give permission for unrelated marketing.

5. What other participants can see

Profiles and communities. Other participants see information made available through the features and permissions that apply to them. Joining one community does not give someone general access to all communities or all records about you. Owners and administrators can see the membership and community information needed for their role; that role alone does not entitle them to every customer's contact details or every private agreement.

Contact cards. A share has a limited preview. Protected fields such as phone, email and street address are released through the recipient acceptance process, rather than being included in that preview. Each recipient must complete their own required steps. The sender chooses the fields included in the share.

Guest recipients. We use the name and email supplied in the guest flow to verify access and record the interaction. The sender can see your supplied name, whether you accepted or declined, and the recorded time where available. Your verification email is not automatically disclosed back to the sender as a reciprocal contact exchange. A targeted sender may already know the address to which they sent the share.

Referrals and agreements. Information is available to the participants and authorized roles for that activity. Protected customer details are subject to the introduction's consent and agreement requirements. A referral is separate from a card share.

Messages and reviews. Messages are available to their conversation participants. Relevant feedback is shown within the feature's permitted audience. Ending the relationship does not itself erase the existing conversation or accepted transaction records; retention and privacy requests are addressed below.

A person who receives or exports your details can keep a separate copy. Revoking a share prevents further access through that share but cannot retrieve information already seen, photographed or saved. Recipients remain responsible for their own use of that information and any privacy obligations applying to them.

6. Service providers and other disclosures

We use providers to supply functions such as authentication, hosting, storage, email delivery, technical support and push notifications where enabled. Clerk provides the configured account authentication service. The provider list and locations for the released service are:

dPakt provides services from Australia.

Providers receive the information needed for the services they supply, subject to the applicable arrangements and law. A sign-in provider also handles information under its own privacy policy when you use its account or service.

We may disclose information to professional advisers or relevant authorities where reasonably necessary and legally permitted, including to meet a legal obligation or address a security incident or legal claim. A request from another member is not, by itself, authority to disclose your private records.

We do not treat acceptance of this policy as blanket permission to sell information or share it for unrelated purposes. Any proposed new purpose must be assessed and, where required, separately notified or consented to before it is introduced.

7. Overseas handling

Our providers or people you deliberately interact with may be outside Australia. The provider disclosure above identifies the countries in which overseas handling is likely, so far as practicable. The countries and actual provider arrangements must be confirmed before this policy is published; we do not promise Australian-only storage.

Where an overseas disclosure is subject to Australian privacy requirements, we take the steps required of us. Publishing this policy does not waive those responsibilities or amount to consent to an exception from them. A card recipient or referral participant overseas may also be subject to different laws.

8. Cookies, device storage and communications

We and our authentication providers use cookies or similar storage where needed to keep sessions working, protect sign-in, and support a guest's authorized contact-reveal session. Blocking these technologies may prevent those features from working. You can manage browser storage through your browser settings.

[cookies and tracking in the released site — to be confirmed]

Verification messages and service communications are used to carry out the interaction you requested and manage your account or activity. They are different from marketing. We do not infer permission for unrelated marketing from a card receipt, referral, terms acceptance or enquiry. Where we send marketing, we obtain any required permission and provide the required way to stop it.

App camera, photo and notification permissions support the feature you choose. You can manage those permissions in your device settings. Turning off push notifications does not remove the underlying in-app records.

9. Security and incidents

We use access controls and other technical and organizational measures intended to protect personal information against misuse, interference, loss and unauthorized access, modification or disclosure. No online service can promise that every risk is eliminated.

Keep your sign-in credentials and verification codes private. If you suspect unauthorized access or an inappropriate disclosure, contact privacy@dpakt.io. We will assess the report, take appropriate action, and notify affected people or regulators where the applicable law requires it.

10. Retention and deletion

We keep information for as long as it is reasonably needed for the purposes described in this policy, including operating an active service, preserving relevant transaction evidence, meeting legal obligations and dealing with disputes. When it is no longer needed and no applicable requirement calls for retention, we take reasonable steps to delete it or de-identify it.

Closing an account or leaving a community does not necessarily require every related record to be deleted immediately. Accepted agreements, other participants' rights and relevant legal records may require limited retention. This does not justify keeping all personal information indefinitely.

The retention approach for accounts, guest verification, shares, referral and agreement evidence, messages, security records and backups is:

[retention schedule — to be confirmed]

You can ask us to close your account or delete information by contacting privacy@dpakt.io. We will explain what we can do, any information that must be retained and why, and the effect on access. We cannot delete copies another person has independently saved. Copies in backups are handled under the confirmed backup retention process rather than represented as instantly erased.

11. Access and correction

You can edit the profile information supported by the app. For other access or correction requests, contact privacy@dpakt.io and describe the information concerned. We may need proportionate information to verify that the request comes from you or someone authorized to act for you.

We will respond within the period required by applicable law. If access or a correction cannot be provided, we will explain the reason and available complaint options, except where the law prevents us from doing so. Where appropriate, a correction can be recorded alongside a historical transaction without falsely rewriting what was originally agreed. Historical-record requirements do not remove applicable privacy rights.

12. Questions and complaints

Send your concern to privacy@dpakt.io, including enough information for us to identify the issue. We will assess it, seek any necessary information, explain our response and tell you how to escalate a matter that remains unresolved.

If your complaint is within the jurisdiction of the Office of the Australian Information Commissioner, you can contact the OAIC after giving us a reasonable opportunity to respond. The OAIC generally asks that you first complain to the organization and allow 30 days. See the OAIC privacy complaint process (opens in a new tab). Other rights or complaint avenues available under applicable law are unaffected.

13. Changes to this policy

We will publish an updated policy when our practices change and show its effective date. We will provide additional notice or seek consent where required. A policy update does not retrospectively create permission for a new use of information.

Related documents: Platform Terms and Contact Sharing Terms.