Changes to our privacy policy, newest first. The policy itself shows the most recent ones. In each row, this page means the policy.
| Date | Change |
|---|---|
| 2026-11-17 | One rewrite of the whole page, to make it shorter and easier to read. Each section now says what its service keeps by kind, and a new table, how long we keep each record, puts the retention periods in one place. What the phone and watch apps reach for is described by kind. The page no longer describes how other companies' services work where that isn't ours to state, such as the push services phones use, or the hardware detail behind confidential processing. The confidential processing section no longer says the build your journal checks can't be changed without a release anyone can see; it says your journal trusts only the build pinned in solstone's open source code. Otherwise, who sees each record, how long it is kept, how it is deleted, and everything we will never do are unchanged. No processor added or removed. The binding covenants are unchanged. |
| 2026-11-16 | The changelog moved to its own page, solpbc.org/privacy/changelog. This page now shows the most recent changes, and its links to the changelog point there. Nothing else on this page changed, apart from its date. |
| 2026-11-08 | The solstone extension section now says your browser's permission decides which sites it reads. Allowing a site in your browser adds it, and if your browser allows the extension on every website, it reads every website except sites you leave out. In some browsers it also asks you to agree first. An update never widens what it reads by itself. The section no longer describes pausing Safari in the solstone app. It now says that after the solstone app is unpaired, the extension can still take in pages until it next checks with the app, and that in Safari, removing the app may leave the sites you allowed in place. Smaller corrections: we say we don't use the crash reports phones share with app developers, rather than that there are none; we honor the Colorado Privacy Act's rights whether or not it applies to us; how long a push service holds a notification is its own to say; Stripe's retention is described as Stripe's, and we say its Link option may already be selected; the sentence on sharing in the covenants section points to our processors' own uses, Stripe's among them; and that section now says that after the founder, Article 8 can only be amended to strengthen it. What the extension takes in from a page, and where it goes, don't change. No processor added or removed. The binding covenants are unchanged. |
| 2026-11-05 | The solstone extension has no welcome page on iphone and ipad. There, if your first site is one you add from the extension, it says then what it takes in, and its settings have the full description. On a computer, you still agree on its welcome page first. The section also now says that allowing a site in your browser adds it, and it no longer says the extension names the addresses a site covers each time you add one, because on iphone and ipad a later add from its popup goes straight to Safari's prompt. What the extension takes in and where it goes don't change. No processor added or removed. The binding covenants are unchanged. |
| 2026-11-05 | The android paragraph now names two things the solstone app can take in that the page had left out: your calendars, when you turn on the calendar source, and your screen, which android asks about each time you turn that source on. What each takes in goes into your journal. go.solstone.app is now listed for everyone who reaches it, in the section on the sites we run and in Cloudflare's row, and what the page says about a pairing link moved there from the android paragraph. No processor added or removed. The binding covenants are unchanged. |
| 2026-11-01 | The solstone extension is coming to Safari on iphone and ipad, inside the solstone app, and the section says what differs there: the extension keeps taking in the sites you've chosen while the solstone app is in the background or closed, and what it takes in waits on the device until the app next runs; pausing Safari in the solstone app always stops it; removing the solstone app discards the pages the app holds; and it takes in nothing from private browsing. The section now says *the same device* where it said *computer*, and the phone section points to it. Private network: the relay's record of your journal is described by kind; it now also covers when the journal last renewed its credential by proving it holds its own key. No processor added or removed. The binding covenants are unchanged. |
| 2026-10-29 | Confidential processing's machine is starting to send our monitoring a health report, and the section now says what is in it: whether its parts are running, error codes, and totals for all journals together and a monthly spread of how much journals used, never broken out by journal. It holds nothing you sent and names no journal or sign-in. Cloudflare runs that monitoring, and its row says so. No processor added or removed. The binding covenants are unchanged. |
| 2026-10-28 | The solstone extension section describes what the extension takes in by kind, rather than item by item, and the extension's welcome page says what it takes in before you agree. The section now names facts the extension notes about the tab and your browser, such as whether the tab was in front; says that when you add a site or leave one out, the extension says which addresses that covers, and that a site such as bank.com can cover every address under it; and says that pausing the solstone app pauses the extension too, unless you turn that off. Nothing the extension takes in goes anywhere new. Email: the page no longer names the address the services portal's emails come from. No processor added or removed. The binding covenants are unchanged. |
| 2026-10-24 | The solstone extension section covers all sites. Besides adding sites one at a time, you can let the extension read every website your browser allows, after a separate agreement, and leave sites out. The section now says what it reads that way, that what it keeps in your browser includes the sites you leave out, what leaving a site out covers, and that it stops anything new from that site, as removing one does. The list of what it keeps in your browser now also names two things it already kept: notes about particular sites, such as one where it couldn't take in a page whole, and, while a page is open, the last copy it read of it. The Chrome Web Store Limited Use statement now covers everything the extension takes in. No processor added or removed. The binding covenants are unchanged. |
| 2026-10-22 | Named two more things the solstone app asks for on iphone and ipad: your photo library, when you import from it, and your calendars, when you turn on the calendar source. What each takes in goes into your journal. Cloudflare's row in the processor table now names our replies to the support form, which it sends, and Google's row no longer counts them. Sentence case throughout. Otherwise no words changed, except where a sentence that started with one of our names is reworded. |
| 2026-10-13 | Corrected how long two turn-on records are kept. The page had said the records the private network's and encrypted backup's turn-on pages leave for your journal to collect are kept until your sign-in is deleted; each is deleted a day or two after it is used or stops being good. The private network's is good for an hour, not five minutes, if you turn it on without a subscription. The solstone.me section now names the short-lived record its turn-on page leaves too. The solstone extension section now covers a browser that lets the extension run in private windows, where it still takes in nothing, and a copy of the extension that comes inside the solstone app and updates with it. It also says how to clear what the extension kept in Safari, where removing the solstone app doesn't remove it. |
| 2026-10-09 | Confidential processing is now available by subscription, and stays complimentary for scouts. The section on it now says what the turn-on record holds while your journal waits for a subscription of its own. Corrected: the page had said the turn-on record is kept until your sign-in is deleted; it is deleted a day or two after it is used or stops being good. The page had also said metering and abuse handling both run inside the confidential container; only metering does. Links to the services terms now use their current address. It also says your journal can check its own access, and what Cloudflare sees when it does. |
| 2026-10-06 | You now close your sign-in, rather than delete it. Where the page described what you do at services.solstone.app/account/delete, it now says you close your sign-in and have 72 hours to change your mind and keep it; delete stays for what sol pbc then deletes, and for your right to deletion. What is deleted, when, and what outlasts it are unchanged. What closing does to your services and subscriptions is in the services terms. |
| 2026-10-06 | Added the solstone extension, which works with the solstone app: that it reads only sites you add, after you agree on its welcome page and your browser asks you to allow each one; what it takes in on those sites, including messages on a mail or chat site and text a page doesn't show; that it sends everything only to the solstone app on the same computer and connects to nothing on the internet itself; that the solstone app puts it into your journal the way it does everything else it takes in; what stays in the browser and how to clear it; and sol pbc's affirmative Chrome Web Store Limited Use statement. No processor added or removed. The binding covenants are unchanged. Writing to us names the versions box and what a report fills in. Both support forms have an optional your versions box, and when you report a problem from inside a solstone app it fills in the versions you're running and the system they run on; the page now says so, and that you see and can change all of it before you send. Wording: the relay keeps a record of your journal, and the page no longer calls your journal or its computer your home. |
| 2026-10-06 | What you send through the contact form now lives in our mailbox, not in the records our systems write about it. Since the afternoon of September 26, 2026, a contact-form message lands in the mailbox Google runs for us, and the record of its arrival keeps who wrote, when and how our AI check rated it, not the message itself; the record of an email no longer keeps its subject, its opening lines or the check's summary of it. The page now names Google for the contact form too, and says that these records keep how the AI check rated a message. Also named, where the page had left them out: our older support address, support@solpbc.org, which still reaches the same mailbox; that a support request sent by August 7, 2026 left a record of its own in our systems, which keeps its subject and who sent it, and a history that can keep what you wrote; the apps' checks for a newer version; that older versions of solstone fetch some of their tools from GitHub or the tools' own sites; that confidential processing's check asks NVIDIA whether the GPU's certificates are still good; the bot check on the services portal's sign-in; the edge logs of v-it.org, solstone.app, trust.solstone.app, transparency.solstone.app and explore.v-it.org; the index of public vit records sol pbc runs, and that vit's explore and inbox commands ask it; help asked on GitHub or Bluesky; our read-only access to Stripe, which shows what Stripe holds about your payments, and that the AI agent that helps us can use it too, and that our working records of a look-up may keep what it showed; and that when we look up a sign-in, the AI agent that helps us sees what we look up, and our working records of it may name your email. Named a limit on what solstone.me protects, and what takes sol pbc out of it: whoever controls the solstone.me name, today sol pbc and Cloudflare, could in principle get a certificate of their own for your address; a new one would normally show in public certificate logs, but not always, and until November 30, 2026 Cloudflare also holds older certificates covering every address, and using one of those wouldn't show in the logs; so where the page said sol pbc can't see an agent's traffic, it now says sol pbc doesn't, and the Cloudflare row now says it is given no readable byte of your journal; your own domain, with a tunnel that only passes the bytes through, takes sol pbc out of the path, and the section warns that some free tunnels decrypt your traffic to move it, and that whoever runs one can read what your agent reads and reuse your agent's key to reach your journal. The summary line in confidential processing now points at each service's own section for how its key keeps us out. Corrected: where the page said sol pbc holds no record of what your agents asked and is built so it cannot receive it, it now says no readable record, and that if you use the operated backup, that record is inside the encrypted copy of your journal, which we have no key to. Turning confidential processing or its audio switch off applies to anything your journal starts from then on, and work already under way finishes where it started; the page had said it took effect immediately. The page had said sol pbc's systems never fetch or store your card's details; the services portal and the hosted services never ask Stripe for them or keep them, but our read-only access to Stripe can show them. The page had said we use your billing details only to run your subscription; we also use them to keep our books. The page no longer says a closed support request keeps the product you picked; it doesn't. A sentence about your solstone.me address now says that it is never reassigned; it had said the address is never given to anyone else. |
| 2026-09-26 | Disclosed the services portal's request trace, which we have kept since September 12, 2026 and this page had described only for the iphone hop: a record of each request the services portal's code answers and each scheduled job it runs, deleted after 90 days, with no network address in it. The page says what some traces carry, and that older ones also record which page was asked for, until they are all gone by December 23, 2026. This corrects the sentences that said we keep no connection metadata for confidential processing, that we write nothing down about its credential check, and that we keep no log of solstone.me's passes, and it corrects how long the iphone hop's traces last; it corrects the page, not what we do. The trace is now named beside those sentences, in what outlasts a deletion, in what a demand could reach, in our GDPR legal bases, and in Cloudflare's row of the processor table. Disclosed a one-way fingerprint of each checkout that started a subscription, kept with no scheduled deletion date so our own internal alert of a new subscription is never raised twice, and that the sign-in abuse counts are also kept per sign-in. The list of what outlasts a deletion now governs wherever another section says something is deleted with your sign-in or kept until your sign-in is deleted. Disclosed that Stripe holds the name on your card and an operator can see it; that Stripe may offer its Link wallet at checkout, and that we keep nothing you give it; the copies we keep of the confirmations, renewal reminders and other notices we email you as a subscriber; and that Cloudflare delivers all the email we send you from services@solstone.app. Clarified what the transparency page shows, what the download leaves out, and that services.solstone.app is the services portal. The iphone hop's list of what it forgets no longer includes when a notification was sent, because its trace keeps a time. Added what withdrawing from a subscription, and asking us to start a service right away, would leave in our records. |
| 2026-09-24 | Notifications from your journal can now reach your phone, and they are off until you turn them on, phone by phone. Disclosed what each party along the way handles: your journal locks each notification to a key only that phone and your journal hold, so no push service and nothing sol pbc runs can read one; on iphone, a hop sol pbc runs on Cloudflare's network passes it to Apple's push service and keeps no record of your phone or your journal; on android, your journal sends straight to Google's push service or your delivery app's server, which also sees the network address of the machine your journal runs on. Cloudflare's row in the processor table now names the hop, and Apple and Google are named as the push services phones use, not as our processors. |
| 2026-09-20 | Added sol pbc's fourth hosted service, solstone.me: an address on the internet for your journal, so an agent you already use can read from it, through a relay sol pbc runs on a Microsoft Azure machine that holds no key to what passes and keeps no record of it. Disclosed in full: the three records we keep (the address binding, the turn-on record, and the address reservation); that the reservation outlives a deleted sign-in with nothing in it that points back to you, so the address can never be issued to anyone else; and that the address's certificates are listed in public certificate logs, as the certificates behind secure websites are, so the fact that the address exists stays public for good. We keep no log of the passes your journal asks for and no record of what any agent asked your journal for, what it was shown, or what it was refused. The connection metadata Azure handles and the pass and address-lookup metadata Cloudflare handles are disclosed, and the agents you connect are named as not our processors. Cloudflare's and Microsoft Azure's rows now say what each runs for it; no processor added or removed. Also narrowed the stated use of connection metadata and storage information for private network and encrypted backup from "operate, secure, and bill" to "operate and secure", matching the services terms, and corrected the summary's claim that each hosted service has a free alternative: two of the four alternatives can cost money with another provider, so the page now says each has a way to do the same thing with sol pbc out of the path, and no longer calls the bring-your-own paths free. Corrected the two sentences on a successor entity to carry Article 8's full condition: a successor must be bound to a substantially equivalent public benefit and to substantially equivalent balancing duties. Corrected the sentence on new services: this page had said we would notify owners before launching one; we give no notice beyond this page and its changelog, so it now says that we publish the updated policy here before launch. Added a table of contents and a link target for every section. The binding covenants are unchanged. |
| 2026-09-20 | One comprehensive accuracy pass, and a reshaping so the page is easier to read. The short version is now a plain list with a link into each section, and each hosted service is described once, in one place, instead of in two. Corrected: we stopped saying we keep a record of which of your devices may reach which of your homes, because since September 2026 we no longer keep one; the relay keeps a record of your home, and this page now describes that record rather than leaving it to be inferred. The page now says that the relay keeps no connection log of its own. Added what the solstone apps on your phone and watch ask permission to reach on your own device: microphone, camera, location, local network and notifications, plus the screen on iphone and ipad, which the page had never described. Added your sign-in: the emails, passkeys and sessions services.solstone.app holds, the 30-day tail on ended sessions, and where to see them; and, for each hosted service, the access records the portal keeps for it, which the page had named only for confidential processing. Added notifications, which reach sol pbc not at all today, and the rule under which a cross-device hop would ever turn on. Added writing to us: the support form, the contact form, where mail to support@solstone.app lands, which is a mailbox Google runs, and that an AI agent on an outside provider's models reads what you send us; Google is added to the processor table on that basis, and Cloudflare's row now names what it runs for us, including the support form, the sign-in codes we email you, and the portal that checks a confidential-processing credential. Corrected the deletion story: you can delete your sign-in and every service yourself at services.solstone.app/account/delete, with a 72-hour safety period; the confidential-processing access records and the backup's credential log are deleted with your sign-in, where this page had said that was queued work; and the things that outlast a deletion are now named one by one, including the 30-day recovery image our database provider keeps. Corrected the confidential-processing access records: they tell us that you consented and each time a credential was issued or refused, not how much you used, which stays inside the container; a third record, the one the turn-on page leaves so your journal can collect its credential, is now disclosed; and the container notes that a channel was admitted or refused. Corrected the covenant on safeguards to match the bylaws' own words: sol pbc maintains them, access logging included. Corrected the processor sentence so it no longer overstates Stripe's contract: Stripe's own terms let it analyze what it holds to improve its products, and this page now says so. Corrected billing retention: this page promised to delete billing details once your subscription and the tax period had both ended; nothing ran that deletion, and billing details now stay until you delete your sign-in, which deletes your customer record at Stripe. Added the self-service data download at services.solstone.app/account/export, which covers your sign-in, subscriptions, scout records and the lasting access records for each service; what the file leaves out, it names, and email stays the route for that. Corrected the amendment-lock sentence so it reaches Article 8, which is what the founder-consent and strengthen-only rules lock, and says the bylaws sit under it. Said that solstone fetches its runtimes, models and backup tool from updates.solstone.app, which leaves the same edge logs as visiting this site, and that we read only aggregate request and error counts from those logs. The contact form, and the support portal's former self-registration route and the removal of the records it left, are disclosed in the writing-to-us section. Following the naming canon, this page now says "our own model" where earlier versions said "our own engine"; nothing about what reads your content changed. No processor was removed. The practices that changed are these: the relay no longer keeps device records, the support portal no longer registers journals on its own and the records that route left are gone, the contact form on solpbc.org no longer passes us the address it was sent from, and the deletions this page describes now run, including deleting your sign-in yourself; where this page had promised a scheduled deletion that never ran, it now says what we keep. The binding covenants are unchanged. |
| 2026-08-28 | Corrected the sentences that claimed, in sol pbc's name rather than a named service's, that nothing readable from your journal reaches us. Those sentences were written when sol pbc ran two hosted services and both were sealed by key custody. Confidential processing, added 2026-08-01, is sealed a different way: by a published build your journal verifies before it sends, and the sentences that summarised our services had never been updated to account for a third shape. Each one now names the service it is about. The note above the processor table had been inaccurate since 2026-06-16, when Cloudflare was named as the relay's network processor: it said we send our processors "never a byte from your journal," while the table directly below disclosed the encrypted bytes and encrypted blocks Cloudflare holds. A correction, not an addition: this page previously said that to run confidential processing we count "fleet-wide totals" that are "not associated with you, your journal, or your account." That was not the instrument. What we actually keep, to run and moderate the service, is a record tying your access to your sign-in and to a journal, and a log of each time that journal was issued or refused a credential. Both are associated with you, which is the opposite of what the old sentence said. Both are Customer Data under our covenants and are now disclosed as such, with how to get them. We also say plainly, rather than round it off, that the second of those two outlives a deleted sign-in today, and that bringing it under the same deletion rule is queued work. We keep no connection metadata for that service, which is a real difference from the other two. The description of confidential processing also changed: it previously said only that we would not tell you we never see it, and it now says plainly that our own engine reads what you send while it answers you, and describes the published build and the check your journal runs before it sends. The recording-laws section now says that what you record on your own hardware goes elsewhere only through a hosted service you turn on. The covenant citation for "we never sell, license, sublicense, or lease your data" is corrected to Section 8.3(a)(1), which is the absolute; the previous line cited the conditional and dropped two of the four verbs. No data practice, processor, or retention period changed, and the binding covenants are unchanged, what changed is that the page now describes them accurately. |
| 2026-08-21 | Standardized the confidential-processing and recording-laws sections on solstone: the recording-laws section names the app as the solstone app. It now describes what the app takes in as what you share with it, no longer a closed list; attributes the act of recording to you where it describes that intake, not only where it allocates responsibility; and says that what the app takes in goes into your journal. The statutory term recording is unchanged, and so is the you-not-us responsibility allocation. No processor added or removed. The binding covenants are unchanged. |
| 2026-08-01 | Added sol pbc's third hosted service, confidential processing, an AI model sol pbc runs on confidential GPU hardware for journals that want more capacity to think with than their own machine has. Disclosed in full: that it is off until you turn it on and reversible at any time; that what leaves your device is the text and images the model works through, plus your audio for transcription when that switch is on (it is on by default while the service is in use, and turning it off keeps speech-to-text on your own device); that your journal itself never leaves; that sol pbc runs the model itself, on its own weights and serving stack, with no third-party AI provider in the path; and, stated plainly rather than softened, that what you send is encrypted over the network but visible in running memory only while it is being processed by that engine, which is not the sealed arrangement the relay and the operated backup have, and we do not claim it is. What we do commit to is what becomes of it: the service runs zero data retention (ZDR). No content is kept, not even in logs. No human reviews it. Nothing is used to train anything. Named Microsoft Azure as a new processor: it hosts the confidential GPU machine (an AMD SEV-SNP confidential virtual machine with an NVIDIA H100 in confidential-compute mode) and the hardware boundary excludes Azure from what that machine is processing, memory included, so it sees no content, no prompts, and no transcripts. Disclosed the verification: your journal cryptographically checks the hardware before every use — the AMD attestation chain, the GPU's evidence, the binding to the encrypted connection, and a fingerprint of exactly which software booted, pinned in solstone's open source code so it cannot be quietly repointed — and sends nothing if the check fails, deferring honestly rather than falling back to any other service. Usage accounting is fleet-wide totals not associated with any owner. The binding covenants are unchanged. |
| 2026-08-01 | Removed the browser-extension disclosure added on 2026-07-26, because there is no longer a browser extension to disclose. We deleted the delivery route it used; that deletion shipped in solstone 1.0.21, and the extension is not a working part of solstone. It was never announced and never listed, and nothing it took in was ever readable to sol pbc, because it was sealed inside the browser and we held no key. When browser support returns it will be part of a full sol client and covered by that client's disclosures, and this policy will describe it then. The row below records what the 2026-07-26 disclosure said, and stays as written. Also updated the recording-laws section to describe what solstone does as experiencing your day along with you, matching the language used elsewhere; the statutory term recording and the you-not-us responsibility allocation are unchanged. No processor added or removed. The binding covenants are unchanged. |
| 2026-07-26 | Disclosed solstone's browser extension in full: that it arrives holding no standing access to any website and reads only the sites you add behind a per-site browser permission grant (and what your browser hands its toolbar popup); that it takes in a page's rendered text and rough layout — including text the page renders out of sight, like screen-reader labels — but never pixels, raw HTML, form-field contents, clicks, scrolling, or keystrokes; that it reads an added site whenever a tab on it is open, background tabs included, and re-reads as the page changes; that the page address is reduced to origin and path inside the page before anything leaves it, with query strings, fragments, and embedded credentials dropped; that message text is included where you add a messaging site, and that outside Gmail and Slack a message you are still typing is taken in with the page; that what it took in waits in your browser's own storage until your journal accepts it, and how to clear it. Named both destinations honestly: a journal on your own computer, which sol pbc never touches, or sealed inside the browser to your own home over the existing blind relay — with that relay's connection metadata and device-enrollment records disclosed as Customer Data, added to the relay section, the processor table, and both subpoena paragraphs. No new processor. Added sol pbc's affirmative Chrome Web Store Limited Use statement, including that our articles bar selling outright and foreclose reliance on the store policy's merger/acquisition transfer permission. The binding covenants are unchanged. |
| 2026-07-13 | Disclosed Scout application/status history, including the forward-only lifecycle audit, its exact minimized contents, operational-only purpose, owner-sign-in-lifetime retention/deletion boundary, and support export channel; named Cloudflare D1 processing; clarified that local use of solstone and vit still sends sol pbc nothing. The lifecycle audit adds no journal content and the binding covenants are unchanged. |
| 2026-06-23 | Added sol pbc's second hosted service, the operated tier of encrypted backup (storage sol pbc runs so an encrypted copy of your journal can live off your own machine). Disclosed what it collects — encrypted blocks sol pbc has no key to and cannot read, plus minimal storage operational metadata (object count, ciphertext size, last-changed time, used only to operate and bill) — named Cloudflare R2 as the storage processor, and disclosed the retention rule: after the paid period ends, the encrypted backup is kept 30 days, then permanently deleted. Stripe (payments) is unchanged. The binding covenants are unchanged. |
| 2026-06-20 | Renamed the hosted service from "solstone hosted — private link" to private network to match sol pbc's v2.1 brand model (the brand lives at the layer; services are named by mechanism). Naming-only — no data practice, processor, or covenant changed. |
| 2026-06-16 | Updated for sol pbc's first hosted service, solstone hosted — private link (a paid, blind-by-construction relay). Added the hosted-relay and billing data-collection disclosures; named Stripe (payments) and Cloudflare (relay network) as processors, with a processor table; described the hosted service in detail (data, processors, encryption, export/delete, graceful cancellation, rights); updated "your rights" with the services.solstone.app self-service + support@solstone.app channels, the CPA appeal mechanism, and the CPA/CCPA/GDPR rights. The binding covenants are unchanged. |
| 2026-05-01 | Hosting attribution corrected: solpbc.org is served by Cloudflare Workers only — the prior reference to GitHub Pages reflected an earlier deployment and was no longer accurate. Linked to the Cloudflare privacy policy for the edge server logs Cloudflare collects from visitors. |
| 2026-05-01 | Updated to reflect the amendment and restatement of Article 8 (CO SOS Doc. 20261537456) and the adoption of restated bylaws. Acquisition language updated to reflect that change of control is conditional (mission-aligned successors only, with covenants no less protective). Amendment-lock language updated to reflect the new strengthening-only rule outside the founder's stewardship. Operational-agent succession references removed; succession now flows through the Successor Designator mechanism in Article 8 §8.4. |
| 2026-03-29 | Initial publication |
Questions? Get in touch.