SMARTECHOR · 9 September 2026
Capacity privacy policy
Effective 9 September 2026. This policy covers Resource Capacity Planner for Jira (Capacity), provided by SMARTECHOR LLC, 30 N Gould St Ste R, Sheridan, WY 82801, United States. Privacy and support contact: support@smartechor.com.
Responsibilities and purpose
Your organization decides which workforce and Jira information to use for planning and who can access shared plans. We process app data to provide the functions it requests, under its instructions and applicable agreement. We separately use support correspondence to answer enquiries, protect the service and meet applicable obligations. SMARTECHOR LLC is responsible for the privacy, security and integrity of the data it or Capacity processes under its obligations; Atlassian does not take over our responsibilities as app provider.
Information we process
Under the signed-in user’s Jira permissions, Capacity reads board and sprint names and identifiers; issue IDs, keys and summaries; assignee account IDs and display names; status categories, remaining estimates and issue-wide logged time. It does not request issue descriptions, comments, attachments or worklog comments.
Saved plans contain dates, member names and identifiers, roles, daily hours, focus, working days, holidays, unavailable hours and proposed assignments. Shared plans also contain owner and collaborator identifiers, access roles, review status, named scenarios and up to 50 recent activity entries. Planning studio can store dated allocations, team-entered skills and staffing assumptions. Owner-only fields contain rates, budgets, manually entered actual costs and up to five Jira workload snapshots, including issue IDs and aggregate measures. Do not enter medical diagnoses, reasons for leave, passwords or unnecessary sensitive information.
Processing, storage and sharing
Capacity runs on Atlassian Forge and stores app records in Forge Custom Entity Store. Source Jira issue details are read for the current user; app code does not persist issue summaries or generated report files. Account-derived private storage keys are pseudonymous identifiers, not anonymization. Shared-plan access is controlled by owner-assigned roles; collaborators do not receive owner-only financial inputs and historical snapshots in app responses.
Users may download CSV and PDF reports. Private financial and historical sections require explicit owner selection. Downloaded files are controlled by the recipient; access revocation cannot recall them. Capacity does not change Jira assignments or issues, send invitation emails, or connect to an external AI, advertising, analytics or application backend. Atlassian may separately process platform operational metadata.
The application platform provider is Atlassian. Website and support mail are hosted through UNLIMITED.RS, a brand of UNITED INTERNET DOO. Information you submit to support is processed in that separate channel. Authorized service providers receive information needed for the service. We may disclose information when required by law or to establish or defend legal claims, subject to applicable protections. We do not sell personal information or use it for cross-context behavioral advertising.
Retention and erasure
Your private plan remains until replaced or erased in Settings. Erasure replaces plan content with an empty plan and fresh revision; a minimal account-derived key and revision remain to prevent stale editors restoring deleted content. Owners delete shared library plans separately. Shared deletion clears content, scenarios, collaborators, financial inputs, snapshots and prior history; a minimal owner/record/revision/deletion-event marker remains. These controls do not erase source Jira data or downloaded reports. Contact us for assistance with a complete personal-data request, including residual identifiers.
Atlassian controls post-uninstall retention and backup disposal for Forge-hosted data. Uninstall is not immediate physical erasure and reinstall is not an automatic restoration promise. See Atlassian’s current hosted-data lifecycle. Support messages are kept while necessary to resolve the request, handle related follow-up, or meet a specific legal or dispute-related obligation; contact us to request deletion. Support copies and platform backups are distinct from live plan records.
Website support and browser data
The support form sends your name, email, product, optional store URL, message and optional screenshot to our support mailbox and sends you an acknowledgment. An essential session cookie protects the request; temporary hashed anti-spam records expire after one hour. Attachments are emailed, not placed in public uploads. Website hosting logs may include IP address, timestamp and browser information. The showcase has no advertising or analytics scripts. App records displayed in the browser and downloaded files are also subject to your organization’s device policies.
Legal bases and international processing
For our own processing, where applicable, we rely on performing a contract or requested pre-contractual steps, legitimate interests in responding to support and protecting the service, and legal obligations. Your organization determines the lawful basis for its workforce planning and provides its own staff notices. Capacity does not make automated employment decisions or authorize employee monitoring.
Processing locations depend on Atlassian’s supported hosting/residency settings and service-provider arrangements. Forge hosted-storage residency does not promise that all compute, platform metadata, support messages or downloads remain in one country. Where required, international processing must be covered by applicable contractual safeguards or another lawful transfer mechanism. Contact us for deployment-specific information and to complete a required data-processing agreement before processing subject to that agreement. No certification or EU-only processing claim is made.
Your rights
Depending on applicable law, you may request access, correction, deletion, restriction or portability, object to certain processing, withdraw consent where relied upon, and complain to your competent data-protection authority. We may request proportionate verification of identity and authority. Contact your organization’s Jira administrator about source Jira data; we assist with app-held information and directly handle requests about our support records. A CSV capacity report is not a complete personal-data export.
Security, contact and changes
Report privacy or security concerns to support@smartechor.com, naming Capacity. Send sanitized details initially and never passwords or API tokens. Measures include permission-controlled source reads, per-record access rules and revision checks; no system guarantees absolute security. Material changes to this policy will be notified as required by law and contract, with an updated effective date.