The short version
- Your community's records live in a separate Supabase project. During the free five-day trial, it is temporarily hosted by DAAS. When you subscribe and complete the claim, it transfers to your own Supabase organization. After you claim it, DAAS keeps no login, key, or access token for it. DAAS staff do not view, export, or use your claimed workspace's records.
- DAAS does not sell your records, use them for advertising, or use them to train AI models.
- The trial includes limited DAAS-funded AI usage. Paid AI uses your organization's own OpenAI account (and Anthropic, if you connect it). Nothing AI drafts is sent or saved without your approval.
- You own your records and can export them. Closing DAAS does not delete a database you have claimed into your own Supabase account.
Privacy Policy
1. Who we are and what this covers
DAAS is a relationship CRM for community organizations. In this policy, “DAAS,” “we,” and “us” mean the operator of DAAS, reachable at admin@daascrm.app. “Your organization” means the community that uses DAAS, and “users” are the people it authorizes to sign in.
Your organization decides what information goes into its workspace, why, who can see it, and how long to keep it. If you are a member of a community that uses DAAS and have a question about your record, please contact that community directly. This policy does not replace a community's own privacy notice.
2. Information DAAS handles
- Signup and support. When your organization sets up DAAS, we receive the details entered during setup, such as names, email addresses, the organization's name, address, and sending domain, plus any messages you send us.
- Workspace directory. We keep a record of which workspace each sign-in email belongs to, so the app can send you to the right place when you log in.
- Setup status. While a user is signed in, the app reports yes/no setup checks to DAAS, such as whether AI and payment keys are connected, whether your community notes are filled in, which forms address is in use, and which DAAS version is running. These checks never include record contents or key values.
- This website. The DAAS website does not use analytics, advertising trackers, or cookies. The app keeps your sign-in and settings in your browser. Fonts are loaded from Google Fonts, which receives standard request information such as your IP address.
Your contacts, households, notes, interactions, giving history, events, and messages stay in your organization's separate database. During a free trial, that database is temporarily hosted by DAAS, and included AI requests are processed through DAAS's sponsored AI service. After you complete the claim, the database belongs to your own Supabase organization.
3. Where your data lives
There is one shared DAAS app at daascrm.app. Each organization gets its own private Supabase project with its own database, logins, and server functions. During the free five-day trial, your separate workspace is temporarily hosted by DAAS and includes limited DAAS-funded AI usage. You can add real contacts during the trial. When you subscribe and complete the claim, the project transfers to your Supabase organization and paid AI uses your own API account.
After you claim your workspace, DAAS keeps no login, key, or access token for it. DAAS staff do not view, export, or use your claimed workspace's records. Updates to the shared app reach you automatically.
Database updates. Your workspace keeps its own database up to date. About once an hour, and whenever someone signs in, it checks daascrm.app for new database updates, such as a new table, and installs any it doesn't have yet. It installs only updates signed with DAAS's private key. It also checks each update for commands that could send data out of your workspace, read your stored keys, or create a new login, and refuses any update that contains them. Every update is listed in Settings → DAAS updates with a plain-English description and the exact SQL it ran. The full list is public at daascrm.app/updates/manifest.json.
Server function updates. Some updates also change the server functions in your workspace. A function can't update itself, so an administrator in your organization approves these on Supabase. That approval lets DAAS install the new functions once. DAAS then revokes it and does not keep the token.
As with any software you run, you are trusting the DAAS app and its updates with your records. That is why every update is signed, listed in your workspace, and published.
New workspaces are created in a Supabase region in the Americas. Your workspace's exact region is shown in your Supabase dashboard. Some connected services listed below may process information in other locations.
Separate projects keep each organization's records apart from every other organization's. Within your workspace, every user your organization authorizes can see your organization's records, so add only people you trust with them.
4. AI features
DAAS uses AI to draft, summarize, search, and research. The free trial includes limited DAAS-funded AI usage without requiring your own API key. Trial requests go through DAAS's sponsored AI service. Paid AI features run on your organization's own API keys: OpenAI is required, and Anthropic is optional. Those keys are stored in your workspace and are never sent to the browser. Paid requests travel like this:
Depending on the feature, a request can include your question, the contacts or households involved, related notes and history, and anything you upload or record. In particular:
- Search indexing. To make semantic search work, saved interaction and household notes are sent to OpenAI to create search vectors. This happens automatically after a note is saved or edited, and on an hourly schedule, even if no one opens an AI chat.
- Voice notes. Recordings you submit are sent to OpenAI for transcription.
- Research. Research features can run web searches through Anthropic when it is connected.
- Your approval. Messages, records, and other changes that AI drafts are not sent or saved until a user approves them.
Paid requests fall under your organization's own OpenAI and Anthropic accounts, their terms, and account settings. Included trial requests use DAAS's provider account and its settings. Both providers state that data sent through their APIs is not used to train their models unless the account owner opts in. Providers may still keep API data for a limited time, for example for abuse monitoring. See OpenAI's API data controls, Anthropic's training policy, and Anthropic's retention policy.
The Daily Five and Prospect Score are calculated by rules inside DAAS, not by an AI model.
5. Services that receive information
Each service receives only what the feature in use needs.
| Service | What it does and what it receives |
|---|---|
| Supabase | Your separate database, logins, and server functions, temporarily hosted by DAAS during the trial and transferred to your own Supabase organization when you complete the claim. DAAS's own setup service also runs on Supabase. |
| OpenAI | AI features, voice transcription, and search indexing. Included trial usage uses DAAS's provider account; paid usage uses your organization's account. |
| Anthropic | AI and web research, on your organization's account, if connected. |
| Amazon Web Services | Email delivery through Amazon SES, on an account DAAS operates. Amazon processes message content, recipient addresses, and delivery, open, and click events, which are returned to your workspace. |
| Stripe | Payments on your forms, through your organization's own Stripe account. Card details go directly to Stripe and never touch DAAS or your database. |
| Cloudflare | Hosts your public forms page. Submissions go straight to your workspace. Also runs the Turnstile security check on trial sign-up, on the DAAS sign-in page, and on donation and event forms. |
| GitHub Pages | Hosts the DAAS website, the app code, and the signed list of database updates. It does not receive your records. |
| Property data | When a user requests property details, the household's address is sent through a DAAS service to a property-data provider (via RapidAPI). DAAS does not store these lookups. |
| OpenStreetMap | Map images, and turning addresses into map locations. |
| Website fonts. Google Maps opens only when a user taps a map or directions link. |
We may also disclose information when required by law or to address fraud or security threats. Your organization's own exports and messages go to the recipients it chooses.
6. Email your organization sends
Emails your organization sends through DAAS can include open tracking and tracked links. Your organization chooses whether to use them and is responsible for its mailing lists. Every campaign includes an unsubscribe link, and unsubscribe requests are honored by that organization's workspace.
7. Security
How we protect your information, and how to report a concern, is described in the Security section below.
8. Retention, export, and deletion
Your organization controls how long its records are kept. Records you delete may remain in your Supabase backups until those backups expire under your Supabase plan. Records you export are yours to protect.
Closing DAAS does not delete a database you have claimed into your own Supabase account. An unclaimed trial is temporarily DAAS-hosted; contact us about access, export, or deletion of a hosted trial. Export what you need, then delete the project in Supabase if you no longer want it. We keep signup and account information for as long as your organization uses DAAS and afterward only as long as needed for legal, financial, or security reasons.
9. Your choices and rights
Depending on where you live, you may have the right to access, correct, delete, or get a copy of your information, or to object to certain uses. For information DAAS holds about you, email admin@daascrm.app; we may need to verify your identity. For a community's records about you, contact that community, and we will help it respond.
10. Sensitive information and children
Community records can reveal sensitive details, such as religious life, family circumstances, or personal needs. Organizations should record only what they need. DAAS is not designed for medical records, government ID numbers, or full card numbers, so please do not store them.
DAAS accounts are for adults authorized by their organization. Organizations may record information about families and children only with the appropriate authority and permissions.
11. Changes to this policy
When our practices change, we will update this page and its effective date, and give additional notice of significant changes where required.
Security
This section explains how DAAS protects your community’s information. It starts in plain words, then gives more technical detail for anyone who wants to check our work. It is part of the Privacy Policy above.
The plain-English version
- Your records live in their own private database, apart from every other DAAS customer’s. Once you claim it, DAAS keeps no access to it.
- Card numbers go straight to Stripe. They never reach DAAS or your database.
- Your AI, Stripe, and email keys are kept in encrypted secret storage. The app tells you a key is connected, but never shows it.
- Every database and server-function update is digitally signed, listed in your workspace, and published for anyone to read.
- Every change runs through automated tests and a separate practice site before it is released.
- Everything travels over encrypted HTTPS connections.
What you can do
- Give each person their own login, and use a strong password that you don’t use anywhere else.
- Add only people you trust. Everyone your organization authorizes can see all of its records.
- When someone leaves your team, have their login removed promptly.
- Sign out on shared computers, and keep your Stripe, OpenAI, and other keys private.
How it works, in more detail
| Area | What we do |
|---|---|
| Separation | Each organization has its own Supabase project, with its own Postgres database, logins, and server functions. New workspaces turn on row-level security for every table. The anonymous (signed-out) role can read only the list of active forms and a limited set of event fields, and can add push-notification sign-ups. Everything else requires a signed-in user of that workspace. Self-service sign-up is switched off in each workspace, so only people your organization invites can sign in. |
| Sign-in | Handled by Supabase Auth, with one login per person. Supabase stores login passwords only as salted hashes. The app asks for the current password before it changes one. The sign-in page runs a Cloudflare Turnstile check, and workspaces where it is turned on refuse password sign-ins and reset emails that skip it. |
| Keys and secrets | AI, Stripe, and email keys are stored in your workspace’s Supabase Vault. Only server functions can read them, and the browser never receives a key value. Scheduled jobs authenticate with a random secret from the Vault rather than a long-lived administrator key. |
| Payments | Card details are typed into Stripe’s own payment fields and go directly to Stripe, so DAAS and your database never handle card numbers. The server re-checks donation amounts and records the amount Stripe confirms. Stripe’s notifications are signature-verified, and each payment is recorded once. |
| Public forms | Donation and event forms reach your workspace only through server functions that accept a narrow set of inputs and limit how often one visitor can submit. A Cloudflare Turnstile check on every donation and event form stops automated submissions, such as bots testing stolen cards; DAAS checks each answer with Cloudflare, and the check’s secret key is never stored in your workspace. Visitors’ IP addresses are not saved; the submit limit keeps only a short code made from the address with a secret key, so it can’t be turned back into the address. The forms page limits what it can load and where it can send information. Trial sign-up on this website is protected by Cloudflare Turnstile. |
| Sent through Amazon SES. Bounce and complaint notices are checked against Amazon’s signature before they are trusted. Unsubscribing takes one click, and a mail scanner opening the link does not unsubscribe anyone. | |
| Updates | Database and server-function updates are signed with a private key that is not kept on the servers that publish the site. Each update is checked against its checksum and screened for commands that could send data out of your workspace, read your stored keys, or create a login, then applied as a single step that is undone if anything fails. An administrator in your organization approves server-function updates. Every update is listed in Settings → DAAS updates and at daascrm.app/updates/manifest.json. |
| Testing and release | Changes are first published to a separate practice site that uses made-up data and test payment keys. An automated test suite runs on every change before it is released. The credential used to publish the site is limited to one repository and expires. We also review the code for security before launch and after significant changes. |
| Encryption | Traffic to DAAS, Supabase, Stripe, and Amazon SES uses HTTPS. Supabase encrypts database storage at rest. |
| Our own access | After you claim your workspace, DAAS keeps no login, key, or access token for it, and DAAS staff do not view, export, or use its records. During the free trial, DAAS temporarily hosts your workspace. |
Reporting a concern
No system is perfectly secure. If you think you have found a security problem, email admin@daascrm.app with the feature involved, the approximate time, and the steps to reproduce it. Please do not include real constituent records, passwords, or keys, and please do not access or change anyone else’s data while testing. We read every report. Where the law or an agreement requires it, we will notify affected organizations of a security incident.
Terms of Service
1. Agreement
These terms apply to the DAAS website and service. “You” means the organization using DAAS and its authorized users. By using DAAS, you agree to these terms. If you accept them for an organization, you confirm that you have authority to do so. A separate signed agreement controls where it conflicts with these terms. The Privacy Policy above explains how information is handled.
2. Your account and workspace
You are responsible for accurate setup information, for choosing who can sign in, for keeping logins private, and for telling us promptly about any suspected unauthorized access. Your workspace's Supabase project belongs to your organization after you claim it, and you are responsible for that account, including its billing and continued availability. Your workspace installs DAAS database updates automatically, as described in the Privacy Policy. Updates to its server functions install only after an administrator in your organization approves them.
3. Your data
You own the information you enter, import, or create. You allow DAAS to process it only to provide the service and follow your instructions. You are responsible for having the right to collect, contact, and keep information about the people in your records, including any notices or permissions the law requires. Publicly available information still requires care.
4. Acceptable use
Do not use DAAS to break the law, send spam or unlawful messages, harass anyone, infringe others' rights, spread malware, get around access controls, try to reach another organization's records, or disrupt the service. You are responsible for your mailing lists, your permission to contact recipients, your message content, and honoring unsubscribe requests.
5. AI features
AI output, summaries, and research can be wrong or incomplete. Review them before relying on them, saving them, or sending them. They are not legal, financial, medical, or other professional advice. You remain responsible for the messages you send, the records you change, and the transactions you start, including those you approve from an AI draft.
6. Connected services and payments
Connected services, including Supabase, OpenAI, Anthropic, Stripe, and Amazon, have their own terms, charges, and availability, which DAAS does not control. Charges on accounts your organization owns are your responsibility. Your organization is responsible for its forms, amounts, receipts, refunds, tax statements, and any disputes with the people who pay or register through them.
7. Fees
The price for DAAS, and what it includes, is stated when your organization signs up. We will tell you before any price change applies to you. You can cancel at any time by emailing admin@daascrm.app.
8. Availability and changes
DAAS may occasionally be unavailable because of maintenance, provider outages, or other causes, and we do not guarantee uptime. We improve the app regularly and will give reasonable notice of significant changes. Keep an export of records that matter to you.
9. Suspension and closing
We may restrict access to address unlawful use, a serious violation of these terms, nonpayment, or a security threat. Where practical, we will explain why and give you a chance to fix it first.
When you cancel, your database stays in your organization's Supabase account. Closing DAAS does not delete it, end its Supabase charges, or erase its backups. Export what you need and delete the project in Supabase when you are ready.
10. Our software and your feedback
DAAS keeps its rights in the software, design, name, and documentation. You may use them as part of the service. If you send us suggestions, we may use them to improve DAAS without obligation to you. Please do not include constituent information in feedback.
11. Warranties and responsibility
Except as stated in a separate agreement, and to the extent the law allows, DAAS is provided as is and as available, without a promise that it will be uninterrupted, error-free, or right for every purpose. We do not guarantee the accuracy of AI output, outside research, or information entered by users. Nothing in these terms limits rights that cannot be limited by law.
12. Changes and contact
If we update these terms, we will post them here with a new effective date and let you know about significant changes. Changes apply going forward. If you have a concern, email admin@daascrm.app and we will work to resolve it. If any part of these terms is unenforceable, the rest still applies.