Disclosure and privacy
Who runs Praxis
Praxis (praxisgj.com) is the internal client operations tool of Griffin Jacobs Consulting, Grand Junction, Colorado. It is used by our team to run client engagements. It is not a product offered to the public, and there is no public sign-up.
Who can sign in
Only team members with an account created by the owner can sign in. Each person has their own account with their own password. Every change made in Praxis is recorded against the account that made it, and the owner can end any account's access at any time.
What we collect from clients
- Intake answers. What a client tells us about their business through the intake form: contact details, the business, its goals, and the materials they choose to share.
- Working notes and recordings. Notes from calls and meetings, and, where a client has agreed to it, recordings and transcripts of those conversations.
- Documents we produce. Audits, plans, presentations and agreements prepared for the engagement.
- Prospect research. For businesses we may contact, publicly available information such as a website, a listing, and how answer engines describe the business.
How we use it
To deliver the engagement the client asked for: understanding the business, preparing the work, sending the documents, and following up. We do not sell this information and we do not share it with anyone outside the engagement, other than the service providers that host and process it for us.
Service providers
Praxis runs on Vercel (hosting), Supabase (database and file storage), Google Workspace (email and document storage), OpenRouter (AI drafting and summarising), Slack (team messaging), Cal.com (scheduling), Resend (system email) and Plaud (call recording, only for team members who connect one). Each holds only what its job requires.
Google account access
A team member may choose to connect their own Google Workspace account to Praxis. When they do, Praxis uses that access for four things: sending email to clients from that team member's own address, so a client hears from the person they are working with; placing a prepared email into that team member's own drafts for them to review and send themselves; reading, in that team member's inbox, only the notification emails Adobe Acrobat Sign sends when an agreement is signed (found by sender and subject) and the signed PDF attached to them, in order to record the signature and file the executed contract; and reading that team member's own primary Google calendar for the next thirty days, so the meetings already on it appear alongside the meetings booked in Praxis on one shared team calendar. Praxis does not read, store or display any other mail.
What Praxis keeps from a calendar is the title, the start and end time, and which team member's calendar it came from. It does not store guests, attachments, conference links or the body of an invitation, and it does not read any calendar other than that team member's primary one. Events marked all day, and invitations that team member has declined, are not copied at all. A calendar entry copied into Praxis is visible to the team, so a team member who does not want a personal appointment shown to colleagues should not connect a calendar that holds one, or should decline the connection.
Praxis requests permission to send mail, permission to create and manage drafts, permission to read mail, and permission to read calendars, each used only as described above. The calendar permission is read only: Praxis never creates, changes, moves or deletes anything on a team member's Google calendar, and a meeting booked in Praxis is not written back to Google. Praxis does not read a team member's contacts or files, it cannot label, archive or delete anything in a mailbox, and it does not use Google account data for advertising, profiling, or training AI models. Documents produced for an engagement are stored in the company's own Google Drive, not in a team member's. A team member can disconnect their Google account from Praxis at any time from Settings, which stops the calendar copy and removes the calendar entries already copied, and can also revoke access from their Google account's security page.
Praxis's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Security
Praxis is served only over HTTPS. Sign-in uses individual passwords stored as salted hashes, sessions expire, and repeated failed sign-in attempts are limited. Google access tokens are stored encrypted. The database is not reachable from the public internet.
Retention and your choices
We keep engagement records for as long as we work with a client and for our own records afterwards. A client may ask us to correct information or to delete their records, and we will do so unless we are required to keep them. Write to griffin@griffinjacobs.com.
Changes
If this statement changes, the date at the top changes with it.