Privacy Notice
Effective October 29, 2026 · Version 2026-10-29-v1
Dayton, Ohio · support@graystontechnologies.com
1. Who is responsible and what this covers
Grayston Technologies LLC, based in Dayton, Ohio, operates Grayston Studios and is responsible for the personal information described here. Contact support@graystontechnologies.com for privacy requests, including if you cannot sign in. This notice covers the public Studio, private clubs, support, account linking and the separate SC features when enabled. SC participation and its external identity, geolocation and payout services are not currently open.
This notice describes information use, not a waiver of privacy rights. Accepting service terms or acknowledging this notice does not authorize marketing, a biometric scan or continuous device-location collection. Any required feature-specific notice and consent must appear before that collection begins.
2. Information, sources and purposes
Account information comes from you and our authentication service: email, account identifier, player name, display name, optional biography, 21+ attestation, authentication and recovery status, and policy versions with acknowledgment times. We use it to create and protect accounts, communicate about the service, administer age restrictions and record agreements. Authentication is handled by Supabase; the Studio application does not store plaintext passwords.
Game and account records are generated by your use: inputs, accepted entries, results, receipts, G Bit and P Bit ledgers, eligible SC records, inventory, cosmetics, loadouts, limits, breaks and account restrictions. Club records include membership, role, invitations, internal distributions, settings, contest history and messages you send. These records support gameplay, settlement, fraud detection, recovery, moderation and disputes.
Technical information may include IP address, browser/device characteristics, session identifiers, timestamps, request errors and security events processed by our application and hosting/authentication providers. We use it for service delivery, access control, troubleshooting and abuse prevention. IP-derived information alone is not accepted as precise-location proof for SC.
Support and business inquiries include the information you send, contact details, issue history and our responses. Optional purchases, when enabled, create order, amount, status, refund and provider-reference records. Payment credentials are handled through the applicable payment service; do not put them in a support message. We use transaction records for delivery, reconciliation, disputes and legally required accounting.
3. Separate SC verification and sensitive information
An enabled SC service may require identity and age checks, residence, sanctions screening, unique-person and fraud checks, current location, a verified prize destination and tax information. Before collection, we must identify the actual provider, the information requested, the purpose, relevant retention and available choices. No vendor name in a comparison or roadmap means that provider is currently collecting your information.
A supported provider may collect identification images, a selfie or biometric information where lawful and separately authorized. The Studio integration is designed to retain normalized decisions and provider references rather than raw identity documents or biometric templates. Provider-held material has its own disclosed handling requirements. Biometric collection cannot begin merely because you accepted general terms; required written notice, consent and a destruction schedule must be in place first.
Location verification, when enabled, may use permitted device signals and location-integrity checks while you request or use SC. Browser permission is one technical step, not proof of eligibility or permission for unrelated uses. Location can be rechecked during participation. You may deny or revoke device permission, but SC may then be unavailable. Free-play browsing does not require an SC location check. We do not use SC identity or precise-location evidence for advertising.
4. Public profiles, clubs and shared games
Your player name, chosen display name, optional biography, sigil, visible customization, reputation, rounds played, Studio mark and join month may appear on your public profile. Profiles are public by default; Account lets you make your profile private and adjust available standings visibility. Your email and private account ledger are not shown on the public profile. A private profile may still contribute anonymously to aggregate clan totals.
A private club is not an anonymous service. Other members see the identity and game/chat activity needed to participate. Authorized club operators and agents can see the membership, roles, balances and activity required by their in-product permissions. Do not post private identification or payment information in club chat. Restricting a public profile does not erase a message or an already accepted shared-game record.
RicoPay and supported shared games use your Studios account, restrictions, customization and the applicable game wallet. Authoritative inputs, outcomes and replays support recovery and disputes. Linking a historical account requires proof of control; matching email addresses alone do not link accounts, and historical Roll Bucks do not become G Bits. A separate external service you choose to visit may have its own privacy notice.
5. Providers and other disclosures
Current infrastructure includes OpenAI Sites for web hosting, Supabase for authentication/database/server processing, Resend for configured transactional email, and Render for the integrated RicoPay game server. Necessary support notifications may include the account identifier, contact email and ticket text. Providers receive information needed for the service they perform and applicable security or legal purposes. Additional payment, identity, location or prize services must be disclosed before activation.
Information may also be disclosed to authorized advisers or authorities when legally required, to investigate fraud or protect rights and safety, or as part of a lawful business transfer with appropriate confidentiality and notice. We do not give a club operator access to unrelated public SC verification documents or another club’s private records through ordinary club permissions.
The current Studio does not operate a targeted-advertising program or sell personal information for monetary payment. Marketing is off by default; service and security messages are separate from optional marketing. We do not infer consent to marketing from gameplay or a privacy request. Any future change involving sale, advertising-related sharing or a materially different purpose requires the applicable notice, choice and consent before it begins.
6. Cookies, device storage and processing locations
Authentication/session storage keeps you signed in and protects account access. Device storage also remembers choices such as sound, display settings, public currency and saved game favorites. Favorites in the SC discovery page are stored on that device. Clearing local storage may reset preferences or interrupt request recovery; it does not erase server receipts or account balances.
Current game preferences do not require advertising cookies. You can control cookies and site permissions in your browser, though some account functions may stop working. Where applicable, we honor legally required opt-out signals for processing to which they apply. Service-provider processing may occur in the United States or other places where those providers operate. Contact us for relevant provider/location information; we do not claim that every record remains solely in Ohio.
7. Retention and deletion
We determine retention by the purpose of a record, account status, accepted-game or payment obligations, security needs, disputes and applicable legal requirements. Account/profile information is used while your account is active; closure hides the public profile and restricts access. Accepted ledger, settlement, consent, tax or fraud evidence may need to remain after closure. Support and technical records are kept only while reasonably needed for the issue, security or an applicable obligation. A legal hold can extend an otherwise applicable period.
Account closure is not an instant erasure of all records, and the current application does not promise a universal automated deletion deadline. On a verified request, we determine which records can be deleted or deidentified, which must be retained and why, and communicate the decision under applicable law. Operational and backup copies may follow different removal cycles. Historical photo uploads are private and are no longer accepted or displayed; contact us to request review and deletion of a specific legacy upload.
Before any biometric or additional sensitive-verification collection is enabled, its specific retention and destruction requirements must be disclosed and implemented. General security or fraud language does not authorize indefinite retention or reuse for an unrelated purpose.
8. Access, correction, deletion and other choices
Account tools allow supported profile changes, export, visibility choices, breaks and closure. You can also email support@graystontechnologies.com to request access, correction, deletion, a portable copy, information about disclosure, or review of a privacy decision. A signed-in account is not required to make a request. Identify the account and requested action; do not send identification documents, passwords or financial credentials by ordinary email.
Depending on applicable law, you may have additional rights concerning sale/sharing, targeted advertising, sensitive-data use, certain automated decisions, authorized agents and appeals. We verify identity and authority proportionately, provide a secure verification route when needed, and respond within the applicable legal period, explaining any permitted extension or refusal. You can appeal by emailing the same address with “Privacy appeal” and the request reference and may complain to the appropriate privacy or consumer-protection authority. We do not retaliate for exercising a lawful privacy right.
We use automated controls to identify eligibility, abuse and transaction risks. A denial may also result from missing or expired evidence. Contact support to request review or correct an error. Review cannot authorize play in a prohibited location or override mandatory eligibility requirements.
9. Security and age restrictions
We use access restrictions, authentication, separate roles, protected records and transport security to reduce risk. No service can guarantee absolute security. Do not share passwords or send sensitive documents through ordinary support or club chat. If we identify a reportable breach, we follow applicable investigation and notification requirements.
The service is for adults 21 and older and is not directed to children. If you believe a minor has supplied information or created an account, contact support so we can investigate, restrict access and handle the information as required. An age gate does not remove obligations that apply if we learn that a child’s information was collected.
10. Updates and contact
This notice has a published version and effective date. Material changes will be identified and, when required, presented for acknowledgment or separate consent before new processing. A general update does not retroactively authorize an incompatible use of previously collected information.
Privacy contact: support@graystontechnologies.com. Operator: Grayston Technologies LLC, Dayton, Ohio, United States. Signed-in users may also use Studio Support. No government identifier, password, precise coordinates or full payment details are needed in the first message.
