FAQ

Your questions, our answers.

Availability, plans, billing and — the one we get most — what we do and don't know about your app.

Availability

Transaction validation on Google Play, the Apple App Store and PayPal. SDKs ship for Unity and Godot, everything else integrates through the REST API.

Our cloud and storage servers run on the edge, distributed around the world, handling billions of requests within milliseconds. Requests are routed to the location nearest your user.
Plans

On the first day of the month, at 00:00 UTC.

Yes. If you see a sudden increase in transactions for an app, upgrading to a paid plan extends its quota immediately.

Absolutely. After cancelling you keep the remaining quota and features until the end of the month, and the app then converts to the free plan.
Billing

No — the free plan requires no payment details at all. When you subscribe to a paid plan, our payment partner offers several payment methods based on your location.

You pay a base subscription per application, which includes an amount of free transactions each month. Going over that quota puts the application’s transactions into usage-based billing in steps of 100. Usage is billed one month later, to make sure you have already received the payout for those earnings.

No. Google, Apple and PayPal continue to pay you exactly as before. IAPGUARD validates your transactions — we do not process them in terms of payment.

Our website is SSL secured and your payment details are transmitted to our payment partner, Paddle.com Inc. We access parts of your personal information in order to provide the service, but we have no access to your payment information. See the Terms of Service and Privacy Policy for the full picture.
Privacy

No. App Store responses do contain information about individual product prices from your app, but we do not process or aggregate them in any way. Unlike our competitors, we do not know, and are not interested in knowing how much revenue your app generates.

To guarantee that transactions are unique, their alpha-numerical identifiers are persisted to our cloud backend — not their contents. For display in the dashboard, our frontend server records only the most recent transactions and wipes them every few hours.

For privacy reasons we do not track purchase history, only a user’s current inventory.

No. User identifiers should be a random alpha-numerical sequence returned by your own authentication system. Please don’t use email addresses or names as identifiers, so that your integration stays compliant with privacy requirements.

Still unanswered?

Write to us — a real person reads it.