RawBoard is operated by Joels Rozkalns, Krogsils, "Mārstaļi", Ķekava, Latvia. Contact: joelrosehill@gmail.com. Telephone: +371 20667726.
First-party service statistics
The administrator can compare account creation, service activity, plan selection and checkout journeys, verified subscription trials and paid invoices, AI usage and operating counters. This uses named RawBoard events, not visited website content, typed answers, screenshots or raw IP addresses. Optional activity and checkout rows are account-linked for up to 90 days and are included in export and deletion. Privacy & account offers an optional-usage control without removing product features. Daily aggregates and opaque deduplication keys expire after 400 days; necessary financial/security records follow their separate rules. The privacy notice explains purposes, coverage limits and rights. An implementation assessment records necessity and balancing safeguards; this addition does not close the existing provider, DPIA or operator-review dependencies.
Email verification and optional authenticator
New accounts are created only after a short-lived email code is verified. The email address and pending registration data are encrypted at rest; account passwords remain salted scrypt hashes. Resend delivers transactional codes. Each address has one verified account. Optional authenticator secrets use authenticated encryption, recovery codes are stored as keyed digests, and accepted time-step codes cannot replay. Enabling or disabling the factor revokes other sessions. Short-lived challenges and keyed rate counters expire automatically. Account deletion cascades active security records; backup and provider retention remain separate.
Public registration is available for the released service. Email activation creates an account with ordinary browsing access. AI tools and Keep active require an active trial or plan grant; an eligible new trial requires a plan subscription and payment card through Stripe. These measures improve account access protection but do not certify the risk assessment or resolve the outstanding AI transfer arrangements.
Anonymous reliability counters
Automatic browser diagnostics use fixed error categories, the RawBoard release and a broad browser engine. Reports contain no account/tab identifiers, IP addresses, page addresses, content, screenshots, credentials, cookies, AI messages or raw error strings. The ingestion endpoint does not authenticate the reporter or read request identity headers. Stored records are combined counts per UTC day, category, release and engine, with a 30-day expiry. There is no device identifier, persistent client queue or third-party telemetry service for these bug reports. Administrator access is restricted.
Connection metadata is necessarily processed in transit; it is not saved in the reporting store or transformed into an identifier. Global server budgets and memory-only client deduplication limit report floods without identifying people. The intended purpose is service reliability, not behaviour tracking. Identifiability must still be reassessed if additional fields, raw logs or external providers are introduced; hashing an identifier would not make it anonymous. See the privacy notice and GDPR recital 26. Other processing risks remain subject to ongoing review.
About this record
This is the public summary of RawBoard’s data-protection review, updated 9 October 2026, supplementing the 5 October 2026 register, record version 2026-10-09.6. The review examined application code, database structure, non-secret server settings and access controls. It did not inspect anyone’s website content, cookies, saved passwords or chat messages.
The operator’s private compliance file contains the processing register, retention schedule, security evidence, legitimate-interest assessments, provider register, impact assessment and procedures for privacy requests and incidents. Detailed security records and customer records are not published here.
Status: technical checks and provider research completed; unresolved AI safeguards and younger-user arrangements remain documented separately. The service is released and paid checkout is enabled following operator approval. This record is not a certification or a statement that every legal requirement has been fulfilled.
Current service and review status
The October review added an explicit browser sandbox, cleanup for inactive AI abuse records and a reviewed expiry schedule for legacy recovery copies. An isolated restore drill confirmed that deleted accounts stay deleted and profile IDs are not reused.
For an under-18 account, the adult parent or legal guardian must make a paid purchase using their own contact details. Declarations remain self-declarations. Withdrawal deadlines include the full final day and applicable non-working-day extensions; support can review additional rights and notices sent before a deadline.
The service is released and paid checkout is enabled following operator approval. This records the operator’s decision; it does not certify that outstanding AI transfer/privacy questions, guardian arrangements or provider safeguards have been resolved. A risk assessment can reach a no-go decision; it is not automatically an approval.
Trial and availability safeguards
Free-trial eligibility uses keyed verified-email, signed random device-marker and Stripe-provided payment-card fingerprint digests with a 180-day retention period. These pseudonymous claims can outlast account deletion to prevent immediate trial recycling and are retained separately during restores. School Wi-Fi is not a permanent one-account ban. No MAC address, hardware scan or advertising fingerprint is collected. A shared-device error can be reviewed through support; paid access and valid friend codes remain available. The Privacy policy gives details.
The October security review added bounded request and password work, response/decompression size limits, narrower inbound administration access, a worker-health watchdog and a dependency patch. Synthetic account-isolation, deletion/restoration, trial, billing and device-browsing checks were exercised. These controls do not certify the absence of all vulnerabilities or resolve provider-transfer and younger-user assessment questions.
What RawBoard handles
- Accounts
- Username, salted password hash, sign-in sessions, creation date, age group and agreement records. Registration does not ask for your birth date.
- Browser
- Saved tab addresses and titles; website cookies relayed and saved in an encrypted account profile; saved website credentials; and page context requested for AI. Websites execute and render on the device, where local storage and IndexedDB also remain. Ordinary typing, scrolling and animation happen on the device. Explicitly kept compatible tabs execute in isolated server browsers; their website sessions, available local/session storage and supported unsent form fields are handled on the server. Encrypted unsent-field checkpoints support recovery until the pin ends; managed recovery copies follow backup expiry. Draft checkpoints exclude password, card, hidden and verification-code inputs.
- Page AI
- Reviewed page context, your question, answers and recent conversation; token usage and estimated cost. Up to four relevant lesson images or diagrams can be included through the optional image-sharing checkbox in the same AI context-sharing prompt.
- Plans
- Trial and friend-code access, allowances, subscription and Stripe payment references. Purchases and withdrawals also need a name and confirmation email.
- Operations
- Limited security and diagnostic information, support/privacy requests, confirmation delivery status and recovery records.
Website content can contain information about other people. Only share content you are entitled to share. Do not use the AI helper for personal or sensitive information. Device games and websites you visit also handle data under their own policies.
Purpose and legal basis
Necessary account, browsing and subscription operations are mapped to performance of a valid service contract. Financial and consumer records are mapped to applicable legal obligations. Proportionate security, abuse prevention and recovery controls are mapped to assessed legitimate interests. Privacy requests are handled to meet data-protection obligations.
Optional processing that needs consent requires its own valid choice; agreeing to Terms or reviewing AI context is not a blanket privacy consent. The private register identifies where a basis still needs confirmation, including contracts involving minors and any unintended sensitive information in browsed pages. A purpose label does not authorize every kind of information someone might enter.
Retention and deletion
AI conversation history: 30 days. Managed database backups: 30 days. Account sign-in sessions normally expire after 7 days. Saved tabs, website state and credentials remain until removed or the account is deleted; making a tab inactive is not deletion. Encrypted AI website permissions remain until revoked or the account is deleted, and a changed AI notice requires a new choice.
Necessary payment, contract and withdrawal records have a separate supporting-record schedule, currently at least five years, subject to the applicable obligation and unresolved disputes. This is not the retention period for browser content. Provider-held data follows the provider’s applicable terms; RawBoard’s 30-day setting does not promise deletion at DeepSeek, Stripe or an email provider.
Account erasure removes active account and browser data while retaining only justified supporting records. A minimal erasure ledger protects supported restores from recreating deleted accounts. Reviewed older unmanaged files containing configuration or database recovery copies have an explicit 30-day expiry from their inventory date. Only unchanged listed copies can expire; altered files and holds need review. External copies, unclassified diagnostic records and mailbox retention still require separate operator review; they are not all covered by the automatic backup timer. Inactive AI rate-limit timestamps are also pruned after their budget/penalty windows.
Use Privacy & account to export account data, delete AI chats or request account deletion. Some requests, including full access, correction, restriction or a pending payment dispute, need support review. An export button does not replace those rights.
Providers and international processing
- RawBoard: the operator controls the service. The main server is declared to be in Latvia.
- DeepSeek: AI requests use its API. API-specific processing roles, retention/training conditions and safeguards for personal-data transfers still require confirmation. The intended AI sharing is limited to non-personal content. The main deployment uses the Redact text model running on RawBoard’s server, deterministic checks and optional account-specific website permissions instead of Qwen review; original lesson images and diagrams can be shared by enabling the optional checkbox in the same context-sharing prompt. Redaction and declarations cannot guarantee anonymity. Replacing the general local reviewer with a text detector changes residual privacy risk and requires renewed operator/DPIA review.
- Desert Ant Labs: supplies the Redact SDK and model. Inference runs on RawBoard’s server in Latvia. Its required licensing telemetry contains a random runtime-installation identifier, SDK/application information, call counts and limited runtime context; RawBoard does not supply customer IDs, prompts, page contents or answers. Its license describes the provider’s telemetry-controller role. The SDK/model runs within RawBoard’s infrastructure; it does not require customers to reach the operator’s private network or development environment.
- Stripe: hosted payments and subscription management. Stripe can act as a processor or a controller depending on the activity. The main server has live Stripe Billing configured; the operator has approved enabling live checkout. Public agreements alone do not prove the terms accepted on a particular account.
- Resend: the confirmation-email connection uses a verified sending domain in the Ireland region. Subscription and withdrawal test confirmations were delivered on 5 October 2026. Transport encryption is enforced. The signed DPA available in the account is incorporated through signup and includes Standard Contractual Clauses. Provider notices specify US storage, 30-day email/log retention on the current Free plan, and up to 90 days for remaining data after termination. Ireland controls sending, not storage. Contractual review is recorded separately from the operator’s final assessment decision.
- Other services: visited websites, device games and the operator’s support mailbox have their own processing and retention practices.
Public agreement references: Resend DPA, Stripe DPA, DeepSeek API terms. See Service providers & data sharing for more detail.
Copies of the public provider documents are kept in the private evidence file. They are marked separately from account-specific acceptance evidence; no missing agreement is treated as signed.
Security and access
Website profiles and saved credentials are encrypted at rest and separated by account. RawBoard passwords are salted hashes. Public domain connections use HTTPS. Protected routes check account ownership, and administrator tools are limited to their purpose.
This is not end-to-end encryption. The server operator controls the system and its keys, and some account and navigation metadata is stored separately from the encrypted profiles. Device execution does not make relayed requests or server-held cookies and saved passwords private from the operator. Each account and original website has a separate browser origin. Visited pages cannot access the RawBoard account origin. Device rendering uses a sandboxed frame; website JavaScript executes on the device. The new renderer requires its own isolation and compatibility tests; the earlier six-account test below covered the legacy server browser. Earlier synthetic tests verified six-account credential/session isolation, deletion and restoration safeguards for the legacy server browser. Selected server files use Windows file encryption with a separately stored recovery certificate; this is not whole-disk or boot-integrity protection and does not protect against a compromised running administrator. Privileged access and external recovery copies still require care.
The account-management screen does not show other users’ browsing history or saved passwords. Necessary maintenance and security access still require care, confidentiality and a documented reason.
Impact assessment and younger users
Screening decision: a formal data-protection impact assessment is required for the intended 14+ service. RawBoard is intended to be offered directly to younger users and handles highly personal browser state and credentials. Latvia’s Data State Inspectorate’s DPIA guidance and required-processing list informed this decision.
A working assessment has been prepared. It evaluates account separation, operator access, credential loss, unintended page data, AI transfers, young users, backups and privacy requests. It records residual risks and actions; it has not received final operator approval and does not authorize unresolved high-risk processing.
Registration records an age group and, where applicable, a guardian-permission declaration. These are self-declarations, not independent age or guardian verification. The assessment requires review of the younger-user flow and consultation proportionate to the audience. A checkbox does not remove the operator’s duties.
Review, requests and updates
Ongoing review must close provider and transfer questions, resolve recorded retention/access issues, assess younger-user safeguards and complete approval of the impact assessment. The service is already released; this record does not imply that registration or payments are waiting for a release date. Current free/trial processing is also subject to data-protection duties. Operator approval to enable checkout does not certify that the outstanding assessment actions are resolved.
Material changes to data, providers, AI features, retention or the audience trigger a new review. The private records identify the responsible operator and the evidence needed to close each action. Account export/deletion and a synthetic restoration were exercised; written procedures also cover manual privacy requests, confirmation bounces and security incidents. A synthetic test does not prove every real request or incident will be handled correctly.
For access, correction, deletion, restriction, portability, objections or a concern about this review, use Contact & legal notice. The Privacy policy explains your rights and complaint options.