Approved
Google API Services
Google approval is complete.
Avery uses Google data for user-facing scheduling features under the Limited Use requirements: no ads, no market research, and no general-purpose model training.
Trust
Avery can handle scheduling because the boundaries are clear.
Routine coordination can move quickly. Sensitive replies stay visible, and you can take over any time.
Visible trust model
Control before automation.
No outside reviewer queue
Avery is designed without outside humans reading your conversation to decide what it sends.
Review before sending
Draft Mode keeps replies visible while you learn how Avery behaves.
Pause or take over
You can stop Avery when you want to handle the conversation directly.
Boundaries
Know the boundaries before you connect anything.
Before Avery starts handling scheduling, you can see what it can access and what it is allowed to do.
Permission boundary map
Visible before setupArea
Avery can
Avery asks when
You control
Calendar access
Reads availability and conflicts for scheduling.
Availability is missing, conflicting, or ambiguous.
Choose connected calendars and update preferences.
Email replies
Drafts scheduling replies and can send simple, low-risk mail.
A reply is sensitive, uncertain, or needs your judgment.
Approve, edit, reject, pause, or take over.
Autonomy
Moves simple coordination forward.
Confidence drops or the next move deserves review.
Use Draft Mode, Smart Autonomy, and conversation controls.
Assurance
Proof before promises.
The proof is concrete: Google approval, CASA security review, SOC 2, and product controls users can see.
Completed
CASA security review
CASA security review is complete.
Avery has completed the application security review for the Google-connected surfaces that matter most: OAuth scopes, token handling, webhook security, abuse controls, and data boundaries.
Completed
SOC 2 program
SOC 2 is complete.
Avery has completed SOC 2 review for the operational controls behind the product, including access control, change management, logging, vendor review, and incident response.
Built in
Product controls
Avery's authority is visible to the user.
Draft Mode, clear pause reasons, take-over controls, and no outside reviewer queue make trust part of the product experience.
Avery signal
Privacy posture
No outside human reviewer decides what Avery sends.
Avery is designed without an external reviewer queue reading your scheduling conversations. When the next reply is ambiguous, sensitive, or could speak for you, the draft waits.
In practice
Trust comes from visible controls, not hidden human oversight.
Sending controls
Automatic for simple replies. Careful when it speaks for you.
Avery can handle low-risk coordination quickly. Sensitive or ambiguous replies stay in front of you.
Runs when it is routine. Pauses when it represents you.
Avery handles the repeatable work while keeping the exception boundary visible.
Draft ModeAvery does the work while sensitive replies wait before sending.Exception path
Smart AutonomyRoutine next steps can send automatically when confidence is high.Routine only
Take overPause Avery and handle the conversation yourself.Any time
Visibility
When Avery pauses, you can see why.
The app explains what Avery noticed, why a draft is held, and what it would do next.
Activity
Avery is moving the thread forward.
Activity viewAvery is drafting a follow-up for the investor intro.Drafting
Review reasonA new constraint changed the proposed time.Held
Preference tuningUse Draft Mode for external scheduling threads.Rule
Pause detail
Why Avery is asking first.
1Changed constraintA participant ruled out the original window.
2Draft preparedAvery found a better time and wrote the reply.
3User choiceApprove, edit, take over, or adjust the rule.
Request access
See the controls before Avery handles a thread.
Know what Avery can access, what it can send, what waits for you, and how you can take over before you connect anything.