Data and Account Policy

Effective date: 31 May 2026. Last updated: 10 August 2026.

This policy describes where BeginThings stores your data, what an "account" means for each product category, and how you can delete everything cleanly when you stop using us.

1. What counts as an account on BeginThings

BeginThings uses a verified Google identity or verified email-link sign-in instead of a site password. BeginRooms keeps a persistent server-side account record for authentication, trial and subscription state, and account-synced room and board content. Google sign-in supplies only the basic profile shown during authentication; BeginThings does not request Google Drive, Gmail or Calendar scopes.

2. Where data lives

Type of data	Where it lives	You control it via
Cat 1 free-tool inputs (e.g., your QR text, your invoice data)	Your browser memory only. Never sent to us.	Closing the tab. Clearing browser data.
BeginRooms room and board content	A responsive local browser copy and, for a signed-in account, the BeginThings account service over HTTPS for saving and cross-device sync. Account content is access-controlled but is not end-to-end encrypted.	In-product delete/export controls, local browser-data controls, and an account-deletion request.
Verified account profile (name, email, photo where supplied)	Persisted in the account service with session and product-access records.	Sign out, revoke Google access where used, and request account deletion subject to required records.
FormulaMapper release state	Downloads, new trials and subscriptions are paused. A compatible future build will keep workbook working data locally and send only the minimum verified-account, machine, device and entitlement identifiers required for licensing over HTTPS.	Device management, cancellation and deletion controls must pass release testing before the product opens.
Cat 4 purchase records (digital product orders)	Payment processor (Razorpay) and our order log.	Refund request. DPDPA/GDPR deletion request.
Cat 5 service engagement files (audit input URLs, scope docs)	Our email and storage for the duration of the engagement.	Deletion request after engagement closes.
Newsletter or lead-capture email	Stored in private server state outside the public document root and used only for the requested communication.	Unsubscribe link or email deletion request, subject to suppression records needed to honour opt-out.

3. Sign-in methods and Google scopes

BeginRooms supports Google Identity Services and a verified email-link flow. When Google is used, BeginThings requests only the default identity scopes:

openid - standard identity assertion.
email - your Google email address.
profile - your display name and profile picture.

We do not request any of the following: Google Drive, Gmail, Calendar, Contacts, Sheets, Docs, Photos, YouTube, or other sensitive scopes. If a future feature requires an extended scope, we will ask you explicitly and update this policy.

4. How to delete your data

If you used only Cat 1 free tools

There is nothing to delete on our side. Your data never left your device. Clear your browser cookies and localStorage for beginthings.com if you want a fresh state.

If you used BeginRooms

Export anything you want to keep using the in-product export control.
Delete rooms or boards you no longer need and sign out.
If you used Google, you may also revoke BeginThings at myaccount.google.com/permissions.
Email sourav@beginthings.com from the verified account address to request account and synced-content deletion, subject to security, backup and statutory-retention windows.
Clear local browser data to remove the local working copy from that device.

If you used FormulaMapper

The account-linked build is not currently released, so no new download, trial or subscription should exist. Before release, the compatible build must provide verified device-management, cancellation and deletion paths. Existing legacy-download questions should be sent to sourav@beginthings.com; the incompatible public binary is retired.

If you bought a Cat 4 digital product or engaged a Cat 5 service

Email sourav@beginthings.com with subject "Data deletion request". We will:

Delete project files and email correspondence (subject to mandatory retention for finished engagements).
Mark your record as deleted in our order log.
Retain only the minimum information required for tax and audit compliance (transaction date, amount, GSTIN if applicable, payment processor reference) for the legally mandated period.

5. Inactive accounts

BeginRooms uses persistent account, entitlement and synced-content records. Inactive-account retention and deletion are governed by operational, security, backup and statutory requirements; you may request deletion at any time. Revoking Google access stops that sign-in method but does not by itself erase required server records.

6. Account or data transfer

BeginThings does not support transferring a paid Cat 3 license, a Cat 4 download, or a Cat 5 engagement to another person or business entity. If a different person at the same organization needs access, please contact us and we will discuss reissue on a case-by-case basis.

7. Data export

You can export the following yourself, at any time, without contacting us:

Workspace 3D content: in-app "Export as .3dwb".
Free-tool outputs: download the generated file (the only output of the tool).
Cat 4 PDFs and templates: re-download from your order email (or request a re-send).

For order metadata or other records, send a portability request to sourav@beginthings.com.

8. Backups and accidental loss

BeginRooms keeps a local working copy and, for signed-in accounts, account-synced content on the service. Sync is not a substitute for an independent backup and is not end-to-end encrypted. Export important work regularly and store that export in a separate location. Free-tool working inputs remain local unless a specific tool clearly states that it uses a network service.

9. Security

BeginThings uses HTTPS for all pages, OAuth 2.0 (popup mode, no client secret) for Google sign-in, and a reputable payment processor (Razorpay) that we do not see card details from. We do not store any card or bank information. Our hosting (Hostinger) operates standard data-center security; we do not have additional certifications and recommend that highly regulated workflows be conducted on platforms with the required compliance attestations.

10. Changes to this policy

We may update this policy. The "Last updated" date at the top reflects the latest revision. Material changes will be announced on the homepage.

11. Contact

All data and account questions: sourav@beginthings.com. Operator: Sourav Mahapatra, India.