Gevie Gevie
How it works Capabilities Pricing
Log in Get started

Privacy Policy

Last revised 30 October 2026. This revision follows an adversarial review and a read-only inspection of Gevie's source code.

Effective 30 October 2026. Questions: contact@gevie.ai.

1. Who we are and what this policy covers

Gevie is a retail operations assistant operated by Geviemart LLC ("Gevie", "we", "us", "our"). The contracting entity is Geviemart LLC, 2200 SE J St, Suite 6, Bentonville, AR 72712. Contact us at contact@gevie.ai.

This policy explains how we collect, access, use, disclose, retain and delete personal information through Gevie's marketing site, account console, web application, desktop and mobile applications, connected integrations and related support services (together, the "Services"). Gevie is initially offered to businesses in the United States.

It covers visitors, prospective customers, account owners, workspace members and other people whose information is processed through the Services. It concerns Gevie, not purchases made through Geviemart's separate grocery retail operations. Gevie's separate pre-launch sign-up site is not covered here; that site publishes its own privacy notice.

For account administration, billing, security and our own customer relationships, Geviemart LLC determines how personal information is used. When we process information from a merchant's connected systems or submitted business records on that merchant's behalf, we act on the merchant's instructions and applicable agreements. The merchant remains responsible for its own privacy notices and for having authority to provide that information. Legal roles, meaning controller, processor, service provider or contractor, depend on the applicable law and the processing activity.

2. Information we collect or access

What is involved depends on the features you use, the systems you connect, the permissions you grant and what you submit.

We limit point-of-sale ingestion to supported fields rather than importing everything available. The current ingestion design excludes buyer names, buyer contact details, order notes and fulfilment addresses, and does not import staff names or contact details from point-of-sale records. Workspace members' names and emails come separately, from account and sign-in processes. An allowlist at the point where data enters maps only permitted fields and drops the rest, and automated tests verify this. Raw point-of-sale payloads are not archived by default.

These exclusions do not mean Gevie never processes personal information about customers, staff or suppliers. Such information can appear in uploaded documents, email, conversations, product descriptions or other content you provide. Identifiers may also be personal information when reasonably linkable to an individual, and sole-trader business information may identify the individual operating the business.

Please provide only what the task needs. Do not submit passwords, full payment-card details, government identification numbers, health records or similarly sensitive information unless a supported feature expressly requires it and you have the necessary authority.

3. How we use information

We use information to provide and administer the Services: to create accounts, authenticate users and manage workspaces, memberships and permissions; to retrieve and synchronise authorised business information and generate sales, inventory, purchasing, receiving, pricing and other supported insights; to respond to text and voice requests, process uploaded documents and prepare recommendations or proposed actions; to carry out approved point-of-sale changes and other enabled actions within the controls applicable to each feature; to provide billing, support, service notices, troubleshooting and account administration; and to maintain security, investigate abuse or failures, and comply with applicable legal obligations.

Connected email information is used to support the user-facing feature you requested. Access to a connected account is not permission to use its contents for unrelated purposes. We do not sell your data, and we do not use your connected business data to advertise to you or your customers. Preparing marketing content at your direction is a service you request, not permission for Gevie to use that data for its own advertising. Restrictions that apply to connected-service information continue to apply to summaries, extracted facts and other derivatives, and authorising a task does not permit a use the connected service's own requirements prohibit.

4. Connected services and approval controls

Point of sale. Square is the point-of-sale platform Gevie offers at launch. Support for Clover and Lightspeed is built but deferred, and neither is offered when you connect an account. Section 7 names Square only, and will name the others before either is offered to merchants.

Every point-of-sale write requires approval from a user authorised for that operation in the relevant workspace before Gevie writes the change. Approval covers the specific change, or the clearly identified batch, presented for review. A material change to the proposed operation requires renewed approval. Connecting an account or granting OAuth permissions does not by itself approve individual writes. Read access supports retrieval, synchronisation and the preparation of recommendations.

Email. Gevie's optional Gmail and Outlook connection is two separate consents, and granting one does not grant the other:

Both are enforced in code: each grant is checked against its permitted scope, and a grant that reaches further than its tier is refused. Mail is read at the moment a feature needs it. What Gevie keeps from a reply, such as an extracted fact, a summary or a task record, follows the retention of the record it is kept in.

Publishing. Where marketing publication is enabled, Gevie prepares content for review and publishes only after your explicit approval. Scheduled posts can be cancelled before they publish. Retracting published content depends on what the connected platform allows; it cannot guarantee removal of copies already viewed, downloaded or shared.

You can disconnect integrations or revoke permissions at the connected provider. Disconnecting stops Gevie's ability to use that connection, subject to the processing needed to recognise the revocation. It does not undo previously approved point-of-sale changes, delete records held by the original provider, or remove material already published elsewhere.

5. AI and voice processing

Gevie uses OpenAI for its AI assistant, for understanding uploaded images, for generated marketing imagery and for live voice conversation. Depending on the request, we transmit relevant conversation content, voice input, uploaded content and information retrieved from connected services to OpenAI so it can process the interaction and produce a response.

Gevie's two voice features use different providers, and it matters who receives your audio:

Gevie does not retain audio captured through its voice features. Audio is processed to provide the interaction and is not persisted by Gevie. Text transcripts, assistant responses and associated voice-message metadata, namely duration and a simplified waveform, may be saved with the conversation and follow its retention lifecycle in section 9. What each provider retains of the audio it receives is governed by that provider's own terms.

OpenAI processes information under the API arrangements applicable to Gevie's account, and its retention depends on the features and settings in force on that account. Provider-hosted content that Gevie creates and controls is included in our deletion procedures, through the controls the provider makes available. Providers may separately retain limited records for security, abuse prevention or legal obligations under their own terms, on a schedule different from Gevie's. Using a provider does not remove Gevie's own responsibilities under applicable law or this policy. See OpenAI's API data controls; consumer ChatGPT settings do not describe Gevie's API configuration.

Google-connected information is additionally subject to section 6.

AI output can be inaccurate, including about people. Review outputs before using or sharing them, and contact us if you need correction or deletion of personal information Gevie processes.

6. Google user data and limited use

Gevie's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the applicable Google Workspace API User Data and Developer Policy, including their Limited Use requirements.

Google-connected information is used for the authorised features presented to the user. We do not use it for advertising, sale to data brokers, creditworthiness assessment, or training or improving general-purpose AI models. Transfers are restricted to those Google's policies permit, including processing needed for the authorised feature, security or legal compliance.

Human access to Google user data is limited to circumstances those policies permit, such as your documented agreement to access specific content for support, security investigation or legal requirements. Any transfer of Google user data in a merger, acquisition or asset sale must also meet Google's applicable requirements, including prior explicit consent where required. These restrictions apply equally to information derived from Google user data.

7. Who we share it with

We use a limited set of service providers to run Gevie, and we do not otherwise share your data:

We may also disclose information where reasonably necessary to comply with law or valid legal process, protect rights and safety, investigate fraud or security incidents, or address legal claims. We do not disclose identifiable merchant business content to prospective investors for ordinary fundraising. For an actual or proposed merger, acquisition, reorganisation or sale, we limit any disclosure to what the transaction requires, apply confidentiality and access restrictions, and honour this policy and applicable law; Google user data remains subject to its separate transfer restrictions, including any required prior explicit consent. We may also disclose information at your direction or with your consent.

Providers that process information on our behalf are bound by applicable agreements and restrictions. A connected service may separately process information for its own purposes under its own policy. This policy does not replace the privacy policies of your point-of-sale provider, email provider, payment provider or other services you use independently.

8. Workspace access and merchant responsibilities

We do not use a merchant's non-public business content to operate or compete through Geviemart's grocery business, and we do not disclose it to another merchant for that merchant's commercial benefit. Personnel access is limited to authorised service, support, security and legal purposes. Any optional cross-merchant benchmarking or additional use would be described separately before introduction, and would require the permissions law, contract or connected-service rules mandate.

Owners and authorised administrators manage workspace memberships and capabilities. What you submit in a business workspace may be accessible to other authorised members according to the product's access controls. Do not assume content submitted in an employer's or merchant's workspace is private from every administrator or authorised colleague.

Merchants are responsible for granting appropriate access, removing it when no longer needed, and providing required notices or obtaining required permissions from staff, customers and suppliers. If your information was provided through a merchant using Gevie, that merchant is generally the first point of contact for requests about its records, and we will assist as applicable law and our agreements require. A merchant's responsibilities do not limit Gevie's own obligations: Gevie handles requests about information it controls for account administration, billing and its own relationship with you directly, and coordinates merchant-directed requests with the merchant.

9. How long we keep it

Account, billing, support and security records are kept for the period reasonably necessary for their specific purpose, taking account of administration, recordkeeping requirements, disputes, fraud prevention and legal obligations. Where retention is legally required we limit what is retained to what that purpose needs. These exceptions do not authorise routine indefinite retention of all business content.

10. Deleting your data and disconnecting

You can request deletion of stored business data by emailing contact@gevie.ai, including while an integration is still connected. The 30-day recovery period applies to ordinary disconnection; a verified deletion or account-closure request is handled under its own procedure and legal deadlines, and the recovery period is not a reason to delay a valid deletion request. Deleting stored business data does not itself revoke credentials. An active connection may allow data to be retrieved again, so disconnect the integration too if you want to stop future access.

When you disconnect a point-of-sale integration, its credentials are destroyed immediately and its associated business data enters a 30-day recovery period, after which it is purged from active systems including derived metrics and snapshots. If you revoke access directly at the provider, the same process begins when Gevie detects the revocation.

Purged data may remain in encrypted backups until those rotate out, on the windows given in section 9.

Deleting an account, deleting particular content and disconnecting one integration are different requests, and cancelling or archiving a subscription is not by itself a completed deletion. Tell us which outcome you want so we apply it to the correct scope. We may verify identity and authority before acting, and we explain any applicable legal retention exception when we respond, where we are permitted to.

Deletion in Gevie does not remove the original records from your point-of-sale or email provider, and does not reverse approved changes. Our deletion procedures cover provider-held content that Gevie creates and controls, through the controls that provider offers and subject to the retention exceptions in section 5. Contact us about those copies rather than treating a reference to a provider's policy as transferring the responsibility to you.

11. Security

Gevie uses administrative and technical safeguards designed to protect information, including encryption in transit and at rest, workspace-scoped access controls, and protection of integration credentials. Point-of-sale credentials are held in a per-tenant encrypted vault, so each merchant's credentials are protected under their own key. Every stored record is tagged to your tenant and all access runs through a tenant-scoped data layer with no cross-tenant query path in application code; automated tests check this. Backups inherit the same encryption, and no merchant data beyond opaque identifiers appears in our logs.

No system can guarantee absolute security. Keep your sign-in credentials safe, review connected permissions, and contact us promptly about suspected unauthorised access. We investigate security incidents and give notice where applicable law or contract requires it. Gevie does not currently hold SOC 2 or comparable certification.

12. Cookies, local storage and technical information

The web application uses browser storage to support sign-in and conversation continuity. That can include refresh-session information and a local copy of the active conversation, including its text. These device-held copies are separate from the server's conversation retention: clearing site data removes the browser-held copies on that device and may sign you out or interrupt continuity, and a deletion on the server does not instantly clear an offline device.

This marketing site runs no analytics and no advertising tags. It loads typefaces from Google Fonts, and the sign-up page loads Stripe's browser integration; both receive the technical request information, meaning IP address and user agent, needed to serve those resources. Gevie's separate pre-launch sign-up site does use analytics and offers a per-browser opt-out; that site's own privacy notice describes it.

Mobile push notifications use a device push token and the notification content. Your browser and device settings let you restrict storage, microphone access or notifications, though some features will then be unavailable. Text interaction remains available without microphone access.

13. Your choices and privacy requests

You can request access to, correction of, or deletion of personal information by emailing contact@gevie.ai. You can also revoke connected-service permissions and manage device permissions. Depending on your location, the applicable law and Gevie's role, you may have rights to obtain a portable copy, restrict certain sensitive-information uses, opt out of sale or targeted-advertising sharing, or appeal a decision on a request. These rights are subject to applicable exceptions, and listing them does not imply every privacy statute applies to Gevie.

Give us enough to identify the account, workspace and request, but do not email passwords or full payment-card details. We may ask for reasonable verification of identity or authority. An authorised agent may submit a request where permitted, subject to verification of that authority. We respond within applicable legal deadlines and explain any permitted extension or refusal.

To appeal where an appeal right applies, email the same address with "Privacy appeal" in the subject line and identify the original request. You may also contact your state attorney general or another competent regulator. We do not retaliate or unlawfully discriminate for exercising privacy rights.

If we process information solely on a merchant's behalf we may refer the request to that merchant or coordinate with them. Requests cannot be used to gain access to another person's information or another workspace.

14. Children and sensitive information

Gevie is a business service and is not directed to children under 13, and we do not knowingly collect personal information directly from children under 13. If you believe a child has submitted personal information, contact us so we can investigate and act. Merchants should avoid submitting children's or other sensitive personal information unless it is necessary, supported and lawfully authorised.

15. Where information is processed

Gevie's initial market is the United States. A United States launch does not mean all service-provider processing happens on United States infrastructure: providers may process information in locations their services and our configuration determine, subject to applicable agreements and legal requirements. This policy does not promise exclusive United States data residency.

16. Changes to this policy

We may update this policy as our Services, providers or obligations change. We post the updated policy and change its revision date. For material changes affecting registered users we give notice by in-product message or to the account email address before the change takes effect, unless different timing is permitted or required by law. Where a new use requires consent, including under an integration provider's rules, we obtain that consent before beginning it. Posting an update does not by itself supply consent where consent is required, and does not override existing restrictions on information already collected.

17. Contact

Questions or requests about your data: contact@gevie.ai.