Privacy policy

Scope and roles

QuotaLedger processes app configuration and technical Jira/Jira Service Management identifiers on behalf of the Atlassian customer that installs the app. The customer determines the projects, organizations, contracts, rules, users, and retention settings used. TechnofyStore acts as the service provider and, where applicable, processor for this customer-directed activity.

Data processed

The app stores project, issue, worklog, organization, Atlassian account, rule, contract, period, bucket, source-event, and audit identifiers needed to resolve coverage, authorize views, reconcile Jira events, and create exports. It also stores quantities, timestamps, statuses, compact rule predicates and formulas, correction reasons, and technical correlation data.

QuotaLedger does not intentionally persist issue descriptions, comments, attachments, customer messages, worklog descriptions, API tokens, payment-card data, or third-party analytics identifiers.

Purposes

• Configure and apply contractual entitlement rules.
• Maintain an append-only ledger and rebuild balance projections.
• Reconcile delayed, duplicated, updated, or deleted Jira events.
• Authorize administration, issue, organization, and portal views.
• Produce customer-requested diagnostic and export artifacts.

Hosting and subprocessors

Application compute and storage use Atlassian Forge and Forge SQL, isolated per installation. The current release declares no remote backend, external storage, advertising, session replay, or analytics egress. Atlassian supplies the hosted platform and its applicable infrastructure, residency, security, and subprocessor commitments.

Access and disclosure

Jira project permissions are combined with group-backed internal roles. Portal output requires an authenticated request and current membership in the bound JSM organization. It omits internal rules, traces, authors, confidential adjustments, and unrelated organization data.

Retention, export, and deletion

Configurable retention removes eligible terminal source-event detail while stable ledger evidence remains available for idempotency and contractual audit. Corrections use append-only reversals or adjustments. Authorized administrators can export contract data and a site data-management manifest before uninstalling. Atlassian's current Forge hosted-storage lifecycle governs deletion after uninstall.

Security

Controls include prepared SQL statements, server-side authorization, bounded schemas, idempotent event keys, immutable ledger movements, forward-only migrations, redacted diagnostics, dependency gates, and no anonymous portal channel.

Requests and contact

Requests for access, correction, export, restriction, objection, or deletion should be sent to support@callsiq.com or submitted through the TechnofyStore support portal. Include the Atlassian site URL and technical installation identifiers, but do not send credentials, issue bodies, or full ledger exports.

The customer/site administrator may need to help identify records because the underlying technical identifiers originate in the customer's Atlassian site.