Skip to policy
Lukas’s Development Need a hand? ↗
THE DETAILS, IN PLAIN SIGHT

Privacy Policy

Know what we collect, and why.

Version 2026-10-24 · Effective 24 October 2026
Terms of Service Refund Policy Privacy Policy Cookies & storage

ON THIS PAGE

01Who handles your information 02Information we collect 03Where information comes from 04How and why we use it 05Licence decisions and your choices 06Who receives information 07Overseas processing 08Cookies, local storage and external content 09Tickets, transcripts and moderation records 10Service messages and marketing 11Security and incident handling 12Retention and deletion 13Access, correction, deletion and complaints 14Children and changes to this policy
01

Who handles your information

This policy explains personal information handling by the individual operating Lukas’s Development, an Australian store selling its own digital Roblox products, its support website and associated Discord bot. It covers customers, borrowers, support participants and people contacting us. We are the store operator; Roblox, Discord and Stripe also handle information under their own policies.

Store operator: the individual operating Lukas’s Development in New South Wales, Australia. Lukas’s Development is the public store brand. The operator currently does not hold an ABN.

For privacy enquiries, access, correction, deletion or a complaint, use Support and identify the request as “Privacy”. If you cannot sign in, contact staff through our Discord support server and ask for a private contact route. Do not post identity documents publicly. This policy does not create consent simply by being displayed.

02

Information we collect

We collect information needed for the following activities:

  • Accounts and linking: internal customer ID; Discord ID, username/display name, avatar information and verified email when provided through sign-in; Roblox user ID, username/profile details and the link between those identities; sign-in status, account roles, permissions and account dates.
  • Orders: products, quantities, amounts, currency, discounts, order dates/status, payment-session references, payment-provider confirmations, receipt email and the policy version and time accepted at checkout. Stripe collects payment details directly; we do not store full card numbers or security codes.
  • Licensing: purchased entitlements, lending and revocation records, recipient identity, experience/universe and creator IDs, creator type and experience information obtained from Roblox, product/version and validation mode, activation timestamps and administrative actions. Where keys are used, verification records include protected key representations rather than displaying the original secret to other customers.
  • Support: subjects, categories, messages, order references, product names, screenshots, email addresses where available, notification preferences, timestamps, assignment and staff notes.
  • Discord operation: server, user, role and channel IDs; verification progress and outcomes; role changes; ticket messages, attachments or attachment references, participants, closure details, transcripts and moderation/warning records relevant to operating the server and responding to issues.
  • Technical information: IP address and request/device/browser information available to hosting and network systems, session and OAuth transaction records, errors and abuse-prevention events. Some of this is processed transiently rather than retained in a permanent customer profile.

We do not need your game players’ private chat, passwords, Roblox login credentials, full card details or unrelated game content for a licence validation request. Avoid including unnecessary information about yourself or others in tickets.

03

Where information comes from

You provide information through purchases, sign-in, account linking, licence lending, support forms and Discord interactions. Discord and Roblox provide the profile and ownership information permitted by their sign-in and API flows. Stripe provides order/payment confirmation information. A licence-enabled Roblox server sends product, universe, version and validation-request information to our service. Other people may provide information about you in a ticket, loan, infringement report or moderation report.

We assess unsolicited information and limit its use to a relevant purpose or lawful obligation. Staff access is restricted by their duties and configured permissions. Browsing the public catalogue does not require a linked account, although purchases and protected account areas do.

04

How and why we use it

We use relevant information to establish accounts and verify account links; take and reconcile payments; deliver products; validate experience ownership and licences; manage exclusive lending; provide updates and support; operate verification and support roles; preserve ticket transcripts; investigate fraud, security incidents and rights complaints; make fair moderation decisions; communicate about your order or request; maintain necessary records; and comply with legal obligations.

We use only the information reasonably needed for a purpose. We do not sell customer lists or use licence validation to collect private game content for advertising. A customer’s private support conversation is not intended to be a public product review. We do not use your acceptance of the Terms as marketing permission.

If a law applicable to you requires a legal basis for processing, the relevant basis may be performance of your order or requested service, compliance with a legal duty, legitimate operational interests subject to your rights, or specific consent for an optional activity. We do not claim that every possible overseas privacy law applies to every customer.

05

Licence decisions and your choices

Automatic checks compare entitlement and experience ownership and can allow or deny operation without a staff member reviewing each request. Loan revocation can similarly end a borrower’s access after the current validation lease expires. These checks manage software access; they are not a credit assessment or a determination of legal guilt.

If an ownership check or licence decision is wrong, contact Support for human review. We may need the experience ID, product and order or account reference to investigate. You can stop future licence requests by removing the product from an experience, but that can prevent it operating. Withholding required identity, payment or ownership information may prevent purchasing or validating a licence; you can still use public information and seek help through the alternative contact route.

06

Who receives information

We disclose information only where relevant to the purpose and subject to applicable law. Recipients can include:

  • Authorised owner, development and support staff, with access based on their responsibilities.
  • Stripe, for checkout, payment handling, fraud prevention and refunds.
  • Discord and Roblox, for sign-in, identity/ownership checks, bot messages and platform features.
  • Render for website hosting, and MongoDB for database and file storage.
  • Resend or a configured email-delivery provider for service messages; Cloudflare where used for domain, network or incoming-mail routing. Email providers necessarily process delivery addresses, message contents and delivery metadata.
  • Professional advisers, payment dispute handlers and regulators, courts or authorities where reasonably needed to establish or defend rights, fulfil a legal requirement or address a serious threat.

A borrower and lender may see the limited identity and lending status needed to manage their loan. They do not receive each other’s private payment details. Information disclosed to a payment or social platform may also be processed by that platform independently under its own policy. Any future ownership transfer of the store would require lawful handling, appropriate safeguards and notice where required; this is not permission to sell customer data for unrelated purposes.

07

Overseas processing

Our providers operate internationally, so information may be processed outside Australia, including in the United States, and in other countries used by their service infrastructure and support teams. We do not promise Australian-only hosting. Provider data centres, backups, sub-processors and support locations can differ and change; the linked provider notices explain their international operations. Ask Support if you need information about the current arrangements for your data.

Where Australian Privacy Principle 8 or another cross-border rule applies, we will take the steps that law requires before the relevant disclosure, including appropriate safeguards and accountability. This notice is not a request for you to waive those protections. We will update this description when a material change in our arrangements is identified.

08

Cookies, local storage and external content

We use first-party session cookies to keep you signed in, temporary browser-bound OAuth cookies to complete sign-in securely, and separate support/staff/transcript sessions where relevant. The main session normally lasts up to seven days; OAuth transaction cookies about ten minutes; temporary Discord-linking cookies about thirty minutes; and support/staff/transcript sessions up to eight hours. Signing out clears relevant sessions, and tokens may expire sooner or be invalidated.

Your browser stores shopping-bag product IDs and quantities locally so your bag survives a refresh. You can clear cookies and site storage through browser settings; doing so can sign you out or empty your bag. Blocking necessary cookies may prevent sign-in and checkout. The current storefront does not intentionally add advertising pixels or third-party behavioural analytics. If optional tracking is introduced, this policy and any legally required choice mechanism must be updated first.

External fonts (including Google Fonts), avatars, product media, payment pages and platform links can cause your browser to contact their hosts, which can receive network information. Their policies apply to their own processing. We do not treat a click on an external link as consent to unrelated marketing by us.

09

Tickets, transcripts and moderation records

Website tickets are available to the account holder and authorised staff. Discord tickets use channel permissions, but participants and authorised server roles can see the conversation while the channel exists. Closed Discord tickets may be archived as transcripts before the channel is removed. Deleting the channel does not delete the archived transcript or copies already held by participants or Discord.

Transcript pages require the configured participant or staff access checks. A transcript URL is not intended to make its contents public. Attachment availability can depend on the source platform. Internal notes and audit records are retained for case handling and accountability and are not automatically disclosed to other customers. You may request access to information about you; we may redact another person’s private information or withhold material only where justified by applicable law.

Warnings and reports may include alleged violations and evidence. We distinguish reports from confirmed findings and consider correction requests. Do not send sensitive personal information, identity documents, passwords or unrelated third-party details unless specifically needed and a suitable private method has been agreed.

10

Service messages and marketing

We may send order, licence, support, account and safety messages by website, email or Discord where necessary for the service or required by law. Ticket email notifications depend on your selected preference and the verified address available to the service. These messages are separate from promotions.

We will only send promotional emails or direct messages where there is valid marketing consent or another permission recognised by applicable law. A purchase alone is not our marketing opt-in. Promotional messages must identify the sender and provide a working, free unsubscribe route that does not require an account login. We will honour marketing unsubscribe requests within five working days, or sooner where required, and keep enough suppression information to avoid resubscribing you by mistake. Essential service messages may continue. Optional marketing must not be launched without a functioning consent record and unsubscribe method.

11

Security and incident handling

We use measures appropriate to the information and operational risk, including authenticated account access, staff permissions, protected session flows, access-controlled files, input checks and safeguards around stored credentials and messages. No online service can guarantee that loss, misuse or unauthorised access is impossible. Staff should access personal information only for authorised work.

If we identify an incident, we will assess and contain it, investigate affected information, take corrective steps and notify affected people and regulators where the applicable law requires. We will not conceal a legally notifiable breach simply because the store is small. If you suspect an account or data incident, contact Support promptly and avoid posting the information publicly.

12

Retention and deletion

We retain information for as long as reasonably needed to supply products and account access, manage active licences and loans, resolve support and payment disputes, prevent abuse, maintain necessary records and meet legal obligations. Account and entitlement records may need to remain while a paid licence is active. Order and financial records are kept for the period required by applicable tax and record-keeping law; many Australian tax records must be kept for at least five years, with longer periods possible in particular circumstances.

Ticket messages, transcripts, warnings and evidence are retained where needed for ongoing cases, repeat-issue handling, safety, disputes or legal obligations, and reviewed for deletion or de-identification when no longer needed. There is no promise that closing a ticket or deleting a Discord channel immediately erases its archive. Current licence audit history is trimmed to approximately ninety days, subject to necessary case preservation; other security and provider logs can have different retention periods.

When we delete live records, residual copies may remain in backups until their normal replacement cycle and may be retained where legally required. We restrict further use to the relevant retention purpose. Ask us to explain a retention decision rather than assuming a single fixed period applies to all records.

13

Access, correction, deletion and complaints

Start a privacy request · Request account/data deletion

You can view orders and licences in your account and ask Support for access to other personal information we hold about you, correction of inaccurate information, deletion or de-identification, or an explanation of a processing decision. You may also ask about withdrawing optional consent or other rights provided by a law that applies to you.

We will verify identity proportionately, generally using your linked account or order information. Do not send identity documents unless we explain why a less intrusive method is insufficient. A request is free to make. We will explain any lawful refusal, necessary redaction, retained record or reasonable charge permitted by law before imposing it. Deletion can prevent continued licence validation; we will explain that consequence and consider less disruptive options. Deleting a store record does not delete records independently held by Stripe, Discord or Roblox.

We aim to acknowledge privacy requests within two business days and respond within thirty calendar days, or within any shorter applicable legal period. If more time is lawfully needed, we will explain why. For complaints, tell us what happened and the outcome sought; we will investigate and provide a response. Where the Privacy Act applies, you may complain to the Office of the Australian Information Commissioner, generally after first giving us a reasonable opportunity to respond. Other applicable regulators and legal remedies remain available. Australian small-business exemptions and exceptions depend on the actual activities and circumstances; this policy does not claim registration with, or certification by, a privacy regulator.

14

Children and changes to this policy

Our store is not intended for people below the minimum age required by the linked platforms and applicable law. A parent or guardian should supervise a minor’s purchases and can contact us about personal information submitted by a child. We do not routinely collect a date of birth simply to browse the catalogue. Where we become aware information was obtained unlawfully, we will assess and take appropriate steps.

The version and effective date appear on this page. We will update it when our practices or legal obligations change and give additional notice of material changes where required. A new policy does not retrospectively authorise an incompatible use or replace consent that the law requires us to obtain separately.

Let’s work through it.

For an order issue, privacy request or question about these policies, start a conversation with the team.

Contact support ↗
← Marketplace Lukas’s Development · Built for your next idea. Your account ↗