Local-first architecture
Source files, previews, and metadata remain on the desktop. Credentials remain local by default; synchronized secrets are encrypted before database storage when encrypted sync is enabled.
Account protection
Desktop sessions use operating-system protected storage. Paid access is verified by the account service, plan and device limits are enforced server-side, and revoked devices lose account-validated access.
Manual bKash verification
Manual requests store the sender number, transaction ID, plan, duration, discounts, and review status needed to match payment and manage access. Verification and approval are restricted to authorized administrators. Automagine never requires a bKash PIN or one-time code.
Coupon and membership integrity
Coupon eligibility, expiry, limits, reservation, and redemption are enforced server-side. Uses are reserved on submission, redeemed on approval, and released on rejection. Renewal duration and eligible plan-switch credit are also applied server-side to reduce manipulation and duplicate processing.
Lemon Squeezy security
Where available, Lemon Squeezy collects payment details as Merchant of Record. Checkout uses server-only credentials, and billing webhooks are signature-verified and processed idempotently.
Application integrity
Production builds use renderer sandboxing, context isolation, restricted Node runtime features, and application archive integrity validation. Administrative credentials are not packaged with the desktop application.
Responsible disclosure
Report vulnerabilities to security@automagine.app. Do not access other users' information, disrupt service, or disclose an issue publicly before we have had a reasonable opportunity to investigate.