Privacy policy

1.Who we are

StudioHQ is operated by My Homesteads LLC, a limited liability company registered in the State of Georgia, United States, based in Paulding County. In this policy, we, us and our mean My Homesteads LLC, and StudioHQ means the StudioHQ web application, its public pages, and the emails it sends.

My Homesteads LLC is the controller of the personal information described in this policy. To reach us about anything here, use the contact form and choose the closest topic.

2.The short version

• We collect what you and your team enter, plus the technical information the service needs to run and to stay secure.
• We do not sell or rent your personal information, and we do not use your content for behavioural advertising.
• We never ask for your Roblox password, Roblox session cookies or Roblox API keys, and you should never enter them. StudioHQ does not log into your Roblox account.
• Access to a studio or project is enforced by the database on every request, so a member only reaches the studios and projects they were added to.
• You can ask us to delete your account and its content, and you can edit or remove most of your data yourself at any time.

3.Information you give us

• Account details: your email address, your name, and the role assigned to your account.
• Profile details: display name, username, avatar, biography, specialties, experience level, developer type, preferred roles, notification preferences, and optionally a Roblox username (a label only, never verified) and portfolio links.
• Studio and project content: studio details, project briefs, development phases, tasks, milestones, checklists, game design documents and revisions, storyboard scenes, team and role records, assets and review notes, bug reports, QA test cases, release notes, community and marketing plans, budget and expense records, and any analytics figures you enter.
• Collaboration records: the members of your studios and projects, and invitations you send, which include the email address of the person invited.
• Uploads: files you attach as project assets or expense receipts, stored privately and reachable only through short-lived signed links that follow your project permissions.
• Public submissions: if you submit feedback on a public community page and mark it public, the title, description and any name you give are visible to visitors.
• Messages: the name, email address and message you send through the contact form.

4.Information created as you use the service

• Security and access records: sign-in events, approximate time, IP address, and browser or device information, kept to protect accounts and detect abuse.
• An audit log of administrative actions: who changed or removed what, and when.
• Usage events: which modules are opened and which actions are taken, in aggregate, so we can improve the product. These events are not used to build advertising profiles and are not shared with advertising networks.

5.Payment information

Paid subscriptions are processed by Base44 Payments, which is powered by Wix Payments. Your card number, expiry date and security code are entered on the payment provider's own hosted checkout page. We never receive or store your full card details.

We do receive and store a purchase record: the product purchased, the amount and currency, the payment status, transaction identifiers, and the email address used at checkout. We use it to give your account the right access and to keep accounting and tax records.

6.Roblox data we read

If your project records a Roblox universe ID, StudioHQ calls Roblox's public interfaces to fetch publicly available information about that game, such as its name, visits, playing counts and favourited counts, and shows it to your team.

This is public data about a game. We do not log into Roblox on your behalf, we do not access your Roblox account, and we do not collect Roblox credentials, Robux balances, or personal information about Roblox players.

7.How we use information

• To create and secure your account, sign you in, and keep you signed in.
• To provide the product: storing your studios and projects, showing records to the members you added, and enforcing the permissions and roles you set.
• To manage subscriptions, access levels, invoicing records and support.
• To send the emails the service sends: invitations, notifications, weekly task reminders if you have them switched on, and billing messages.
• To keep StudioHQ safe: investigating abuse reports, moderating public pages, and acting on content that endangers people, especially children.
• To protect the service technically: detecting misuse, preventing fraud, and maintaining availability.
• To improve the product: understanding which modules help teams and which do not.
• To meet legal, tax and accounting obligations, and to respond to lawful requests.

8.Legal bases for users in the EEA and UK

Where the General Data Protection Regulation or the UK GDPR applies to you, we rely on these legal bases: performance of a contract (providing StudioHQ to you), our legitimate interests (keeping the service secure, supporting you, and improving the product, balanced against your rights), your consent (optional profile fields and any optional emails you switch on, which you can withdraw at any time), and compliance with a legal obligation (tax and accounting records and lawful requests).

Our servers and our service providers are located mainly in the United States. Where personal information is transferred out of the EEA or the UK, we rely on appropriate safeguards such as standard contractual clauses with our processors.

9.Who can see your information

• Your team: the people you add to a studio or project, according to the access roles and roles you assign. You control who that is.
• StudioHQ administrators: the operators of StudioHQ can access data in the app for support, security and abuse handling. Administrative actions are recorded in the audit log.
• Service providers: the platform that hosts StudioHQ and provides the database, authentication, file storage and email delivery, the payment provider that processes subscriptions, the provider that powers the AI project assistant, and public data providers such as Roblox. They process information on our instructions and for the purposes described here.
• Authorities: where we are legally required, or where we believe in good faith that disclosure is necessary to protect someone from serious harm.
• A successor: if the business is sold or merged, information may transfer as part of it, and we will tell you before your information becomes subject to a different policy.

We do not sell or rent personal information, and we do not share it with advertising networks or data brokers.

10.The AI project assistant

The AI assistant drafts tasks, design document sections, and status summaries from the project context you give it. That project context is sent to a large language model provider to produce the draft, and the result is saved in your project so your team can review it.

Do not put other people’s personal information, credentials, or confidential third-party material into the assistant. We do not use your content to train our own models.

11.Emails you will receive

We send transactional email: studio and project invitations, notifications, weekly task reminders if you or your studio have them enabled, and billing messages about your subscription. You can change notification preferences in your profile. Billing and account-security messages about a paid subscription cannot be switched off while the subscription is active.

We do not send marketing email to people who have not asked for it, and every optional email you receive includes a way to stop receiving it.

12.Cookies and similar technologies

We use cookies and browser storage to keep you signed in, to remember your settings such as light or dark mode, and to count aggregate usage. Visitors in the EU, the EEA and the UK are asked for consent before aggregate usage counting is switched on, and can change that choice at any time. The cookie policy explains each category, the third parties involved, and how to control them.

13.How we protect information

• Access control is enforced per request by the database itself, so a member only reaches the studios and projects they were added to, and roles decide what they can change.
• Private uploads are stored privately and reached through short-lived signed links that follow project permissions.
• Administrators have the access they need to run and support the service, and their actions are recorded in an audit log.
• Information is encrypted in transit. No system is completely secure, so please use a strong, unique password and never send Roblox credentials to anyone, including us.
• If you think you have found a security problem, tell us through the contact form and mark it as a security issue.

14.How long we keep information

• Account, studio, project and content records: kept while your account is active, then deleted or turned into anonymous records when you ask us to close your account.
• Purchase and billing records: kept as long as tax and accounting law requires, which in the United States is generally seven years.
• Security and audit records: kept for a limited period, then deleted or anonymised.
• Backups: deleted on a rolling schedule, so a deleted item can persist for a short time in a backup before it ages out.
• Public submissions: kept until they are removed or you ask us to remove them.

15.Your rights and choices

You can edit your profile, change notification preferences, remove your own records, and leave a studio or project yourself. For anything you cannot do in the app, send us a request through the contact form and tell us the email address on your account.

• Access and copy: get a copy of the personal information we hold about you.
• Correction: have inaccurate information corrected.
• Deletion: ask us to delete your account and the content you own. Some records may be kept where the law requires it, such as billing records.
• Restriction and objection: ask us to stop or limit certain processing, including any processing based on consent, which you can withdraw at any time.
• Portability: receive your information in a structured, commonly used format.
• Complaint: complain to us first, and where the law allows it, to your local data protection authority.

We may need to verify that a request comes from the account holder before we act on it. We aim to answer within 30 days, and within 45 days for requests under United States state privacy laws.

16.United States state privacy rights

If you live in a state with a comprehensive consumer privacy law, for example California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon or Montana, you may have the right to know what personal information we collect and why, to request a copy, to have it corrected or deleted, to opt out of the sale or sharing of personal information and of targeted advertising, to limit the use of sensitive personal information, and not to be discriminated against for exercising those rights. You may use an authorised agent to make a request.

We do not sell personal information, we do not share it for targeted advertising, and we do not use sensitive personal information to infer characteristics about anyone. If you are not satisfied with our answer, you can appeal by replying to our decision through the contact form. Georgia, where we are based, does not currently have a comprehensive consumer privacy statute, but we apply this policy to everyone who uses StudioHQ.

17.Children and younger developers

StudioHQ is a working tool for game development teams and is not directed at children. You must be at least 13 years old to use it, and if you are under 18 you may only use StudioHQ with the involvement and permission of a parent or guardian.

We do not knowingly collect personal information from children under 13. If we learn that we have, we will delete it. A parent or guardian who believes a child under 13 has created an account or posted information can contact us and we will remove it.

Roblox is played by a very large number of children, so we ask developers to keep personal details out of public submissions and out of project content, and we ask studios not to require personal information from younger members.

18.Do Not Track and Global Privacy Control

We do not track you across other companies’ websites and we do not run behavioural advertising, so a browser Do Not Track signal does not change how we treat your information. Where a Global Privacy Control signal is sent, we honour it as a request not to sell or share personal information, which we do not do in any case.

19.Changes to this policy

If we change this policy we will update the date at the top of this page. If a change materially affects what we do with your information, we will tell you in the app or by email before it takes effect.

20.Contact us

For any question, request or complaint about privacy, use the contact form, choose the privacy topic, and include the email address on your StudioHQ account so we can find you. If you are in the EEA or the UK and are not satisfied with our response, you have the right to complain to your national data protection authority.