userclouds · dstello · May 30, 2025 · May 30, 2025
diff --git a/app/(home)/page.tsx b/app/(home)/page.tsx
@@ -24,7 +24,7 @@ export default function HomePage() {
 
       <div className="flex flex-col sm:flex-row gap-4">
         <Link
-          href={`${process.env.basePath}/docs`}
+          href="/docs"
           className="inline-flex items-center justify-center rounded-lg bg-fd-primary px-6 py-3 text-sm font-medium text-white hover:bg-fd-primary/90 transition-colors"
         >
           Read Documentation

diff --git a/content/_dangling-articles/key-concepts.mdx b/content/_dangling-articles/key-concepts.mdx
diff --git a/content/_dangling-articles/principles-for-use.mdx b/content/_dangling-articles/principles-for-use.mdx
diff --git a/content/docs/guides/(data-access)/how-to-guides/use-your-custom-sdk.mdx b/content/docs/guides/(data-access)/how-to-guides/use-your-custom-sdk.mdx
@@ -6,12 +6,9 @@ hidden: false
 createdAt: "Fri Feb 09 2024 20:27:45 GMT+0000 (Coordinated Universal Time)"
 updatedAt: "Fri Feb 09 2024 20:28:13 GMT+0000 (Coordinated Universal Time)"
 ---
-For a smooth developer experience, UserClouds automatically generates a custom SDK for each of your tenants. This SDK allows you to call each of your <Glossary>accessor</Glossary>s and <Glossary>mutator</Glossary>s as functions directly in your codebase. 
+
+For a smooth developer experience, UserClouds automatically generates a custom SDK for each of your tenants. This SDK allows you to call each of your <Glossary>accessor</Glossary>s and <Glossary>mutator</Glossary>s as functions directly in your codebase.
 
 ## Downloading the custom SDK
 
 You can download your custom SDKs manually from your tenant homepage in the UserClouds console. Custom SDKs are currently available in Go and Python, with more languages in development. Please reach out to us if you need a different SDK!
-
-## Deploying the custom SDK
-
-_More info coming soon!_
diff --git a/.../guides/(data-access)/proxy-and-plug-in-implementation/1-proxy-introduction.mdx b/.../guides/(data-access)/proxy-and-plug-in-implementation/1-proxy-introduction.mdx
@@ -49,8 +49,8 @@ Each of these proxies sits between the application and data source, intercepting
 | Functionality                                      | SQL Proxy             | NoSQL Proxy                                      | API Proxy |
 | :------------------------------------------------- | :-------------------- | :----------------------------------------------- | :-------- |
 | Granularity                                        | Global, Column, Query | Object Store _(file path considered in context)_ | Endpoint  |
-| Masking                                            | ✅                    | :x: _ (coming soon!)_                            | ✅        |
-| Tokenization                                       | ✅                    | ❌ _ (coming soon!)_                             | ❌        |
+| Masking                                            | ✅                    | ❌                                               | ✅        |
+| Tokenization                                       | ✅                    | ❌                                               | ❌        |
 | Access Policies                                    | ✅                    | ✅                                               | ✅        |
 | Access Policies that consider data in the response | ✅                    | ❌                                               | ❌        |
 | Logging                                            | ✅                    | ✅                                               | ✅        |

diff --git a/content/docs/guides/(data-storage)/definitions/purpose-and-consent.mdx b/content/docs/guides/(data-storage)/definitions/purpose-and-consent.mdx
@@ -6,9 +6,10 @@ hidden: false
 createdAt: "Thu Aug 03 2023 19:04:43 GMT+0000 (Coordinated Universal Time)"
 updatedAt: "Fri Jun 28 2024 22:47:11 GMT+0000 (Coordinated Universal Time)"
 ---
+
 ## Summary
 
-Purposes are used to track, enforce and audit user consent in User Store. Purposes have names like `marketing`, `analytics` and `operations` that map to the data processing purposes described in your privacy policy and terms of service. 
+Purposes are used to track, enforce and audit user consent in User Store. Purposes have names like `marketing`, `analytics` and `operations` that map to the data processing purposes described in your privacy policy and terms of service.
 
 When users share data with you, they consent to a set of purposes for each piece of data that they share. For example, they might consent to using their email address for personalization, but not marketing. User consent is granular: it is stored per piece of data. Note that <Glossary>system column</Glossary> are not associated with purposes.
 
@@ -20,7 +21,6 @@ You can define and describe your own set of purposes in the Purposes table of th
 
 ![Name and describe your data processing purposes in the Purposes table under Access Rules.](/assets/images/purposes.webp)
 
-
 ## How users consent to purposes
 
 Users can share and revoke consent to process their data for a particular purpose (or set of purposes) when:
@@ -29,7 +29,7 @@ Users can share and revoke consent to process their data for a particular purpos
 - They share a new piece of data with you
 - They complete flows authorizing or revoking authorization for particular uses of their data, e.g. a sign-up for a weekly newsletter
 
-Consent is granular: it is stored per piece of data. For example, an end user might consent to using their email address for marketing, but not their phone number. When a user consents to a particular data processing purpose for a particular piece of data, this is tracked in User Store as a **consented purpose**. 
+Consent is granular: it is stored per piece of data. For example, an end user might consent to using their email address for marketing, but not their phone number. When a user consents to a particular data processing purpose for a particular piece of data, this is tracked in User Store as a **consented purpose**.
 
 ## How user consents are stored
 
@@ -39,8 +39,6 @@ Consented purposes are stored per column, per user in User Store. For example, a
 
 Consents must be specified for all mutator operations (creates, updates and deletes). Consents are passed to the User Store in the context at execution time. If a data value is authorized for multiple purposes, deleting a data value for a single specified purpose will remove that consented purpose (only).
 
-_(Coming soon)_ UserClouds is building off-the-shelf integrations with consent management solutions like OneTrust and PrivacyArc to pass consent data collected by third party services into User Store.
-
 ## How user consent is enforced
 
 In UserClouds, data <Glossary>accessor</Glossary>s (read APIs) are used to retrieve a pre-specified set of columns of data for 1+ users. Every accessor is associated with a purpose at creation time.

diff --git a/content/docs/guides/(data-storage)/definitions/regions.mdx b/content/docs/guides/(data-storage)/definitions/regions.mdx
diff --git a/content/docs/guides/(data-storage)/how-to-guides/import-user-data.mdx b/content/docs/guides/(data-storage)/how-to-guides/import-user-data.mdx
@@ -7,4 +7,4 @@ createdAt: "Fri Apr 05 2024 22:04:25 GMT+0000 (Coordinated Universal Time)"
 updatedAt: "Fri Apr 05 2024 22:05:06 GMT+0000 (Coordinated Universal Time)"
 ---
 
-\_User Data can be imported into the User Data Vault in bulk. Docs coming soon!
+User Data can be imported into the User Data Vault in bulk.