Privacy Policy
Last updated October 29, 2026
Decize is an organization decision system. This policy explains what data the service processes, why it is processed, and the controls available to workspace members.
Who we are
Decize (“Decize,” “we,” or “us”) is currently operated by the Decize team. Questions about this policy can be sent to support@decize.app.
What we collect
- Account data: authentication identifiers, email address, display name, and session information for people who sign in.
- Organization data: workspace name, member names and email addresses, roles, organization values and goals, capture settings, and integration settings.
- Decision data: titles, summaries, owners, dates, forecasts, approvals, outcomes, lessons, source messages, and AI-generated organization analysis.
- Inbound communication: email message content and delivery metadata when mail is sent or forwarded to a workspace capture address.
- Operational data: audit events, request logs, error details, and aggregate product analytics used to secure and improve the service.
We do not sell data or use it for advertising.
How we use data
- Provide and secure organization workspaces.
- Capture, organize, search, and report on organization decisions.
- Generate the AI analysis, summaries, themes, and related-decision recall requested by a workspace.
- Send capture replies, outcome prompts, and organization digests.
- Prevent abuse, diagnose failures, and improve reliability.
Workspace access
Decisions belong to an organization workspace, not to an individual journal. Every member of a workspace can read all of its decision records; roles govern what each can change. Owners and managers can manage membership, settings, exports, and organization data. Database row-level security separates organizations on reads, and server-side code scopes each write to its organization.
AI processing
Decize sends the content needed for an AI feature to Anthropic (Claude), with Google Gemini available as a fallback provider. Related-decision embeddings are generated on our own server with an open-source model, so that step sends nothing to a third party. Inputs can include decision and email text, relevant organization values and goals, and compact related records. One check runs without being asked: when a decision is saved, opened or downloaded, Decize asks the AI provider whether each of its closest past decisions (at most three) is about the same thing, sending the newer decision’s title and summary and the earlier one’s title, date, outcome, lesson and whether it is still in force, and keeps the answer so the same pair is not sent again. A past decision checked this way can turn out to be unrelated; it always comes from the same workspace. We don’t train AI models on your decisions.
If we switch on AI evaluation, TypeSafe (typesafe.ai) also receives the text of an emailed outcome reply, with the titles, decision dates and short summaries of the decisions it might be about, so its reading can be compared with ours. Its answers are stored for evaluation only and are never shown or acted on. Evaluation is off by default.
Where data is stored
Your decision log is stored in a Postgres database on a server we rent from Hostinger in Boston, in the United States. The server’s disk is not encrypted at rest. Copies also exist in our nightly database backups, kept on that server for 14 days; in Hostinger’s weekly backups of the whole server, which it stores separately; in mail handled by Resend; in our Hostinger support mailbox; and for about an hour in the server’s cache of AI-written summaries. Until 28 October 2026 the log was stored with Supabase in AWS us-east-1 (N. Virginia); a copy as it stood that day remains there, and another with the operator, until we delete them. Email sent to a workspace capture address, and the email Decize sends, pass through Resend, which processes them in AWS ap-northeast-1 (Tokyo). The emails Decize sends stay in the recipients’ mailboxes. Replies sent to support@decize.app or to our send-only addresses go to Hostinger instead. AI requests are processed by the providers listed below. This describes where data is kept today; it is not a data-residency commitment.
Service providers
Handle decision content
- Hostinger — the server in Boston, US, that runs Decize: the application, database, sign-in, background jobs, embeddings, and backups.
- Google and Anthropic — AI model processing.
- Resend — outbound and supported inbound email delivery.
- Slack: when your workspace connects it, the text after /decision, a message someone logs with “Log as decision”, and the thread where someone tags @Decize, read at that moment and only when someone tags @Decize, plus the names and email addresses of the people in it.
- Supabase — our database host until 28 October 2026. It keeps a copy of the data as it stood that day until we delete it; nothing new reaches it.
Billing only
- Dodo Payments — payment processing and subscription billing.
Dodo Payments receives the workspace owner’s email address and a workspace identifier from us. It collects card and billing details directly on its own checkout page, and Decize never sees or stores them. It never receives decision content.
Off unless we switch it on
- TypeSafe — optional AI evaluation, only when switched on.
It is off today. If we switch it on, it applies to every workspace; there is no per-workspace setting.
Site infrastructure
- Hostinger — also our domain DNS and our support mailbox, which receives replies sent to support@ or to our send-only notifications@ and reports@ addresses. A reply can quote the Decize email it answers.
- Cloudflare Turnstile — bot check on the sign-in and refund forms, when enabled. It sees the visitor’s IP address and browser signals.
Cookies
Decize uses essential session storage and cookies for sign-in and security. We do not use advertising cookies, cross-site advertising trackers, or a third-party analytics service.
Retention, export, and deletion
Organization data is retained while the workspace is active and as needed for security, legal, and backup purposes. Owners and managers can delete decision records and export organization decisions on every plan. Workspace owners can delete the whole workspace from Settings at any time. Workspace owners can also choose, in Settings, to have Decize remove the text of emails sent to it after 30, 90 or 365 days; by default it is kept. Decisions, outcomes and lessons are kept either way. Deleted data can remain in backups until they rotate. Deleting a decision erases the text of the emails linked to it, including replies in its thread that changed it or reported how it went; other messages in the thread keep their text. Deleting in Decize does not recall emails it has already sent, or anything already sent to the service providers listed above. Account deletion requests can be sent to support@decize.app. We may need to confirm that the requester has the authority to delete the data.
Your rights
Depending on where you live, you may have rights to access, correct, export, delete, or restrict processing of personal data. Contact support@decize.app to make a request. If your data is controlled by your employer or another organization, we may direct the request to that organization.
Children
Decize is intended for workplace use and is not directed to children under 16.
Changes and contact
We will revise the date above when this policy changes. For security details, see Security. For privacy questions, email support@decize.app.