1. Who operates CASE
CASE is a product of APEXXTECH GLOBAL LLC. For privacy questions or requests about your CASE information, contact contact@apexxtech.io.
2. Account and workspace information
When you sign in with Google, CASE receives your Google account identifier, verified email address and name. Signing in alone does not connect your mailbox. CASE stores information you enter into your business workspace, including its name, clients, contacts, invoice records, supporting references and activity history.
3. Connecting company Gmail
Gmail authorization is a separate choice. You select a company mailbox and Google asks for read-only permission. CASE checks that the account you authorize matches the mailbox selected for your workspace.
CASE searches for relevant business correspondence, including invoice, purchase-order, work-order, quotation, bid, payment and dispute messages. The current integration stores message and thread identifiers, sender information, subjects, received times, bounded message snippets and the filing decisions that associate evidence with a client or invoice. It does not download Gmail attachments or store complete email message bodies through its current collection feature.
CASE’s Gmail integration does not send email, change labels or delete original messages. Recent collection covers a bounded date range. Older evidence is collected when you explicitly choose an archive year.
4. How information is used
Information is used to identify your account, provide your business workspace, collect the evidence you choose to connect, associate it with client and invoice records, and show activity and follow-up context. Unknown senders and uncertain matches remain available for user review.
Saved Google access and refresh credentials are encrypted on the backend so you do not have to authorize every individual read.
5. Google API data and Limited Use
CASE’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Google user data is not sold, used for advertising or used to train general-purpose artificial-intelligence or machine-learning models. It is used for the user-facing workspace features described in this policy. Human access to Google user data is restricted to purposes permitted by Google’s policy, such as support with your consent, security investigations or applicable legal requirements.
6. Access and service providers
The workspace owner and members authorized for that workspace can access its business information according to their permissions. CASE uses service providers to operate the application, currently Vercel for hosting and Prisma Postgres for database services. Google processes sign-in, authorization and Gmail API requests. Providers may process information outside your country.
Information may also be disclosed when necessary to comply with applicable law or protect the service and its users. Access and disclosure of Google user data remain subject to the Limited Use requirements described above.
7. Disconnecting Gmail
From Connections, you can stop new collection, remove CASE’s saved Google credentials and ask Google to revoke CASE’s authorization for the selected account. If Google does not confirm revocation, CASE provides a link to manage access in your Google Account. Google revocation can affect other permissions previously granted to the same Google Cloud project for that account.
Disconnecting does not delete original mail in Gmail or evidence already imported into CASE. These are separate records with separate removal processes.
8. Retention and data requests
CASE stores workspace information to provide the workspace and its record history. Imported evidence is not automatically deleted when Gmail is disconnected. Saved Google credentials are removed from CASE’s application database when you disconnect Gmail.
You can request access, correction, export or deletion of stored CASE information by emailing contact@apexxtech.io. We verify the requester’s authority before releasing or removing business information. The scope and timing of a request can depend on account ownership, service-provider retention and applicable security or legal recordkeeping requirements. Contact us for information about a specific workspace or request.
9. Cookies and browser storage
CASE uses essential cookies for the Google authorization process and your signed-in session. The current application uses a short-lived authorization cookie and a session cookie with a maximum lifetime of seven days. Your browser may temporarily retain a business-name draft in session storage during onboarding. Google credentials are not stored in that browser draft.
Hosting providers may process technical request and error information to operate and protect the service.
10. Security
CASE uses HTTPS, server-side workspace access checks and encryption for saved Google credentials. These measures reduce risk but do not guarantee that all security incidents can be prevented.
11. Connecting WhatsApp Business
Where enabled, a workspace owner can authorize a WhatsApp Business account and phone number through Meta. CASE stores the account and phone identifiers, display number, business name and encrypted authorization token. CASE sends the number’s registration PIN to Meta during setup and does not retain it.
For a connected number, CASE receives message identifiers, sender details, timestamps, text excerpts, available attachment names and delivery statuses from Meta. CASE uses them to show conversations and file evidence. CASE sends a reply or approved template only when an authorized workspace owner chooses to send it. Meta processes account authorization, message delivery and related events.
You can remove CASE’s authorization through Meta. Imported records remain in CASE. See Retention and data requests for removal requests.
12. Changes and contact
When this policy changes, the updated version and date will appear on this page. Contact contact@apexxtech.io with privacy questions or data requests.