Trust and data handling
Privacy
ABM Warranty is built for Apple IT operations, where data accuracy and administrative control are non-negotiable. We designed the product to support real-world fleet management without introducing unnecessary collection or opaque processing behavior.
Privacy policy
ABM Warranty Privacy Policy
This Privacy Policy applies to the ABM Warranty app (the “Application”), created by Jon Brown (the “Service Provider”) as a freemium service. The Application is provided “AS IS.”
What information does the Application obtain and how is it used?
The Application does not obtain personal information when you download or use it. Registration is not required to use the Application.
Does the Application collect precise real-time location information?
No. The Application does not collect precise location information from your device.
Do third parties see and/or have access to information obtained by the Application?
No. Since the Application does not collect personal information, no personal data is shared with third parties.
What are my opt-out rights?
You can stop all information processing by uninstalling the Application. You may use the standard uninstall processes available through your device or application marketplace.
Children’s privacy
The Application is not intended to knowingly solicit data from or market to children under 13 years of age.
The Service Provider does not knowingly collect personally identifiable information from children. Parents and legal guardians are encouraged to monitor children’s internet use and instruct children not to submit personal information through the Application without permission.
If you believe a child has provided personal information through the Application, contact: hello@abmwarranty.com
You must also be at least 16 years old to consent to personal data processing in your country (or have a parent/guardian provide consent where permitted).
Security
The Service Provider is committed to safeguarding confidentiality. Since the Application does not collect personal information, there is no stored personal dataset in the Application to be accessed by unauthorized parties.
Changes to this policy
This Privacy Policy may be updated from time to time. Updates are posted on this page. Continued use of the Application after updates is treated as acceptance of the revised policy.
Effective date: March 20, 2026
Your consent
By using the Application, you consent to this Privacy Policy as currently published and as amended in the future.
Contact
If you have privacy questions about the Application, contact: hello@abmwarranty.com
FAQ
Common questions
How does the app authenticate with Apple Business Manager?
ABM Warranty uses Apple’s official OAuth 2.0 client flow. You create an EC P-256 private key in Apple Business Manager, then enter the required identifiers in the app. Credentials are stored locally on your Mac and are not sent to third-party services.
Is this safe to use in large environments?
Yes. The app is designed for large organizations and includes pagination safeguards, serialized coverage requests, retry handling, and protections for malformed or partial ABM API responses.
Does the app modify any data in Apple Business Manager?
No. ABM Warranty is focused on reading and reporting warranty data; it does not modify device records or coverage settings in ABM.
What happens if some devices fail to load or return errors?
Individual device failures do not stop the overall import. Errors are captured so the app can continue processing remaining devices and you can review failed items later.
Can I export warranty and coverage data?
Yes. You can export warranty and AppleCare+ coverage data to CSV for audits, lifecycle planning, budgeting, and internal tooling.
How do I use managed preferences?
Managed preferences allow you to deploy and enforce configuration for ABM Warranty using your MDM, removing the need for manual setup on each device. This is especially useful in enterprise and MSP environments where consistency and control matter.
To use managed preferences, you define the required keys (such as API credentials, certificates, or feature flags) in a configuration profile and deploy it via your MDM solution (e.g., Jamf, Kandji, Mosyle). Once applied, ABM Warranty will automatically detect these managed settings at launch and treat them as authoritative.
If managed preferences are present, the app respects them as read-only. Users cannot override or modify these values locally, ensuring that credentials and configuration remain consistent across all deployed machines.
This approach is ideal for standardized environments where administrators want to centrally control how ABM Warranty is configured and used.
Source: Managed Preferences.
How do I use managed credentials?
Managed credentials are designed for environments where API access should be centrally controlled and not manually entered by end users.
Instead of adding credentials directly within the app, administrators can deploy them via managed preferences (MDM). Once deployed, ABM Warranty will automatically load and validate these credentials on startup.
Managed credentials are clearly distinguished from manually added credentials within the app. They cannot be edited or deleted by the user, which prevents accidental changes or credential drift.
This is particularly useful for MSPs managing multiple tenants, organizations with strict access controls, and environments where credential rotation and auditing are required.
The app will use these managed credentials just like local ones, but with added safety and enforcement from the management layer.
Source: Multiple Credentials.
How do I use the ABM Credential Packager?
The ABM Credential Packager is used to prepare your Apple Business Manager API credentials for deployment via MDM.
Instead of manually distributing raw API keys and certificates, the packager bundles them into a format that can be securely embedded into a configuration profile.
The general workflow is:
1. Export your ABM API key and certificate from Apple Business Manager
2. Use the Credential Packager tool to convert certificates into the required format and bundle credentials into a structured payload
3. Insert the packaged output into your MDM configuration profile
4. Deploy the profile to target devices
Once deployed, ABM Warranty will automatically detect and use these credentials as managed credentials, requiring no user interaction.
This process ensures secure handling of sensitive credentials, consistent deployment across devices, and compatibility with managed preferences. It is the recommended approach for organizations deploying ABM Warranty at scale.