Privacy Policy

Overview

Root Record Software Systems (“we,” “our”) provides Root Record websites and Root Record software, including Business Manager by RootRecord, Weather Manager, Kilauea Alerts, Account Hub, Token Manager, Root Goals, Roots Idle Farmer, and RootMC, plus account, billing, Discord linking, and Roots where those features are turned on.

On your device. Some product data stays on the device until you export it, enable sync, notifications, backup, or another feature that sends it to our systems. We do not use an on-device database for advertising.

On our systems. Signed-in products may store workspace, weather, alerts, goals, farms progress, token-tool state you choose to save, earn or Roots records, or similar operational data when you use online features.

On the public site. www.rootrecord.cloud is a public site. Reading it does not require an account. Pages may request public status, operations, and geology feeds. A missing reading stays missing. The site does not publish host names, private routes, or a finer location than Hawaiʻi and the Mainland Server.

Data we collect

• Account data. Where you create an account (email, a social sign-in, or a username and password), we store identifiers and, where you use a password, a hash of that password. A session cookie may keep you signed in. If you choose a key-storage preference in settings, we store that preference.
• Payment and billing data. Payments are processed by our payment provider. We do not store your full card number or card verification value. We store subscription status and billing references from the provider so we can grant access and show your plan. Subscription data for a lapsed account is kept for one year after the cycle ends, then removed. The provider’s privacy policy applies to payment data they process.
• Product and workspace data. Depending on the app, this can include business records you enter (time, clients, money, inventory, schedules, work logs), saved weather locations, notification registration, alert preferences, goals, farms progress, and similar rows needed to run the feature you turned on.
• Connected readings. If you connect a device or service (for example solar or power statistics, or system metrics) we store what that connection sends and show it in the dashboards you use. If you turn on a public reading or a public dashboard, what you choose to share there can be seen by anyone with the link or the public page.
• Public feeds. Status, weather, earthquake, and volcano pages use public sources and our own public readings. Kilauea Alerts presents that kind of information. It is not a government service.
• Apps calling our servers. When you sign in, check a subscription, sync, earn Roots, play Root Farms, or use optional online backup, an app contacts our services over a secure connection. We process the account identity, subscription state, usage signals, and encrypted backup copies where you enable backup.
• Discord linking. If you connect Discord, we store your Discord user id and username or display name, link them to your account, and may assign a role in the Root Record Discord server (for example a verified role). Discord handles the sign-in. We do not receive your Discord password. You can unlink where the account or verification screen offers it.
• Roots and app activity. We may record per-app usage signals — earn totals, last activity, saved locations, push registration, or workspace rows — to show which products have used your account and to operate Roots.
• Photo submissions. If you submit a photo, we collect the image and the details you provide (caption, time, and your account identifier). Photos are reviewed before publication. We may reject or remove content that violates the Terms or safety rules.
• RootMC. Governance and play records may include a Minecraft username, a Discord user id, vote choice, and calculated vote weight. Public proposal pages show the proposal and aggregated results, not private account email.
• Wallet and public-network tools. Where a Root Record tool runs in the browser or on your device and asks a wallet to sign, private keys are not sent to us. A referral code in a link may be stored only in that browser. Files you upload to a public network such as IPFS can be retrieved by anyone who has the address. Review every signature in the wallet before you approve it.
• Messages you send us. Email to agents@rootrecord.cloud, in-app feedback, and project requests include whatever you write, plus the address you send from.
• Server logs. Our servers may log IP address, path, and time for operation and security. The public marketing pages do not run a third-party advertising tag.
• Affiliate redirect pages. If you use an Amazon or similar affiliate redirect we operate, we may log a visitor id, IP address, account identifier if you are signed in, the referring page, the destination, and whether the redirect completed. The destination has its own privacy policy.

How we use it

We use data to provide the apps, accounts, dashboards, alerts, Roots, and custom work you asked for; to keep the Services secure and available; to bill for paid plans; and to improve our own services. We do not sell your personal information.

For content you upload, the Terms of Service describe access for moderation, support, SI report generation where that feature exists, and compliance. Controls in a product decide who else can see that content, where those controls exist.

SI report data and our own models

When you or the platform generates an SI report on an online service, we may send the relevant inputs to an SI provider to produce the report. We may save input and output pairs on our systems and use them to create, train, and improve our own models. We do not sell that data. We do not use it to train a third party’s commercial model for that third party’s own product. The Terms are the contractual permission for this use.

SI-assisted development is also how Root Record builds software. That work uses project materials a customer provides for a job, under the scope of that job. It is separate from training on your app content unless you use an online SI feature that says it stores inputs and outputs.

Sharing

We do not sell your personal information. We share data only as needed: with hosting and database providers that run the Services; with our payment provider for payments; with identity providers when you use those sign-in options; with Discord when you link an account; with app stores for distribution and purchase records they already hold; and with service providers for a feature you use. Each third party’s policy applies to what they process. We may disclose data when the law requires it, or to protect the Services, our users, or others from harm.

Public pages and public dashboards you enable are visible to the people who can open them. Aggregated status counts are public when the feed returns them.

Affiliate links

Some links, including links to Amazon, are affiliate links. A click may pass through our redirect before the external site opens. We log those visits as described above. If you make a qualifying purchase, we may earn a commission. See the Terms.

Cookies

• Session cookie. Where an account sign-in is offered, a session cookie keeps you signed in. It ends when you sign out, close the browser, or after inactivity, depending on the screen.
• Public site. Reading www.rootrecord.cloud does not require a tracking cookie, and these pages do not load an advertising tag. A browser may still store ordinary site files.
• Older visitor analytics. Earlier rootrecord.info operations used a first-party visitor cookie, about one year, HttpOnly, for traffic counts, plus UTM parameters for campaign attribution. If a signed-in product or redirect still sets that cookie, it is first-party, not an ad profile. Clearing cookies resets it.

Retention

We keep account, product, and log data as long as needed to run the service and to meet operational or legal duties. Subscription data for a lapsed account is stored for one year after the billing cycle ends, then removed. Files on your devices stay under your control until you delete them.

Approved photos may stay up until you delete the account, ask for deletion, or we remove them. Rejected submissions may be kept for a limited time for abuse prevention and a moderation record.

Billing records needed for accounting, tax, fraud prevention, and disputes may be kept after other account data is deleted. Server logs may persist for a short period. Deleted data may remain in backups until those backups rotate, typically within 30 days.

Security

We use ordinary safeguards for services we host: hashed passwords, secure connections, and access control. No method of transmission or storage is perfect. The public site describes the boundary in plain language on Security. It does not publish a security score, a host name, or a private endpoint.

Operations may be power-managed. A planned window, when one exists, is the service notice on this site, not a standing claim that the system is down every night.

Your choices

• Account. Manage sign-in, plan, and linked apps from the account screens where they are offered, including Account on this site when sign-in is open.
• Download. Where a profile offers it, download a copy of your account data before you delete it.
• Delete some data and keep the account. Use the data deletion page. We aim to finish a verified request within 30 days.
• Delete the account. Where the product offers permanent deletion, that action removes the account and associated online data. It may require your password. It is irreversible. Backups may still hold copies until they rotate.
• Apps. Turn off optional online features, sign out, or uninstall. Export or back up a local database before you remove an app if you need a copy.
• Discord and photos. Unlink Discord where the screen allows it. Ask us to remove a photo through data deletion or email.
• Cookies. Clear or block cookies in the browser. Blocking the session cookie means the site cannot keep you signed in.

Children

The Services are not directed at children under the age shown at sign-up. If you believe we have account data for a child who should not have an account, write to us and we will delete it.

Changes

We may update this policy. The “Last updated” date will change. Continued use after the change means you accept the updated policy, unless law requires a different process.

Contact

Privacy questions and deletion requests: agents@rootrecord.cloud. The agreement for use of the Services is the Terms of Service.