Privacy notice
Last updated: September 14, 2026
This notice explains how HourMargin handles information through the HourMargin website and the Budget Guard app for Jira Cloud.
Who handles your information
The provider is Ahmet Çağrı Şimşek, operating as HourMargin in the Netherlands. HourMargin acts as controller for its website and business-contact activities, and as processor (or subprocessor) for Jira app data processed on the customer's instructions. Our Customer Data Processing Addendum describes the terms for that customer-directed processing and how it becomes part of a customer agreement.
Website information
- Your work email, Jira user range and consent to receive Marketplace launch emails.
- Your company name, when you choose to provide it.
- Basic campaign attribution, page interactions, a browser-session identifier and a country code supplied by our hosting infrastructure.
Budget Guard app information
Budget Guard reads Jira worklogs so it can calculate project budget usage. The app stores only the fields needed for that purpose in tenant-scoped Atlassian Forge storage:
- Jira project, issue, worklog and account identifiers.
- Worklog dates, update times and time-spent values.
- Budget, currency, cost-rate and billing-rate settings entered by a Jira administrator.
- Cached Jira display names, project-role references, user/role rates and notification-recipient references.
- Configuration audit actor identifiers and timestamps, synchronization status and privacy-processing records.
Budget Guard does not send Jira worklogs, financial settings or calculated project totals to hourmargin.com or to an external analytics service. App data remains within Atlassian Forge services.
Why we use it
We use website information to manage launch updates, evaluate demand and improve the website. We process Jira app information to provide customer-directed budget calculations, role/user rates, synchronization, exports, access control, administrator-configured Jira-native weekly summaries, privacy reporting and troubleshooting. The app does not use Jira data for website marketing.
Sharing and sale
We do not sell personal information. Website infrastructure providers may process limited website data on our behalf to host and secure the site. Atlassian provides the Forge runtime and storage used by Budget Guard. We do not currently use advertising cookies.
Access and security
Financial settings and app results are available only through the installed Jira site. Budget Guard requires Jira administrator permission before returning or changing this information. Forge storage is scoped to each app installation and encrypted at rest by Atlassian.
Retention and your choices
We keep launch-list submissions only while they are useful for Marketplace launch communication and product evaluation. A Jira administrator can delete a project's Budget Guard configuration, worklog ledger, audit entries and synchronization records from inside the app. Forge-hosted storage may retain soft-deleted installation data for up to 28 days after app uninstallation under Atlassian's hosted-storage lifecycle.
Site-wide deletion also removes shared privacy-processing state. Atlassian account closure/update reporting removes cached profile names, not every identifier-linked worklog, rate or financial record. For broader requests, contact us to coordinate the appropriate project/site deletion or platform-dependent steps. App CSV reports are not a complete export of every stored personal-data category.
You can unsubscribe from launch emails or ask us to access, correct, export or delete website information at any time. Jira app export and deletion requests must come from an authorized administrator of the relevant Jira site.
Contact
Email privacy@hourmargin.com for privacy questions or data requests. For product support, email support@hourmargin.com.