Legal
Privacy Policy
How Planndora System collects, uses, protects, and shares personal information across the product, billing, and platform security controls.
Introduction
This Privacy Policy describes how Planndora System (“Planndora”, “we”, “us”, or “our”) collects, uses, stores, and shares personal information when you visit our website, create an organization, or use our project and product management platform (the “Service”).
By using the Service, you acknowledge this Policy. If you use Planndora on behalf of an organization, that organization may control your workspace account and related content.
Who We Are
Planndora is a multi-tenant workspace for projects, issues, sprints, documentation, ideas, integrations, and related collaboration features. Platform administrators operate organization-level controls; workspace admins manage members, billing, and project access within their tenant.
- Contact for privacy requests: support@planndora.com
- Product website and application operated under the Planndora System brand
Information We Collect
Account and organization data
- Name, email address, password (stored as a secure hash), phone, profile fields (bio, job title, department, avatar), and role within an organization.
- Organization profile details such as name, slug, industry, website, employee count, and address fields.
- Member invitations, verification tokens, and password-reset / OTP flows.
Workspace content
- Projects, issues, sprints, comments, attachments, documents, wiki content, ideas, assignees, watchers, and activity history you create or upload.
- Integration configuration you connect (for example Slack, WhatsApp, or Google Calendar credentials as configured by your organization).
Billing and payment data
- Plan selection, seat counts, subscription status, billing period dates, invoices, receipts, and payment history.
- Payment method details are processed by our payment processors (primarily Stripe; PayPal where enabled). We do not store full card numbers on Planndora servers.
- Customer and subscription identifiers returned by Stripe (or PayPal) needed to manage billing and proration.
Security, device, and usage data
- IP address, user agent, approximate location signals when available, timestamps, and action type for security audit events (for example login success/failure, logout, password changes, invites, role changes, project create/delete, billing changes, IP block/unblock).
- IP blacklist entries maintained by platform superadmins (IP address, reason, creator, active status, optional expiry).
- Transactional email usage metadata (recipient, purpose, subject, status, actor, organization) for deliverability and abuse monitoring.
- Product usage events needed to operate features, diagnose errors, and improve performance.
Security: Security logs & IP controls
Platform operators may review security logs and block abusive IP addresses. Blocked IPs are denied API access (including login). These records exist to protect accounts, workspaces, and the Service.
How We Use Information
- Provide, operate, maintain, and improve Planndora features (projects, issues, watchers, documents, notifications, MCP/API 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.
Legal Bases (Where Applicable)
If you are in a region that requires a legal basis for processing (for example the EEA/UK), we rely on one or more of: performance of a contract (providing the Service), legitimate interests (securing the platform, preventing abuse, improving reliability), consent (where we ask for it), and legal obligation.
Payments & Billing Privacy
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.
Billing: Payment processors
Stripe is the primary processor for automatic proration, seat charges, invoices, receipts, and payment retries. PayPal may be offered as an alternate checkout path where configured. Review Stripe’s and PayPal’s privacy notices for processor-side processing.
Data Retention
- 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 blacklist 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.
Security Measures
- HTTPS/TLS for data in transit; hashed passwords; role-based access (superadmin, company admin, member) and project-level membership.
- Issue edit permissions further limited so members may view project issues but edit only when assigned (or when they are admins), reducing unnecessary write access.
- Security audit logging of sensitive actions; optional IP blacklist enforced on API requests.
- No method of transmission or storage is perfectly secure. Use strong unique passwords and protect account access.
Security: IP blocking
If an IP is placed on the platform blacklist, requests from that address receive an access-denied response before normal API handling. Blocking is used to stop abuse, credential stuffing, and similar threats.
Your Rights & Choices
- Depending on your location, you may have rights to access, correct, export, restrict, or delete personal data, or to object to certain processing.
- Update profile information in-app. Organization admins control membership; contact support@planndora.com for account or privacy requests.
- You may request logout-related audit recording via the product logout flow; discard tokens client-side after sign-out.
- Marketing communications (if any) can be opted out where offered; transactional and security messages remain necessary for the Service.
Children’s Privacy
Planndora is built for professional and organizational use and is not directed to children under 16. We do not knowingly collect personal information from children. If you believe a child has provided personal data, contact us and we will take appropriate steps.
International Transfers
Your information may be processed in countries other than where you live, including where our hosting providers and payment processors operate. Where required, we use appropriate safeguards for cross-border transfers.
Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be posted on this page with an updated effective or “last updated” date. Continued use of the Service after changes become effective constitutes acknowledgment of the updated Policy.
Contact Us
For privacy questions, data requests, or security concerns, email support@planndora.com. We will respond within a reasonable time consistent with applicable law.