Archetric — Privacy Policy

Archetric™ is a product of Big Think Labs, LLC. Status: Published for launch; not legal advice Version: 1.12 · 2026-09-28 · effective 2026-09-07

This Policy is published so that the Service can be bought and used, and nothing in it is legal advice. Where a fact or a term is still to be settled, the sentence it affects is written in its safest form rather than left with a blank, and the open item is kept on our own list, which is not part of this Policy. You can ask us for that list using the contact details in Section 14.

Changelog

| Version | Date | What changed | | --- | --- | --- | | 1.12 | 2026-09-28 | No term changed. The note at the top now says that where a fact or a term is still to be settled, the sentence it affects is written in its safest form, and that you can ask us for our list of open items. Section 4 now says in this Policy itself that the terms for our account with the artificial intelligence (AI) platform behind the assistive features have not yet been confirmed, so this Policy makes no claim about how long that platform keeps your text or whether it may use it to train its models. The entries in this history are rewritten in plainer words. The effective date does not move: no category collected, use, sharing route, retention period, or right moved. | | 1.11 | 2026-09-28 | No term changed. Abbreviations are spelled out the first time they appear, for example application programming interface (API), General Data Protection Regulation (GDPR) and Open Authorization (OAuth), and "US" now reads "United States". The page on our website now shows this Policy only: it no longer shows the list of open items we keep for our own record, which was never part of this Policy. The effective date does not move: no category collected, use, sharing route, retention period, or right moved. | | 1.10 | 2026-09-25 | The personal canvas is paused. Sections 4, 5 and 8 no longer describe the assistive feature that read a starting paragraph into cards, and say "an individual's canvas" where they said "personal canvas". | | 1.9 | 2026-09-25 | No term changed. Section 14 points you to the contact details published on the contact page at archetric.com rather than naming an address, and the email address shown on that page changed to hello@archetric.com. At the time of this change, that address could not yet receive mail, because no mail service had been set up for it. The effective date does not move: no category collected, use, sharing route, retention period, or right moved. | | 1.8 | 2026-09-20 | Section 2 describes the contact form in the public directory of certified partners before it passes on any message. It names every field the form asks for, says the form passes your message to that partner so they can answer you, and says no part of the message is stored. The one thing stored is a count of attempts, per listing, per day, against a one-way hash of the network address a message came from, which cannot be traced back to a person. It also says a partner publishes their listing text on purpose, and that no address and no telephone number of theirs appears on any public page. Section 5 says the message has no retention period because it is not stored, and the count is deleted 30 days after the day it covers. No other category, use, sharing route, retention period, right or date of effect moved, and the effective date stays 2026-09-07. | | 1.7 | 2026-09-19 | Section 2 describes the certified partner program's application form before it collects anything. It names every field the form stores and why, says the record is held against your account rather than an address, that you need an account to apply, and that we do not read a draft. Section 5 says how long it is kept: a live application while it is live, a withdrawn or declined one for 12 months, and one you delete yourself is deleted at once, together with the record of any decision about it. No other category, use, sharing route, retention period, right or date of effect moved, and the effective date stays 2026-09-07. | | 1.6 | 2026-09-19 | Renamed to Archetric; no term changed. The Service is now called Archetric, at archetric.com, and is operated by Big Think Labs, LLC, as it was in every version from 1.0. Section 1 says the Service was formerly offered under the name Modular Business and at the old domain, and that this Policy still applies to information given to it then. Section 14 points to the contact page at archetric.com rather than the old domain; the mailing address is unchanged. Not one category collected, use, sharing route, retention period, right, or date of effect moved, and the effective date stays 2026-09-07. | | 1.5 | 2026-09-06 | Section 4 describes the assistive features, which ask an AI model to answer on our own account rather than on yours, including a new one that read the starting paragraph of a personal canvas into cards. It says the platform is a setting, with Anthropic's Claude as the default, and narrows the neighboring sentence about AI vendors to agent work so the two agree. Section 8.4 says that paragraph is stored with the canvas and its text reaches the platform when you ask for the reading. No claim is made about what that platform keeps or trains on. | | 1.4 | 2026-09-06 | Section 4 says, for the first time, what a share link carries, and it now carries less. A share link carries the shape of a canvas (its departments, sections, seats and wiring, under the names you gave them) and no longer carries your numbers, the people holding your seats, your providers, your notes, or anything else you typed about a seat. What a link carries sits in the part of the web address (uniform resource locator, or URL) that never reaches our servers or anybody else's. A link you created before this change still carries the whole canvas, because a link already sent cannot be changed. | | 1.3 | 2026-09-06 | Sections 4, 5 and 8.2 now state only what is true today about the house AI provider used for a trial: which provider it is, that the content of a trial run goes to it to produce the run's result, that what it keeps and what it may use it for are governed by that provider's own published terms, and what we keep. Section 8.2 names the published document and the date we read it (Anthropic's Commercial Terms of Service, effective June 17, 2025, read 2026-09-06) for the one thing those terms settle, which is training. It also says that we hold no separate arrangement with that provider about how long the content of a request is kept, so this Policy does not say how long it is kept, and that we will say so if that changes. The earlier promise to state those terms here later is removed. The Terms of Service carries the matching change at Section 12.5(c). | | 1.2 | 2026-09-05 | Four sentences in Sections 4, 5 and 8.2 that described what the house AI provider does with the content of a trial run are replaced by what we can actually state, because those descriptions had not been confirmed with the provider. Each now names the provider, says the content reaches it to serve the request, and says that provider's API terms for our account govern. This Policy no longer refers to a legal review. The Terms of Service carries the matching change at Section 12.5(c). | | 1.1 | 2026-09-05 | Section 3 describes the anonymous visitor identifier used before you have an account, before it went into use. It lists what is collected, names the finding summary, capped at 140 characters, as the one field that could carry your own words, and names where it goes: Big Think HQ, a Big Think Labs system, not an outside vendor. It claims no switch to turn this off, because none exists: clearing or blocking local storage is the control that works. Section 9's question about cookies is answered in Section 3. | | 0.1 | 2026-09-04 | First draft. | | 0.2 | 2026-09-04 | Adds Section 8 (Sponsored Accounts, the Trial, Gate Participants, and the Brain), the matching collection and sharing entries in Sections 2 and 4, and a retention paragraph in Section 5; renumbers former Sections 8–13 as 9–14. | | 1.0 | 2026-09-05 | Published for launch. The company is named as Big Think Labs, LLC. The trial's figures (50 runs, 14 days) are settled. Section 12 states plainly where the Service is offered from, in place of a placeholder about the General Data Protection Regulation (GDPR). Each sentence that depended on something not yet settled is written in its safest form. | | 1.0, amended | 2026-09-05 | The mailing address is added to Section 14; no other change. |


1. Who We Are

This Privacy Policy explains how Big Think Labs, LLC, a North Carolina limited liability company operating Archetric™ (archetric.com), collects, uses, and shares information when you use the Service. Big Think Labs, LLC is a small United States company based in North Carolina, founded and operated by Craig Mathews. Archetric is the product; Big Think Labs, LLC is the company that holds your information. This Policy should be read alongside our Terms of Service.

The Service's former name. The Service was formerly offered under the name Modular Business and at modularbusiness.co, and this Policy continues to apply to it under either name, including to information given to it then.

2. Information We Collect

Account information. Your email address and any other information you provide when creating an account.

Canvases and business models. The departments, seats, workflows, and configurations you build to model your business, whether saved locally in your browser (free tier without an account) or saved to our servers (any account tier).

Runs. Reports submitted by agents and people through our ingest API: counts, costs, timestamps, and a short free-text description. Free-text is automatically processed to redact detectable email addresses and phone numbers before storage, but this automated process is not guaranteed to catch every instance of personal information, so we ask you and your agents not to submit personal or regulated data in free-text fields.

Connection identifiers. When you connect a third-party application, our connector provider holds the Open Authorization (OAuth) credentials for that connection. We store only the connection identifier issued by the connector provider, not the underlying credentials, tokens, or the content of your connected application beyond what an agent or integration explicitly reports as a run.

Sponsored canvases. Where an organization pays for an individual's canvas, we record who the payer is, which seats the payer holds, and which work area those seats sit in, so that the payer's access can be limited to them. We do not label the rest of the canvas as belonging to the payer and we do not disclose it to the payer. See Section 8.

The brain index. If you point the Service at a folder of your own documents, we store an index of that folder — enough to find and cite a document when an agent or a person asks a question of it — together with the run records of work that read from it. We do not store a copy of the documents themselves; they stay in your storage and are read through the connection you own.

Persons named on a gate. A gate may name a person who is consulted or whose approval is required. Where that person does not hold an account with us, we store the name and address you supply for them, the message sent through your own connected accounts, the answer, and the date. See Section 8.

Usage analytics, and the visitor identifier that exists before an account does. The first time you visit one of our sites we store an anonymous identifier — a random value, in your browser's local storage — whether or not you ever create an account. We use it to tell one visit from another and to understand how people move through our sites. We do not use third-party advertising trackers, and we do not sell your data to ad networks or data brokers.

What we collect with it. The page path you viewed; the host of the site that referred you (for example google.com), never the full referring address; campaign tags (utm_source, utm_medium, utm_campaign, utm_content), captured once, on your first visit; and product events by name, from a closed list — for example an account created, a canvas saved, a first run, a trial started, a subscription started or ended. Each event carries at most a few fields drawn from a fixed vocabulary: a department from our own eleven, or Alliances, a severity of low, medium or high, an outcome of completed, blocked or abandoned, a plan name.

What we do not collect, and the one exception we would rather name than have you find. No canvas content, no documents, no journal text, no run inputs or outputs, and no name you typed. The exception is a finding summary: when the product emits a finding, the event may carry a short description of it, capped at 140 characters, one line, no links. That field is composed rather than chosen from a list, so it is the only one that could contain words drawn from your own business. Every other field is a fixed value from a list we publish.

Where it goes. To Big Think HQ, our own system, operated by Big Think Labs — not to a third-party analytics or advertising vendor. Events are forwarded from our own server rather than sent from your browser to anyone else.

Linking to your account. If you create an account, we link that identifier to it, so what you did before signing up is joined to your account rather than left as a separate anonymous record.

Your control over it, stated as what exists rather than what is planned. The identifier lives in your browser's local storage. Clearing your site data removes it and you are seen as a new visitor; blocking local storage for our sites prevents one being stored at all, and the product keeps working — it simply cannot tell a returning visitor from a new one. There is no switch inside the product today that turns this off. If we add one, this Policy will say so before it is needed.

A partner program application. If you apply to the certified partner program at /partners/apply, we store the answers you give on that form: which path you applied for, the kinds of business you work with, what you do today and who for, two or three engagements you describe, why you are applying, optionally how you heard about the program, and, for the Author path, a link to something you have written or built. We store it against your account, not against your email address, so that you can open it, change it while it is still a draft, withdraw it, or delete it yourself at any time. An application cannot be made without an account, and we do not read a draft: nothing reaches us until you submit it. The form asks you not to name a client, and we ask the same here. Purpose: to decide on your application and to write to you about it. It is not used for marketing, and it is neither sold nor shared. Retention is in Section 5.

A message you send a partner through the directory. If you write to a certified partner from their page in the directory at /partners/directory, the form asks for four things: your name, your email address, your message, and a tick of a consent box saying you understand where the first three go. It also carries one hidden field that no person sees and no person fills in, which is how an automated submission is refused. Purpose, at the point of collection: to pass your message to that partner so they can answer you. Your name, your address and your message go into one email, sent from us to the address that partner gave us for this, with your address written in the body of that mail rather than in a header, so the partner can read it and reply to you directly. No part of what you write is stored here. There is no place in our database for the body of a message or for a sender's address, so once the mail has gone we hold nothing you typed. What we do store, and only to limit how many messages one sender may send in a day and to deal with abuse, is a count: one row for each partner listing, each sender, and each day, holding how many attempts that sender made. The sender is recorded as a one-way hash of the network address the message arrived from, combined with a secret held on our server and with that day's date, so the row cannot be read back to an address or to a person, and a row from yesterday cannot be matched against one from today. Retention for both is in Section 5. Two things about the partner's side of that page, because a reader would want to know them: the listing you are reading is text that partner wrote and published on purpose, being their name, where they work, the kinds of business they work with, one paragraph, and if they want one a public line about getting in touch; and no address and no telephone number of theirs appears on any public page, which is why there is a form at all. The address a relayed message is sent on to is never published.

Payment information. Billing is handled entirely by Stripe. We do not store your full payment card number; we retain only what Stripe provides for account and subscription administration (for example, subscription status and the last four digits of a card).

Support and correspondence. If you contact us, we retain that correspondence to respond and to improve the Service.

3. How We Use Information

We use the information above to: (a) provide, operate, and maintain the Service; (b) process payments and manage subscriptions through Stripe; (c) measure and display run outcomes and cost/time savings; (d) maintain and improve the connector integration and ingest API; (e) provide customer support; (f) detect, prevent, and investigate fraud, abuse, or security incidents; (g) comply with legal obligations; and (h) with your consent, communicate product updates. We do not use your business content (canvases, run detail, connected-application data) to train models for other customers or third parties.

4. How We Share Information

We share information only as follows:

  • Stripe, to process payments and manage billing.
  • Supabase, as our hosting and database infrastructure provider, which stores account, canvas, and run data on our behalf under its own security commitments.
  • The connector provider, which holds OAuth credentials for your connected third-party applications and brokers those connections; it does not receive your canvases or run content beyond what is needed to establish and refresh a connection.
  • The AI vendor or platform you choose for each agent seat receives only what that agent, running on your chosen platform, is configured by you to send it. We do not route your business data through AI vendors on your behalf for agent work; the Service receives run reports back from your agents, not the other way around. The assistive features in the next bullet are the exception, and each of them runs only when you ask for it.
  • The AI platform behind the assistive features. Two features ask a model to answer on our own account rather than on yours: suggesting the shape of a business from a description you type, and finishing a process on a card. When you use one of them, the text you supplied for it is sent to the AI platform configured for the Service — Anthropic's Claude by default; the platform is a setting rather than a fixture — to answer that one request. What that platform keeps of it, and what it may use it for, are governed by that platform's own published terms. The terms that apply to our account for this use have not yet been confirmed with that platform, and what Section 8.2 records for the trial has not been established to apply here as well, so this Policy makes no claim about how long that platform keeps this text or whether it may use it to train its models. We will update this Policy when those terms are confirmed. Nothing is sent unless you ask, no other part of your canvas is included, and the credential stays on our servers and never reaches your browser.
  • Certified consultants, only when you grant a specific consultant explicit access to specific business content for a specific engagement, as described in Section 7.
  • An organization that sponsors an individual's canvas, which receives only the run records of the seats it holds in its own work area, and nothing else on that canvas — see Section 8.
  • The house AI provider during a trial. If you take a trial that runs on our own AI account, the content those trial runs send to the model goes to a single AI provider — Anthropic's Claude, through Claude Code on the house account — to produce that run's result. What that provider keeps of that content, and what it may use it for, are governed by that provider's own published terms. We hold no separate arrangement with that provider about how long the content of a request is kept. Section 8.2 names the published document we read, the date we read it, and what is still open.
  • A person you name on a gate, who receives a message sent from your own connected accounts, as you — not from us — as described in Section 8.
  • Service providers who support our infrastructure (for example, email delivery, error monitoring) under confidentiality obligations, limited to what is necessary to provide their function.
  • Legal and safety, where required by law, subpoena, or to protect the rights, property, or safety of Big Think Labs, our customers, or the public.
  • Business transfers, if we are involved in a merger, acquisition, or sale of assets, subject to this Policy or a successor policy with comparable protections.

A share link you create yourself, and the one thing it carries. When you copy a share link for a canvas, the link carries the shape of that canvas — its departments, its sections, its seats, the wiring between them, and the names and units you gave them — and nothing else. It does not carry your numbers (volumes, ratios, capacities, costs, prices, budgets), the names of the people holding your seats, your providers, your notes, your steps, your tasks, or any other free text you typed about a seat. What the link carries sits in the URL fragment, which a browser never sends to a server, so a canvas shared this way does not reach us, our hosting provider, or anyone else along the way; the person you send it to gets their own copy to change, and it is not linked to yours. Two limits we would rather state than have you discover. A link you created before this change carries the whole canvas, numbers included — a link already sent cannot be reached or withdrawn, and breaking it would take away what its recipient was told they were being given. And a link is only as private as the person you send it to: anyone who has the URL can open it, so treat it the way you would treat a document you emailed.

We do not sell your personal information, as "sale" is defined under applicable state privacy law.

5. Data Retention

We retain operational data (accounts, canvases, connection identifiers) for as long as your account is active. Runs and their outcomes are retained in perpetuity in sanitized form, meaning stripped of the free-text redaction described in Section 2 and, where applicable, further de-identified, to preserve long-term measurement history and product improvement without retaining sensitive content indefinitely. If you request deletion of your account and data, we will delete or de-identify your personal information and canvases within 30 days of a verified request, except: (a) sanitized run and outcome data, which is retained under the perpetuity policy above because it no longer identifies you; (b) information we must retain for legal, tax, or accounting compliance; and (c) backups, which age out on our standard backup rotation schedule.

A partner program application is kept on a stated clock. While your application is live we keep it for as long as it is live. An application you withdraw, and one we decline, is deleted 12 months after that decision, by a job that runs daily rather than by a promise in this document. If you delete your application yourself, from your own page, the record goes at once, together with the record of any decision made about it, and it is not recoverable.

A message relayed to a partner has no clock, because there is nothing to put one on; the abuse count has one of 30 days. The message you send a partner through the directory is passed on and not stored, so no period applies to it: once the mail has gone, no copy of your message and no copy of your address exists here. The count described in Section 2 is kept for 30 days, and it is deleted by the next write rather than by a promise in this document: a write to that table first deletes, in the same transaction, every row older than 30 days, so the clock is kept by the one thing that would otherwise be adding to the pile and there is no scheduled job that can be late. The deletion is held by the database itself, on the table, rather than by the code that happens to be writing, so it runs for every write there will ever be and not only for the ones written by somebody who had read this Section.

Three retention points specific to Section 8. The brain index is kept while the connection to the folder is live; revoking the connection ends our access to the folder, and the index is then deleted or de-identified. Gate records naming a person who has no account — the name, the answer, and the date — are retained as part of the gate's record for as long as that record is retained. Run records from a trial are retained by us on the same footing as any other run record — that is the sentence above, applied to a trial. What the house account's own provider keeps of the content of a trial request is a separate matter, governed by that provider's own published terms and not by this Section; Sections 4 and 8.2 say what we know about those terms and what we do not.

6. Security

We use industry-standard technical and organizational measures to protect your information, including encryption in transit, access controls, and bearer-token authentication for the ingest API. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If we experience a security incident affecting your data, we will notify you as required by applicable law.

7. The Operator-Cannot-Read Commitment

Big Think Labs' operators — including Craig Mathews and any employees or contractors — cannot read the content of your business data (canvases, run detail, connected-application content) as a matter of routine operation. Access is restricted by default. The only exception is when one of our operators is separately engaged by you as a consultant, and you have given that consultant an explicit, scoped grant of access to specific content for a specific engagement. Grants are logged. This commitment is modeled on Health Insurance Portability and Accountability Act (HIPAA)-style minimum-necessary access principles as a matter of our own policy; Big Think Labs is not a HIPAA-covered entity or business associate, and this Policy does not create HIPAA obligations unless a separate agreement says otherwise.

8. Sponsored Accounts, the Trial, Gate Participants, and the Brain

This Section describes four arrangements in which information crosses between parties, and what each party can see. The contractual rules behind them are in our Terms of Service, Section 12.

8.1 What a sponsor can see

Where an organization pays for an individual's canvas, the individual is the account holder and, as between them, owns the canvas. The paying organization is a payer, not an owner. It can see the seats it holds in its own work area on that canvas and the run records those seats produce. It cannot see any other area, project, seat, connection, note, document, or run record on the canvas — including anything in an area paid for by a different organization — and the Service provides it no route to them. Nor can it set or read gates, cadences, or budgets outside the seats it holds. When the sponsorship ends, for any reason, the individual keeps the canvas and may convert it to a self-paid account or export it; the paying organization keeps the run records of the seats it held; and the link between the two canvases is severed, ending each side's access to the other.

Connections carry the same rule. Every connection — an AI account, a calendar, a mailbox, a money feed — has an owner, either a business or an individual, and a seat may act only on connections owned by its own scope. An AI account paid for by an employer is not available to that person's personal areas, and a person's own accounts are not available to their employer's work.

8.2 The trial, its provider, and retention

We do not run AI agents, with one exception: a trial in which agents run for a limited period on an AI account we hold. During a trial, the content those runs send to a model goes to one AI provider — Anthropic's Claude, through Claude Code on the house account — to produce that run's result.

What that provider keeps of that content, and what it may use it for, are governed by that provider's own published terms. On the question of training, one of those documents is explicit: Anthropic's Commercial Terms of Service, effective June 17, 2025, which we read on 2026-09-06, state that Anthropic may not train its models on customer content submitted through its services. On the question of how long content is kept, we have not obtained any separate contractual commitment from that provider, so this Policy does not tell you how long that provider keeps it. If we obtain such a commitment we will update this Policy to say so and to say what it covers. What we keep of a trial is in Section 5: the run record, on the same footing as any other.

A trial is capped at 50 runs or 14 days, whichever comes first. On a trial connection, outbound communications are disabled and no recipe may move money, so no message reaches anyone outside your business from our account and no payment can be made from it. When the trial ends, seats must move to a connection you own. Run records made during a trial are yours and stay on your canvas.

8.3 Messages to a person named on a gate

A gate may name a person who is consulted before a decision, or a person whose approval the gate requires. If that person holds an account with us, the gate reaches them inside the Service. If they do not, the message goes out through your connected accounts, from you, at your direction — we are not the sender, and we do not add that person to any list, market to them, or contact them for our own purposes. What we store about such a person is what you supplied and what came back: their name, the address you used, the message, the answer, and the date, held as part of the gate's record. You are responsible for having the right to contact them.

8.4 The brain: an index, not a copy

You may point the Service at a folder of your own documents — standards, handbooks, procedures, personal notes — held in your own storage and read through a connection you own. Those documents stay where they are. We do not take or keep a copy. What we hold is an index of the folder, so a question can be answered with a citation back to your document, and the run records of the work that read it. Revoking the connection ends our access to the folder at once; the index is then deleted or de-identified as described in Section 5. The documents in your brain are never used to train models for other customers or for third parties, consistent with Section 3.

9. Cookies and Similar Technologies

We use functional cookies only — for example, to keep you signed in and to remember canvas state saved locally in your browser on the free tier. We do not use advertising or cross-site tracking cookies. You can control cookies through your browser settings; disabling functional cookies may affect the Service's ability to keep you signed in or preserve local canvas state.

10. Children

The Service is intended for business use by adults. You must be at least 18 years old to create an account or use the Service. We do not knowingly collect information from anyone under 18. If we learn we have collected such information, we will delete it.

11. California and Other State Privacy Rights

Depending on your state of residence, you may have rights to know what personal information we hold about you, to request deletion, to correct inaccurate information, and to opt out of certain uses. To exercise these rights, contact us using the details in Section 14. We will verify your identity before fulfilling a request. We do not discriminate against you for exercising these rights.

12. Where the Service Is Offered From

The Service is operated from the United States and is directed to business users in the United States. If you use the Service from outside the United States, your information is transferred to and processed in the United States, where privacy law differs from the law where you live. We will publish the additional terms that European, United Kingdom (UK), and other international users are entitled to before offering the Service in those markets.

13. Changes to This Policy

We may update this Policy from time to time. We will post the updated version with a new "Version" line and, for material changes, provide notice as described in our Terms of Service. Continued use of the Service after an update takes effect constitutes acceptance of the revised Policy.

14. Contact

Questions about this Policy, and requests regarding your data, reach us through the contact details published on the contact page at archetric.com, or by mail to Big Think Labs, LLC, 1227 August Moon Court, Fuquay-Varina, North Carolina 27526.


This page renders our official copy directly, so what is published here can never say something different from what we keep on file.