Planndora Privacy Policy

This Privacy Policy explains how Apptriangle Pty Ltd (ABN 78 651 767 949, ACN 651 767 949) of 10 Mount Street, North Sydney, 2060, NSW, Australia ("Apptriangle", "Planndora", "we", "us", or "our") collects, uses, discloses, and protects personal information in connection with Planndora, our multi-tenant project and product management platform (the "Service"), our website, and related support and billing functions.

This Policy applies wherever you access the Service from, including from Australia, the European Economic Area ("EEA"), the United Kingdom ("UK"), the United States, and the Asia-Pacific region. Section 15 sets out disclosures required specifically for those regions; where a region-specific disclosure is more protective than the general terms of this Policy, the region-specific disclosure applies to individuals in that region.

This Policy is incorporated into, and forms part of, our Terms of Service. By creating an account or using the Service, you agree to this Policy as part of that binding agreement. If you use Planndora on behalf of an organization, that organization (your "workspace" or "tenant") controls your account and the content within it, subject to Section 2 below.

Apptriangle Pty Ltd is the company that operates Planndora and is the entity legally responsible for the matters in this Policy.

For account, billing, and platform-security data — your name, login credentials, organization membership, subscription and payment metadata, and security/audit logs — Apptriangle is the data controller (or, under the Australian Privacy Act, the APP entity responsible for that information).

For workspace content — the projects, issues, sprints, comments, attachments, documents, and similar material your organization and its members create or upload — your organization (the customer that administers your workspace) is generally the data controller, and Apptriangle acts as its data processor / service provider, processing that content only as instructed by the organization and as needed to operate the Service. If you have questions about workspace content specifically, your organization's administrator is usually the right first point of contact; Apptriangle remains available for privacy and security requests at the contact in Section 21.

Business customers can request a Data Processing Addendum ("DPA") from Apptriangle that formalizes this processor relationship, including sub-processor terms, international transfer mechanisms, and audit rights — see Section 19.

Planndora's AI features are built on the Model Context Protocol (MCP). How that server is deployed determines who processes the underlying data, and this is a deliberate design choice intended to keep customer content inside environments the customer controls wherever possible:

• Customer-hosted MCP (default): Where your organization has its own infrastructure, the MCP server is deployed on that infrastructure, under your organization's control. In this configuration, Apptriangle does not access, store, transmit, or process the workspace content handled by that MCP instance, and we do not use it to train or fine-tune any AI or machine-learning model, whether ours or a third party's. Apptriangle's role is limited to the core Planndora application and the connection metadata described in Section 3.
• Jointly agreed hosting (fallback): Where an organization does not have suitable infrastructure of its own, we will discuss deployment options with that organization during onboarding, and the MCP server will be deployed only in an environment the customer has reviewed and approved — which may be infrastructure operated by Apptriangle or by a mutually agreed third-party provider. In that configuration, Apptriangle (or the agreed provider) acts as a data processor for the data handled by that MCP instance, subject to the same purpose-limitation and no-training commitment above, and subject to the customer's Data Processing Addendum.
• Because the location and operator of the MCP server are set per customer, the countries in which MCP-processed data is handled will vary and are agreed with each customer individually rather than fixed by this Policy. If you have questions about where your organization's MCP deployment is hosted, ask your workspace administrator or contact us at the address in Section 21.

• Provide, operate, maintain, and improve Planndora's features (projects, issues, watchers, documents, notifications, and API/MCP access where enabled).
• Authenticate users, enforce roles and permissions, and manage organization membership.
• Process subscriptions, per-seat charges, prorations, renewals, receipts, and failed-payment retries via Stripe (and PayPal where offered).
• Send transactional email such as invites, verification, password reset, billing receipts, and important service notices.
• Detect, prevent, and investigate fraud, abuse, unauthorized access, and security incidents — including IP blocking when warranted.
• Respond to support requests and communicate product updates you opt into.
• Comply with legal obligations and enforce our Terms of Service.

Where a legal basis is required (including under the GDPR/UK GDPR), we map each purpose to a specific basis rather than relying on a general list: (a) performance of a contract (providing the Service); (b) legitimate interests (security, fraud prevention, platform reliability, business continuity); (c) consent (where we ask for it); (d) legal obligation (compliance with law); (e) vital interests (preventing serious harm).

• We do not sell personal information.
• Payment processors: Stripe (primary) and PayPal process payments, proration, invoices, and receipts under their own privacy policies.
• Infrastructure and service providers that help us host, store files, send email, monitor uptime, or analyze reliability — bound by contractual confidentiality and security obligations. A current list of sub-processors is available at [SUB-PROCESSOR LIST URL] and we will provide advance notice before adding a sub-processor that will handle personal information.
• Organization administrators and authorized members may access workspace content and member activity according to role permissions.
• Platform administrators may access security logs, mail-usage logs, and IP blocklist controls needed to operate and secure the platform, on a least-privilege, need-to-know basis, and that access is itself logged.
• We may disclose information when required by law, legal process, or to protect the rights, safety, and integrity of users and the Service.
• In connection with a merger, acquisition, or asset transfer, information may transfer subject to appropriate confidentiality protections and, where required, notice to affected individuals.

Apptriangle is based in Australia, and our core infrastructure and payment processors may operate in other countries, including Australia / Singapore / United States / Ireland and the United States (for Stripe/PayPal). Where we transfer personal information out of a jurisdiction that regulates such transfers, we use one or more of the following safeguards depending on the origin of the data:

• EEA/UK-origin data: Standard Contractual Clauses (SCCs) adopted by the European Commission, and, for UK-origin data, the UK's International Data Transfer Addendum, or reliance on an applicable adequacy decision.
• Australia-origin data: compliance with Australian Privacy Principle 8, including satisfying ourselves that the overseas recipient is subject to a comparable privacy law or contractual safeguards, or obtaining consent where required.
• Data subject to Asia-Pacific frameworks (for example Singapore's PDPA or Japan's APPI): contractual and, where the destination is not a recognized adequate jurisdiction, comparable safeguards, together with the disclosures in Section 15.4.

We use cookies and local/session storage for three purposes: (a) strictly necessary cookies to keep you signed in and support core functionality; (b) analytics cookies to understand product usage and reliability; and (c) marketing cookies, where used, to measure the effectiveness of our own communications.

• For visitors in the EEA and UK, we request opt-in consent through a cookie banner before setting non-essential (analytics or marketing) cookies, consistent with the ePrivacy Directive/PECR. For visitors elsewhere, you can control cookies through your browser settings and, where offered, an in-product preference center; disabling certain cookies may limit signed-in features. See our Cookie Policy for the current list of cookies and providers.

Planndora uses a per-seat, prorated billing model powered primarily by Stripe. When seats are added mid-cycle, Stripe calculates prorated amounts; renewals charge for all active seats. Payment receipts and invoices are generated through the payment provider and may be emailed to the customer.

• Card and wallet details are entered on Stripe (or PayPal) hosted checkout / customer portal surfaces whenever possible.
• We store subscription and payment metadata needed for entitlements (plan, seats, status, period end, provider references).
• Failed payments may trigger provider retry logic and temporary restriction of paid features until resolved.

We use cookies and local/session storage for three purposes: (a) strictly necessary cookies to keep you signed in and support core functionality; (b) analytics cookies to understand product usage and reliability; and (c) marketing cookies, where used, to measure the effectiveness of our own communications.

• For visitors in the EEA and UK, we request opt-in consent through a cookie banner before setting non-essential (analytics or marketing) cookies, consistent with the ePrivacy Directive/PECR. For visitors elsewhere, you can control cookies through your browser settings and, where offered, an in-product preference center; disabling certain cookies may limit signed-in features. A separate Cookie Policy with the current list of cookies and providers is available at www.planndora.com/cookie_policy.

• Account and workspace data are retained while your organization remains active or as needed to provide the Service.
• Security logs, email-usage logs, and IP blocklist records are retained for security, audit, and abuse-prevention purposes for a period appropriate to those purposes, then deleted or aggregated where feasible.
• Billing and payment records may be retained as required for accounting, tax, dispute resolution, and legal compliance.
• After account deletion or organization offboarding, we delete or anonymize personal data within a reasonable period, except where longer retention is required by law or legitimate business records.

• HTTPS/TLS for data in transit; passwords stored as salted cryptographic hashes; role-based access control (platform administrator, organization administrator, member) and project-level membership.
• Issue-edit permissions are scoped so members can view project issues but edit only when assigned or when they hold an administrator role, limiting unnecessary write access.
• Security audit logging of sensitive actions, and an optional IP blocklist enforced on API requests.

Subject to the exceptions and processes of the law that applies to you, you may have rights to access, correct, export, restrict, or delete your personal information, or to object to certain processing. Region-specific rights are set out in Section 15; the baseline process is:

• Update most profile information directly in-app. For workspace content controlled by your organization, ask your workspace administrator, who can action most requests directly.
• Send a request to support@planndora.com. We will take reasonable steps to verify your identity before acting on a request that goes beyond your own account settings.
• We aim to acknowledge requests within 5 business days and to resolve them within 30 days, or to explain any extension needed for complex requests.
• You may request logout-related audit recording through the product logout flow; discard tokens client-side after sign-out.
• Marketing communications can be opted out of at any time; transactional and security messages remain necessary for the Service.

We do not currently make decisions that produce legal or similarly significant effects about you based solely on automated processing without human involvement. If that changes — for example, if a feature were to automatically restrict account access based solely on an automated risk score — we will update this Policy and provide the disclosures required by applicable law, including Australia's automated-decision-making transparency requirement taking effect 10 December 2026 and Article 22 of the GDPR/UK GDPR where applicable.

These disclosures supplement, and where more specific control, the general terms of this Policy for individuals in the listed regions.

Planndora is built for professional and organizational use and is not directed to, or intended for use by, anyone under 18 years of age. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us at support@planndora.com and we will take appropriate steps to remove it.

Marketing emails we send are sent consistently with the Australian Spam Act 2003 (consent, clear sender identification, and a functional unsubscribe mechanism in every message) and, for recipients in the EEA/UK, on a consent basis consistent with the ePrivacy Directive/PECR. You can unsubscribe at any time; this does not affect transactional or security messages necessary for the Service.

Business customers who need a formal processor agreement — for example to meet their own GDPR Article 28, UK GDPR, or equivalent obligations — can request a Data Processing Addendum from support@planndora.com. The DPA covers processing instructions, confidentiality, sub-processor authorization and notice, international transfer mechanisms (including SCCs/IDTA where relevant), breach notification timing, deletion or return of data on termination, and audit rights, and will reflect the deployment model your organization has chosen under Section 4.

We may update this Privacy Policy from time to time. Material changes will be posted on this page with an updated effective date, and where a change materially reduces your rights we will take reasonable steps to notify affected customers directly (for example by email) in advance of the change taking effect. Continued use of the Service after changes become effective constitutes acknowledgment of the updated Policy.

Apptriangle Pty Ltd (ABN 78 651 767 949, ACN 651 767 949)

10 Mount Street, North Sydney, 2060, NSW

Privacy requests, data requests, and security concerns: support@planndora.com

We will respond within a reasonable time consistent with applicable law, and in line with the timeframes set out in Section 13.