GiftingStack
Sign in Get started

Legal

Terms of Service

Last updated: 14 November 2026

The rules for using the GiftingStack API, dashboard and website.

1. Agreement

By creating an account or using GiftingStack ("the Service") you agree to these terms. If you use the Service for a company, you confirm you can bind it. If you do not agree, do not use the Service.

The Service is for businesses and developers who use it for their trade, business or profession. It is not offered to consumers. You must be at least 18 years old to create an account. We may refuse or close an account that is used for personal or household purposes. Nothing in these terms excludes rights that the law does not allow to be excluded.

The Service is provided by an individual developer based in the Republic of Türkiye, under the name GiftingStack ("we", "us"). Our identity and postal address are available on request at support@giftingstack.com.

2. The Service

GiftingStack gives your app balances in units you define, a catalog of gifts, a way to send gifts between your users, a ledger of every change, and webhooks, plus components that show gifts to other users of your app: gift rooms, leaderboards, gift walls and "while you were away" summaries. You connect it through our API and SDKs and manage it in the dashboard.

3. What GiftingStack is not

You decide how your users get units, for example through in-app purchases. The Service is built for virtual gifts: you must not use it to pay anyone out, to let users withdraw or cash out units or received gifts, or to exchange them for money, money equivalents (such as cash-redeemable vouchers or gift cards) or crypto assets. If your app does any of that outside the Service, it is your decision and your sole legal responsibility, and it must be lawful.

You may choose to give a user who received a gift something of your own, such as a ticket, a product or access to a service, for example a concert ticket to a user who received a "ticket" gift. That is your own offer, made outside the Service: we only record that the gift was sent, we do not deliver, guarantee or pay for what you give, and the received gift itself stays a counter that cannot be spent or transferred. You are solely responsible for that offer, including your terms with your users, consumer, tax and prize-promotion law, and the rules of the app stores where your app is sold (for example, units used to send such gifts may need to be sold outside in-app purchase). If your app does any of this, it must be lawful.

4. Your account

You sign in with your email address. Keep your email account and API keys secure. You are responsible for everything done with your keys. Revoke a key in the dashboard if you think it has leaked. Give us accurate information and tell us if it changes.

5. Your responsibilities

Reporting illegal content. Anyone can report content they believe is illegal, such as an uploaded image or a display name shown in a gift room, to support@giftingstack.com, our single point of contact for users and authorities. Please say where the content is (for example the image address or the app and room), why you believe it is illegal, and how we can reach you. We review each report without undue delay and tell the person who reported it, and the customer whose content it is, what we decided and why.

6. What your users see of each other

Some features show one end user's activity to other users of your app: gift rooms send each gift, with the sender's display name and user identifier and the receiver's user identifier, to everyone in the room; leaderboards show user identifiers with their gift counts and ranks; gift walls show the gifts a user or a post received. You decide whether your app uses these features, which rooms a user may join, and which display names, gift names and messages you send to us.

7. Gift artwork and uploaded images

The ready-made gift artwork in our library is licensed to you, to the extent we own or may license rights in it, for use inside the apps you connect to GiftingStack. Some of it was made with the help of AI tools; we do not promise that every piece is protected by copyright or that you get exclusive rights in it. The licence is non-exclusive and non-transferable. You may not sell or redistribute the artwork files on their own, offer them as a library or asset pack, or present them as your own work. Artwork you upload stays yours. The library artwork is provided as is: we do not promise that no one else has rights in a piece. If you tell us about a claim, we will look at it and, where needed, replace or remove the piece.

Images you upload. In the dashboard the project owner can upload images for your gifts. They must be PNG, JPEG or WebP files of up to 2 MB, and each project environment (test and live) can hold up to 200 files and 100 MB in total. You are responsible for having the rights to everything you upload, and you must not upload unlawful or infringing content. Uploaded images are served publicly from uploads.giftingstack.com. We may remove content that breaks these terms.

8. Plans, limits and billing

The plans are Test (free), Starter (29 USD a month), Growth (99 USD a month) and Scale (499 USD a month), as described in the pricing section of the website; the prices are published and there are no individual agreements. Paid plans are billed through Creem. Prices exclude taxes; VAT or sales tax is added at checkout where required. The Service has technical limits to protect it, such as rate limits per project environment (shared by its secret keys), a cap on users and monthly operations in the test environment (50 users, 5,000 operations a month) and the number of viewers per gift room (20 in a test room, 1,000 on Starter, 5,000 on Growth, 20,000 on Scale); requests beyond them may be rejected. The current limits are shown on the website. The live environment needs a paid plan: on Test you can create no live keys and make no live changes; live keys made earlier can then only read data and delete end users.

8.1 Service fee based on verified sales

Besides any plan fee, the Service fee for the live environment depends on the coins you sell. The fee base for a month (UTC) is the USD value of (a) store sales: credits you booked in the live environment with a verified App Store or Google Play receipt, at the price the store reports as paid by your user (before the store's commission, and including sales tax or VAT where the store's price includes it), minus store refunds of those purchases; plus (b) web sales: credits booked with a price and currency and no receipt, at the price you declared; plus (c) bonus excess and (d) the web spending floor, both as set out in 8.3. Test credits are never counted. The sales share is the same on every paid plan: nothing on the first 2,000 USD of your account's fee base in the month, 1.5% of the part from 2,000 USD up to 500,000 USD and 1% of the part above 500,000 USD, with no cap. The monthly plan fee is due on a paid plan in every month, whatever the fee base. A project's month in which refunds exceed sales counts as zero. Amounts in other currencies are converted to USD with the daily euro foreign exchange reference rate published by the European Central Bank for the day of the sale (the latest earlier rate within 14 days if none was published that day); an amount in a currency for which no such rate is available is not counted. The fee is calculated on the figures the Service records; we never receive, hold or move the money your users pay.

The sales share of a month is charged through Creem with the first renewal of your plan after that month has closed. The dashboard shows how each month's fee base is made up: verified store sales, refunds, declared web sales, bonus excess and the web spending floor. If your subscription ends before the share of a closed month has been charged, that share stays due and we charge it through Creem separately.

A project is one app. The exemption and the share tiers apply to the total live sales of all projects your account owns: your account's fee base is the sum of the fee bases of its projects on a paid plan, and the share is divided among those projects in proportion to their fee base. The plan fee is due for each paid project. Splitting one app across projects or accounts to lower the share is a wrong record (section 11).

8.2 Accurate sales records

You must credit each sale of coins in the way that matches it: a store sale with its verified receipt (the price then comes from the store), a sale in your own web shop with the price your user actually paid, and anything that is not a sale as a bonus, without a price. A credit that says none of these is refused. For a Google Play sale we read the order price with the service account you provide, which needs the Play Console permission to view financial data; if it is withheld, the sale cannot be priced and you remain responsible for crediting it correctly.

In particular: coins sold inside your iOS or Android app are sold through Apple's or Google's in-app purchase and credited with the verified receipt. You must not record such a sale as a web sale or as bonus coins. Coins sold on the web are credited with the price and currency your user actually paid. A credit of coins that were sold, left without a price or called a bonus, is a wrong record. Wrong records are reporting your sales incorrectly in the sense of section 11. These terms do not change Apple's, Google's or your payment provider's own rules, which you must follow too.

8.3 Bonus coins, web spending floor, checks and retroactive billing

Coins credited without a receipt and without a price are not a sale. Each month, up to 20 % of the coins you credited as sales (store and web) may be given away without counting. Coins above that allowance are the bonus excess, valued at the average verified store price per coin of the same month, or the average declared web price per coin when there is no verified store sale that month (nothing is added in a month with neither), and added to the fee base.

Coins your users spend on gifts should come from coins you credited. For each month we take the coins spent on gifts in the live environment over that month and the two months before it, and subtract the coins credited as sales (store and web), the 20 % allowance, the bonus excess and the coins already counted this way in the earlier months of that period. If 10,000 or more coins remain, they are the web spending floor: valued at the average declared web price per coin of the period, or the average verified store price per coin when there is no declared web sale (nothing is added when there is neither), and added to the fee base. A coin is counted at most once. There is no web spending floor in the first three months in which your project uses the live environment, or in a month in which your plan changed.

We may compare declared web sales and bonus coins with your verified store data, with the coins spent on gifts in your project and with the coin prices shown publicly on your website, web shop or app. We may bill retroactively, for up to 12 months before we tell you what we found, (a) for web sales declared at a price lower than what your users paid, for the difference, and (b) for store sales credited without their receipt, at the store price. Before we bill we send you the months concerned, the records we relied on, how we calculated the amount and the amount itself, and you have 15 days to explain or send evidence. We review what you send in good faith and give you our reasons before we charge. An amount you dispute in good faith is not treated as unpaid while we review it. A charge for earlier months under this section is billed through Creem and is due like any other charge; if it stays unpaid, section 11 applies. A transaction or coin is never charged twice.

8.4 Audit

On reasonable written request, and no more than once a year, you will give us the information we need to confirm your credits and sales, limited to your credit records, the store prices of the products you sell and the prices of your web sales.

Receipt verification and store notifications (see the Privacy Policy) are part of the Service; on the live environment verified receipts are how store sales are recorded for the fee.

8.5 Cancellation, plan changes and refunds

Paid plans renew every month until you cancel. You can cancel at any time in the billing portal; your plan stays until the end of the period you have paid for and is not renewed after it. A change to another paid plan takes effect at once, and Creem works out the difference for the rest of the current period: for a more expensive plan it is charged to your saved card when you confirm the change.

Fees already paid, including the plan fee for a period that has started and the sales share of a closed month, are not refunded, except where we made a billing error or the law requires a refund. To report a billing error, write to support@giftingstack.com; Creem, our merchant of record, takes payments and issues receipts and any refund under its own terms.

8.6 Price changes

We may change our prices. A new price applies from the first billing period that starts at least 30 days after we tell you by email or in the dashboard. If you do not accept it, you can cancel before it applies.

9. Availability and changes

We work to keep the Service reliable, but we do not promise it will be uninterrupted or error-free, and we offer no service level agreement. We may change or remove features. Where a change breaks an existing integration or removes a material feature of a paid plan, we will give at least 30 days' notice where we reasonably can, except when the change is needed at once for security, the law or to stop abuse. If such a change substantially reduces what your paid plan does, you can cancel before it applies.

10. Your data

Your data stays yours. You give us the right to process it to provide the Service. How we handle personal data is described in the Privacy Policy and the Data Processing Addendum. The live ledger is append-only by design, so balance changes are corrected by new entries and not by editing old ones; the test environment can be reset by the project owner, which erases its data.

11. Suspension, deletion and ending

You can stop using the Service at any time. The project owner can delete a project in the dashboard and delete the account once it owns no project. We may suspend or end access if you break these terms, put the Service or other people at risk, or if the law requires it. Where we reasonably can, we will warn you and give you time to export your data first. If an account breaks these terms seriously, we may delete its projects without waiting for the grace period below.

Deleting a project cannot be undone once it has run. When the owner asks, the API keys stop working at once; for 7 days the owner can cancel; after that the project's data is permanently erased from our live systems (normally within about 8 days of the request) and from Cloudflare backups after up to 30 days more. The limits of this are in the Privacy Policy (section 5) and the DPA (section 8): for example webhook messages already queued for retry (up to 5 days) and copies you hold yourself. We keep records the law requires, such as invoices, for the legal period.

We may suspend your live environment if an amount you do not dispute stays unpaid 7 days after we asked you to pay it (this includes a charge for earlier months under section 8.3), or if you report your sales incorrectly: for example a web sale declared below the price your user paid, or store sales credited without their verified receipt. Before suspending we tell you what we found and give you 7 days to correct it, unless the case is a repeat of one we already told you about. We lift the suspension once the invoice is paid or the records are corrected, and we do not delete your data because of a suspension.

While the live environment is suspended: live API keys can still read data (GET and HEAD requests) and can still delete an end user, so you can export your data and honour privacy requests; every other write, such as credits, debits, gift sends, token creation and battles, is refused with the error project_suspended and the reason; client tokens and gift rooms stop working; queued webhooks are still delivered. Your test environment is never suspended. The reason we give is shown to you in the API response and in the dashboard.

We may also suspend the live environment at once, without the 7-day period, if we reasonably believe the Service is being used for fraud, illegal content or an attack, and we will tell you why.

12. Disclaimers

The Service is provided "as is" and "as available". To the fullest extent the law allows, we give no warranties of any kind, including fitness for a particular purpose and non-infringement. Nothing in these terms limits rights you have under law that cannot be limited.

13. Limit of liability

To the fullest extent the law allows, we are not liable for indirect, incidental or consequential loss, or for lost profit, revenue, data or goodwill. Our total liability for any claim relating to the Service is limited to the greater of the fees paid for the Service in the 12 months before the claim and 100 USD. These limits do not apply to fraud, wilful misconduct or gross negligence, or to any liability that cannot be limited by law. They do not limit the rights of data subjects or the powers of data protection authorities.

14. Changes to these terms

We may update these terms. We tell you about a meaningful change by email or in the dashboard at least 30 days before it applies, unless the law or security needs it sooner. The sign-in form shows the current version and records which version you accepted. If you do not accept a change, you can cancel before it applies. A change that adds fees or obligations to your paid plan applies to you only once you have accepted it.

15. Governing law

These terms are governed by the laws of the Republic of Türkiye, without its conflict-of-law rules. Before going to court, the parties try for 30 days to settle a dispute in good faith after one of them describes it in writing. Disputes then go to the courts and enforcement offices of Istanbul, Türkiye, where such a choice is valid, unless the law gives you a right to bring them elsewhere that cannot be waived.

16. General

17. Contact

GiftingStack, operated by an individual developer in the Republic of Türkiye. Questions about these terms: support@giftingstack.com.