Private Beta EULA
Defines the temporary evaluation licence, ownership, prohibited conduct, confidentiality, data responsibilities, expiry and beta risk notice.
Controlled testing
These materials describe how StamPOS intends to control pre-release builds, tester access, payment testing, incidents and feedback. Final legal documents will be reviewed and issued directly to each approved tester.
Defines the temporary evaluation licence, ownership, prohibited conduct, confidentiality, data responsibilities, expiry and beta risk notice.
Records the tester, approved site, devices, build, testing period, scope, support arrangements, confidentiality and termination rights.
Covers installation checks, required scenarios, sandbox payment tests, severity levels, bug reports and end-of-test actions.
Provides a consistent record for payment mismatches, data corruption, security concerns, workflow failures and supporting evidence.
Confirms legal access, beta labelling, build identification, backup testing, payment safeguards, security review and tester support.
Approved testers receive the current version directly so that the correct build, dates, parties and testing restrictions can be recorded.
Beta builds are not for general production use. Sandbox or simulator payment modes are required unless a specific live pilot is authorised in writing. Testers must maintain independent records and backups, minimise personal information and immediately stop affected testing if money, payment state, security or data integrity may be at risk.
The EULA and Beta Testing Agreement are working templates and are not presented as final legal advice. StamPOS intends to have the documents reviewed by an Australian commercial solicitor before relying on them with unrelated external businesses or live commercial transactions.
Each issued document should identify its version, effective date, approved build, tester, devices and testing period. Website summaries do not replace the signed documents supplied for a particular private beta.