1. Who we are
CubiBase is a developer platform operated by TradingPlus Inc., 9450 SW Gemini Dr, PMB 49313, Beaverton, OR 97008-7105, United States. Privacy questions go to [email protected].
This draft describes the CubiBase marketing website at cubibase.com and the CubiBase service developers use through the Console and the APIs. It does not describe other products that TradingPlus Inc. may offer.
2. Scope
The draft covers personal information TradingPlus processes to run the website and the developer platform. It also explains customer application data, which is different. If a practice is not described here, do not assume it. Several operational facts are listed for counsel in the internal review notes and are intentionally left open.
3. Two kinds of information
Developer-account information is about you as a CubiBase customer: your email, password hash, session, projects, and how you use the Console. TradingPlus decides why that information is processed for the purpose of providing the platform.
Application data is the content you and your users store in a project database. That may include your end users’ names, messages, or other records. You decide what that database contains and which tables are exposed. For that data, the intended relationship is that you are the controller (or the equivalent under your local law) and TradingPlus processes it to provide the platform. A data processing addendum is not published and is not offered by this draft.
4. Developer account information
When you register, CubiBase stores the email address you submit and an Argon2id hash of your password. The password itself is not stored. The metadata database also stores project records, membership in projects you create, API key metadata, and audit events for actions such as creating a table or a key.
- Email verification and password reset use single-use tokens.
- A publishable API key is stored so the Data API can recognize the project. A secret key, if you create one, is shown once and stored only as a hash.
- The Data API does not authenticate with that secret key in the current engine.
5. Authentication and account security
The Console keeps the developer access token and refresh token in HTTP-only cookies named cb_access and cb_refresh. A CSRF cookie, cb_csrf, is not HTTP-only because the Console’s own requests need to read it. Refresh tokens rotate. These cookies are set by the Console, which is a separate application from this marketing website.
Application requests carry an end-user JWT. CubiBase verifies it and uses the subject as the user id for that transaction. CubiBase Auth can also create and authenticate your application’s users: their emails, Argon2id password hashes, session records, and MFA factors are stored in the auth schema of your project database, and auth events are logged. For that data you remain the controller, as described above. Alternatively you can verify tokens from your own identity provider. A development issuer can mint a token for a user id you choose while you are building, when that issuer is enabled.
6. Usage logs and technical information
API responses include a request id. The engine logs error events with that id. This draft does not state a log retention period, and it does not claim that logs are free of personal information. Confirm the log fields and retention before this policy is adopted.
Standard hosting data, such as IP address, user agent, and the URL requested, may be processed by the website host and by the API host to deliver the service and to investigate abuse. The exact fields depend on the host configuration and are part of the review.
7. Cookies and analytics
The marketing website loads Firebase Analytics, which uses Google Analytics 4, in production builds. The Firebase project is cubibase-firebase. The measurement ID is G-28D90H53PS. This is not the Firebase project used by the CubiBase Console. Google may receive pages viewed, referrer, approximate location derived from IP address, browser, device, and similar technical data, and may set its own cookies, including cookies named _ga. We use that measurement to see which public pages are used. This code does not configure Google advertising features or a remarketing audience.
Analytics starts about a second and a half after the page renders, then loads the Firebase script. It does not run during static prerender, and the local development server does not send hits unless VITE_FIREBASE_ANALYTICS=true. A consent banner is not implemented in this version. Counsel should decide whether visitors in the EEA, the UK, or other regions must opt in before analytics runs, and this draft should be updated to match that decision.
The marketing site does not set its own account cookies. Console session cookies are described in section 5. You can block cookies in your browser. If you block Google’s cookies, the page still loads. Blocking them may not stop every network request to Google.
8. Why information is processed
- To create and secure your developer account.
- To provision a project database and serve the Console and the Data API.
- To verify end-user tokens you configure and apply row policies.
- To measure use of the public website, as described above.
- To answer a message you send to [email protected].
- To investigate abuse and to enforce the acceptable use draft if those terms are adopted.
This draft does not rely on a named legal basis such as “legitimate interests” or “contract.” The basis depends on the law that applies, which counsel must confirm.
9. Application data
You choose the tables, columns, and rows. People described in those rows are usually your users, not CubiBase’s accounts. You are responsible for having a lawful basis to collect their information and for telling them how your application works. CubiBase’s generated REST API will return a row when the request satisfies the key, the token, the exposure flags, and any row policy on that table.
Do not put secrets you cannot rotate into a table you then expose. The publishable key is not a substitute for a careful schema.
10. Controller and processor
For developer-account information and marketing-site measurement, TradingPlus is acting for itself. For application data stored in a project database, the draft’s intended allocation is that the customer determines the purposes of that data and TradingPlus processes it to host the project. That allocation is not a signed data processing addendum. Do not cite this page as a DPA.
11. Service providers
Google LLC processes Firebase Analytics for the marketing website, as configured in this repository. Amazon Web Services hosts the marketing website’s static files (S3 and CloudFront), as recorded in this repository’s infrastructure notes. Those two statements are about the public website.
A subprocessor list for project databases, email delivery, and secret storage is not published. The engine can be configured with different adapters, so this page will not guess which vendors store customer databases. Counsel should approve a list before the policy names them.
12. Storage and international transfers
This draft does not promise that developer accounts, project databases, logs, or analytics stay in the United States or the European Union. Google and Amazon may process website traffic in more than one country. Where a project database runs is an operational fact that must be written down before this policy states a region.
13. Security measures in the product
The current engine hashes developer and end-user passwords with Argon2id, keeps Console session tokens in HTTP-only cookies, provisions a separate database per project, and creates request roles that cannot bypass row-level security. Tables created through CubiBase have row-level security enabled and forced. The Data API requires a publishable key and an end-user JWT. End-user refresh tokens rotate and are stored as hashes. The SQL editor accepts one read-only statement.
The public website is served over HTTPS. This draft does not claim encryption at rest, a penetration test, a bug-bounty program, or a compliance certification. Those items are open until there is something specific to cite.
14. Retention
Fixed retention periods are not published. Developer account records and project databases are kept while the account and project exist, subject to deletion behavior that still needs to be confirmed, including backups. Google’s analytics retention follows the Firebase and Google Analytics settings on the cubibase-firebase project. This draft does not restate a Google default as if TradingPlus had chosen it.
15. Deletion
A project owner can delete a project through the control API the Console uses. This draft does not promise that backups disappear at the same moment, because backup behavior has not been stated. A self-serve control to delete the developer account itself was not found in the engine. To ask for account deletion, email [email protected] from the address on the account. We will not invent a completion deadline on this page.
16. Privacy rights
Depending on where you live, you may have rights to access, correct, delete, or export personal information, or to appeal a decision. This draft does not name a statute, a response deadline, or an appeal process. Email [email protected] with the right you want to exercise and the email on the account. We may need to verify that you control the account. Requests about application data should go to the developer who runs that application. TradingPlus will assist that developer when a processing addendum, once it exists, requires it.
The product, as built, does not include a feature that sells personal information. This sentence is a description of the software, not a legal warranty under any particular state privacy law.
17. Children
CubiBase is a developer tool. It is not directed at children under 13, and we do not knowingly register a child under 13 as a developer. If you believe a child’s personal information was submitted as a developer account, email [email protected]. Application data is controlled by the customer. Do not build an application for children on CubiBase unless you are prepared to meet the laws that apply to you. The minimum age to hold a developer account is part of the terms draft and is not settled.
18. Changes
When a reviewed policy replaces this draft, the page will say so and will carry an effective date. Until that happens, this page stays marked as a draft. Continuing to use a future service after an adopted policy is posted is a question for the terms, not a trick hidden here.
19. Contact
TradingPlus Inc., 9450 SW Gemini Dr, PMB 49313, Beaverton, OR 97008-7105, United States. Email [email protected]. There is no published Data Protection Officer and no published EU or UK representative. Do not invent one from this page.
TradingPlus Inc., 9450 SW Gemini Dr, PMB 49313, Beaverton, OR 97008-7105, United States. [email protected].