Privacy

Effective October 14, 2026. Halo is operated by Superbloom Labs. Contact ternlyteam@gmail.com about privacy or data rights.

What Halo processes

• Shopify store and customer identifiers, customer or checkout email, accessible order identifiers, dates, status and purchased items, and product information.
• Creator directory email, name, profile images, social handles, profile links and follower snapshots, linked to matching store customers.
• Manager login email and account identifier, store connection, notification preferences, discovery/read state and processing authorization.
• When enabled, sequence drafts, recipient enrollment, customer marketing permission, sending schedules, delivery outcomes and unsubscribe or suppression records.
• Authentication and limited access/security records. We do not put customer emails, profiles, order contents or credentials in application logs.

Why we use it

On the merchant’s instructions, Halo matches normalized customer emails to creator emails, displays matching profiles and their purchases, creates requested CSV exports, and sends the merchant readiness and weekly notifications. Saved customers and orders can match creators added to the directory later. An email match is a discovery lead, not verified identity or permission to contact someone.

We use manager details to authenticate access, provide support and protect the service. Essential authentication cookies support web sign-in. Optional message sequences send merchant-authored emails only after the merchant connects a sender and enrolls eligible customers. Halo checks the customer’s current Shopify marketing permission before sending. We do not sell store customer data, add it to a shared creator directory, or use it for advertising or consequential automated decisions.

Connected Gmail and sending domains

Connecting Gmail authorizes Halo to read email content and labels, send emails you compose or schedule, and synchronize read and archive state. We access the verified Google account identifier, mailbox address, message and thread identifiers, participants, headers, timestamps, bodies and attachment metadata. Attachments are retrieved when an authorized user downloads them; remote images and tracking content are blocked in the reader.

Halo initially imports the past two years of email and keeps a private archive updated so earlier conversations can appear when you add someone to Contacts. Unrelated messages are retained privately but do not appear in the workspace. Only current Contact conversations are shown. History sharing is private by default and separate from permission for teammates to send from your inbox. We retain this archive until you disconnect the Google account; disconnecting removes its archive and synchronization cursor from Halo.

Verified-domain emails are sent through Resend, using the connected Gmail inbox for replies. Resend receives the sender, recipient, message content and delivery identifiers needed to send the message and report its outcome. Recipients see the sender and reply address selected by the merchant. Reply detection, unsubscribes and delivery failures prevent further sequence sends; they cannot recall a message already submitted to the provider.

Google account data is used only to provide these connected-email features and protect their operation, in accordance with Google’s API Services User Data Policy and Limited Use requirements. We do not use it for advertising, sell it, or use it to train general-purpose AI models. Human access is restricted to specific consented support, necessary security investigation or legal requirements.

Who processes data

Vercel provides hosting, task delivery and operational logs; Supabase provides database and authentication; Resend delivers sign-in, merchant notifications and enabled domain sequences. Google provides connected Gmail message, attachment, sending and label access. Shopify supplies store data and embedded authentication. Service providers process only what is needed for their role. Hosting and delivery may involve processing outside your country. Social profile and product links lead to third-party services with their own policies.

Retention and security

Store records are retained while the merchant uses Halo for ongoing discovery. On uninstall, Halo stops processing and deletes app-held store personal data within 48 hours. Shopify erasure requests remove the affected records. Web account deletion is available through support; disconnected login accounts remain until that request. Operational logs follow the hosting provider’s configured retention.

We use encrypted transport and storage, encrypted Shopify and Gmail credentials, authenticated store-specific access and restricted operator access. Any retained database backup must be encrypted and access-restricted; deletion requests must be reapplied before a restored copy is made available.

Your choices

Merchants can change notification preferences, export results, stop sequences, disconnect senders, uninstall Halo or request account deletion. Disconnecting Gmail immediately removes Halo’s stored connection tokens and private mail archive, and holds scheduled emails that depend on that inbox. Sequence history remains until the associated store or customer data is erased. You can also revoke Halo’s access in your Google Account’s third-party connections settings. Customers can use an email’s unsubscribe link and should contact the store for access, correction, deletion or objections; we assist the merchant and handle Shopify privacy requests. Creators can contact us to request review or removal of their directory record. We verify requests before disclosing or changing data.

Merchants are responsible for customer notices and any required lawful basis or consent, including before using exported contacts. See the data-processing terms for our respective responsibilities. We will communicate material changes before they take effect.