Acceptable use policy

1. What this covers and how it changes

This policy forms part of the terms of service and uses the terms defined there. It covers you, every Authorised User, and everything you send to or create within the Service. It takes effect on {effective date}. Gemifier may amend it on {AUP notice period} notice, or immediately where the law or an active abuse or security issue requires it.

Automated use is the intended use. You drive the Service through an API. Scripted, server-to-server access is expressly permitted, and nothing here limits the volume, frequency or automation of legitimate calls beyond the limits in section 11 and in your Order.

2. Data you must not send

The Service has no field for this. Do not put it in one that will accept it:

• special category personal data: racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, health data, or data concerning sex life or sexual orientation;
• data about criminal offences, convictions or alleged offences;
• government-issued identity numbers and identity documents;
• payment card numbers, security codes or any other cardholder data;
• credentials, authentication secrets, keys or tokens, yours or anyone else's;
• personal data about anyone for whom you have no lawful basis to send it.

Exclusion and cooling-off flags are the deliberate exception. Send a true or false flag saying an individual is excluded or in a cooling-off period, so eligibility rules can act on it. Send no narrative, diagnosis, treatment, harm assessment, spend concern or other detail about their gambling behaviour or wellbeing.

3. Choosing an identifier

You identify each End User with an identifier you choose. We hold only what your systems send, what your staff enter in the dashboard, and what the Service derives from those. Choose an identifier that reveals no more than it needs to: an internal account number is a good choice; an email address, a national identifier, a payment reference or a person's name is not. You may later display or disclose it in a context you did not plan for; Gemifier will not mask or pseudonymise it, and you warrant you have considered this.

Gemifier renders nothing an End User sees. Where you publish rankings or standings, you build that display and carry the privacy consequences.

4. Free-text fields and file names

Free-text attribute values, event property values, points adjustment reasons, marketplace reversal reasons and the file names of uploaded media all accept arbitrary text. So do image contents. Gemifier does not inspect, filter, moderate or screen any of them.

The accurate statement is that the schema has no personal data fields and requires none, not that personal data is technically impossible to send. Keep personal data out unless you put it there deliberately and record that decision. Section 3 of our privacy policy says the same from the other side; the data processing agreement sets out the categories you may send. Anything outside them is sent at your own risk.

5. Mechanics, licences and the law

You decide which mechanics to run, in which markets and for whom, and you hold every licence they require. You decide whether a mechanic is a game of chance, a lottery, a prize competition, a sweepstake, a prize promotion or an advertisement, and you comply with the law that follows. You are the sole promoter, and Gemifier gives no gaming, financial, tax or legal advice and warrants no configuration against any law applying to you.

You must not use the Service:

• to accept, place, settle or record a real-money wager;
• to sell a chance to win for money or money's worth;
• to operate a paid loot-box or random-reward mechanic where that is prohibited;
• to reward a loss or recovery from one, or to direct mechanics at children where your law prohibits it.

Check age and exclusion at fulfilment. The Service receives no age and no field from which age can be derived, so Gemifier cannot know whether an End User is a child or is excluded. Qualification-time checks are not enough: eligibility is locked in when an individual first qualifies for a mission, and a later signal does not remove them from an occurrence in progress. See our responsible gaming statement.

6. Rewards and points

Points, balances and marketplace credits are an internal accounting unit: not money, no redemption right against Gemifier. Gemifier does not hold, transmit, process or issue money, funds, wagers or any monetary value. You define, fund, source, deliver and honour every reward. Gemifier records a grant and, where you register a destination, attempts to tell your system, but never fulfils, never funds, and does not communicate with End Users by any channel.

A notification is a prompt to read the record, not an instruction to credit anything: it carries identifiers only, never an amount. Reconcile against the recorded grants, and check eligibility and stock before you fulfil. Gemifier does not warrant that a stock count is accurate: two purchases of a last unit can both succeed.

7. Credentials

An API key is full authority over the environment it belongs to. Keep keys server-side, out of mobile and browser applications, public repositories and screenshots, and never share one outside your organization. Revoke a key the moment you suspect it is exposed. API keys are displayed once at creation and stored by Gemifier only as a cryptographic hash; Gemifier cannot recover a key.

Dashboard credentials are personal to one individual and must not be shared. There is no second factor and no self-service password recovery, so a lost password is a lost account. Remove a member's access when they leave.

8. Outbound delivery destinations

Where you register a destination for notifications:

• register a destination you own or control, never a third party's;
• register an encrypted destination. The Service will accept a plain, unencrypted one, so this is your obligation, not something we enforce;
• verify the signature on every delivery, and reject anything that fails;
• treat the delivery identifier as your duplicate check: delivery is at-least-once, is not guaranteed, and an abandoned notification cannot be re-sent;
• do not point a destination at internal infrastructure or a network you do not control. Gemifier refuses private, loopback and reserved addresses, but that safeguard is not your compliance.

The destination is not a Gemifier sub-processor, and you are the exporter for that leg: see the data processing agreement.

9. Media and uploaded images

Only the image formats in the documentation are accepted; scalable vector files are not. Public or private is fixed at upload and can never be changed. A public asset is readable by anyone holding its address, with no credential, and is cached for a long period: unguessable, but not secret. Deleting one removes it from storage, but cached copies may persist, and an asset in use must be detached before it can be deleted.

There is no content moderation, no malware scanning and no metadata stripping. Do not upload confidential material, photographs of identifiable people, or anything you are not licensed to use. You warrant that what you upload is lawful, and Gemifier may remove content on notice.

10. Sandbox and Live

Each project has a Sandbox and a Live environment, and a key belongs to one for its lifetime. Sandbox holds separate data and separate keys, but shares infrastructure with the live service and is not an isolated system. Do not send production personal data to Sandbox: test with synthetic records.

11. Service limits and fair use

These limits are technical, not commercial. There is no per-second, per-day or per-month request quota; current values are in the documentation.

Retry a refused request with backoff. Do not spread traffic across keys, environments or organizations to get around a limit, and do not load test Live without asking us.

12. Prohibited conduct

You and your Authorised Users must not:

• interfere with the Service, probe the isolation boundary, or reach for another organization's data;
• circumvent authentication, the permission model, or the limits in section 11;
• store or transmit unlawful content, malware, or material that infringes another person's rights;
• build a competing product, or resell the Service except under a written agreement with us;
• reverse engineer the Service, except as the law expressly permits;
• publish benchmark or performance results without our written consent.

13. What happens if you breach

In the ordinary case we will tell you and give you {cure period} to put it right. We may act without notice where there is a security risk, a risk of harm to an individual, legal exposure, or a legal requirement.

Suspension is proportionate: where suspending one key, destination or environment is enough, we may do that rather than suspend your whole account. Suspension does not relieve you of fees. A serious or unremedied breach is a material breach of the terms of service, and the termination rights there apply.

14. Reporting abuse and vulnerabilities

Report abuse, unlawful content or a suspected vulnerability to {security contact}, or to business@gemifier.io, with enough detail for us to locate it. Do not test a vulnerability against another organization's data, and give us a reasonable opportunity to respond before you publish.