Information SOFRA handles
SOFRA handles account and workspace information such as your name, email address, role, restaurant brand, locations, and the configuration and activity you enter in the platform. Product features may also store menu, order, customer, website, launch, and operational records when you choose to use them.
When an authorized customer uses Launch Center to register a business, SOFRA stores the US legal business name, entity type, registered address, authorized representative contact details, and the operating locations assigned to that entity. The required Employer Identification Number (EIN) is encrypted on the server and shown in ordinary customer and staff views only as a masked ending. SOFRA does not collect identity documents, personal tax identifiers, or bank onboarding details in this form; those remain in the relevant payment provider's secure flow when required.
The public AI Growth Report can use a website address or a restaurant selected through Google Places to prepare the report. Google Business Profile authorization is separate from the public report and is required only when an authorized customer completes Launch onboarding for a location.
To open the full AI Growth Report, a visitor gives their name, email address and, if they choose, a phone number. SOFRA stores these with the restaurant the report is about, the time they were submitted, and the IP address and browser of the request, and uses them to follow up about the report and to prevent abuse of the form. The form uses Cloudflare Turnstile to check that a person is submitting it; Cloudflare processes the browser data that check needs. The browser also remembers the details and which reports were opened, so the next report opens without asking again.
Google Business Profile data
When an authorized customer chooses Connect Google, SOFRA requests these scopes:
- openid to identify the Google account completing authorization.
- email to show and record which Google account is connected.
- https://www.googleapis.com/auth/business.manage to list Business Profile accounts and locations the account can access, read and refresh the selected profile, and manage a location's Manager access only after the customer gives separate consent.
SOFRA stores the Google subject identifier and email, scopes and token status, encrypted access and refresh tokens, selected account and location identifiers, and the supported profile information Google returns: business name, address, city, state, postal code, coordinates when returned, phone numbers, website URL, regular and special hours, categories, description, store code, Google location ID, and verification metadata. SOFRA also stores connection, consent, Manager-access, error, refresh, and verification records.
The customer's token is used only for that customer's authorized Business Profile actions. SOFRA's platform Manager identity uses its own staff-authorized grant. Customer tokens are never reused as SOFRA's identity.
How SOFRA uses and shares this data
SOFRA uses Google data to let an authorized customer select the correct profile, keep its mapping current, review profile information against the saved SOFRA location, and—after a second explicit consent—grant the configured SOFRA Location Group Manager access to that selected location. Google data does not silently overwrite the SOFRA location record; the customer chooses whether to use a conflicting name, address, or phone value. Google Business Profile hours remain distinct from ordering, delivery, and pickup hours. SOFRA uses its separate platform identity to accept the matching invitation and then checks Google again before reporting active access.
Google data is available to authorized users in the customer workspace and to authorized SOFRA staff who operate Launch Management. SOFRA sends requests to Google when those features need Google's OAuth or Business Profile APIs. The implementation does not sell Google user data or use it for advertising.
Storage and security
OAuth tokens and business tax identifiers are kept on the server and encrypted with authenticated encryption before database storage. The browser receives connection and profile status and masked tax identifiers, not reusable OAuth tokens or full stored tax identifiers. OAuth state values are hashed, expire, and can be used only once in the signed-in user's expected workspace context.
SOFRA records connection, consent, Manager-access, and staff actions in Launch and audit history so customers and staff can distinguish requested, pending, active, revoked, and failed states.
Disconnect, retention, and deletion
Disconnecting a Google authorization asks Google to revoke the grant and removes reusable access and refresh token material stored by SOFRA. The selected profile mapping, Manager-access record, consent history, and audit history remain so the customer and SOFRA can complete offboarding and understand what occurred. After onboarding, customers submit a disconnection request and authorized SOFRA platform staff perform the audited authorization, Manager-access, or mapping change. Automatic-reply controls remain separate and customer controlled.
The Google connection screen also provides Request data deletion. That records a request in the customer's Launch history for SOFRA staff review. Review is needed because the same authorization can serve more than one location and because Manager access may need to be removed first. Minimal event and audit records may remain to document that authorization, revocation, access removal, and deletion actions occurred; those records do not provide reusable Google access.
For a request covering other SOFRA account data, or if you cannot sign in, email info@get-sofra.com from an address that can be verified as authorized for the workspace. No fixed automatic deletion period is implemented for these retained records.
Your choices
- Leave Google disconnected while working on other Launch tasks; Launch readiness remains blocked until each launched location has a valid connection and confirmed profile mapping.
- Request disconnection from Launch Center for authorized platform-staff review.
- Independently pause, disable, or withdraw automatic-reply consent immediately.
- Request deletion from the connection screen or through SOFRA Support.
Questions and changes
Questions about this policy or a data request can be sent to info@get-sofra.com. This page will be updated when the implemented data practices change.
Last updated: 29 October 2026