A plain-language summary of what we store, how we use it, who can access it, and what control you have over your workspace data.
Picrowd stores the data you add to your workspace: records, custom fields, notes, files, comments, project structure, collaboration settings, shared links, and account details.
Files you upload are stored in Cloudflare R2. Authentication data is stored for any sign-in method you use: Google, GitHub, Apple, or magic links. We do not have access to your third-party account passwords.
Your data is used exclusively to operate the product you signed up for: running your workspace, keeping records and notes in sync between collaborators, generating shared links, sending notifications you have configured, and providing exports and API access.
To run the product, Picrowd uses a small set of infrastructure services. Your workspace data is stored in SQLite on Railway with persistent volumes. Uploaded files are stored in Cloudflare R2. Emails are sent through Resend. Authentication can involve Google, GitHub, or Apple depending on how you sign in.
Plugins like Drive, Dropbox, and Box access external services only when you explicitly connect them and grant permission. They operate under the access you provide.
Picrowd’s AI assistant can connect to Google services — Gmail, Google Calendar, Google Drive, Google Docs, and Google Sheets — but only after you explicitly connect each tool through Google’s OAuth consent screen. Nothing is accessed until you connect a tool yourself, and each tool receives only the permissions listed on that consent screen. You choose which tools to connect, and read and write access can be toggled per tool.
Google user data is accessed solely to provide the specific, user-facing features you invoke: searching or reading email to answer your request, drafting or sending messages you approve, managing calendar events you ask for, and creating, reading, or editing files and documents on your instruction. Tool results appear in your AI session history so you can review exactly what the assistant did; every tool call is also recorded in an audit log you can inspect. Google content is not copied into your workspace records unless you explicitly save it there.
When a request you make requires it, the minimum relevant Google content (for example, the messages matching your search) is processed by our AI model provider strictly to generate your response. It is not used by Picrowd or shared with any provider to build advertising profiles or to train models.
Picrowd’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
When you use Picrowd AI, the content needed to fulfill your request (your message, relevant workspace records, and — if you invoked a connected tool — the minimum relevant tool results) is processed by our AI model provider to generate the response. AI actions that change your data require your approval, are logged, and are reversible.
We do not use your workspace content or Google user data to train our own or third-party generalized AI or machine learning models.
Picrowd uses an authentication cookie to keep you signed in. We do not use third-party tracking cookies, advertising pixels, or analytics scripts that follow you across the web.
Last updated July 7, 2026. Contact: hello@picrowd.com