Privacy Policy
Reply Relay is an app for HighLevel (LeadConnector) sub-accounts. It is operated by Ali Özgür Ketenci ("we"). This policy explains what data the app handles and why.
Data we access and store
- Access tokens issued by HighLevel when you install the app.
- Your settings: the owner mobile number you enter and whether relaying is on.
- Reply codes: a short number (e.g. #12) linked to each customer's contact ID and display name, so replies reach the right person.
- Counters: how many messages were forwarded and replied to.
Message text passes through our server only to be forwarded; we do not store message content. To forward messages we read the sender's contact name and create one contact for the owner's number in your sub-account.
How we use it
Only to forward inbound text messages to the owner's mobile and to send the owner's replies back to the right customer, using your sub-account's own phone number. We do not sell, rent or share your data, use it for advertising, or use it to train AI models.
Messaging costs and compliance
Messages are sent through your sub-account's phone system, so standard messaging fees from your provider apply. You are responsible for having consent to text your customers and for complying with messaging rules (such as A2P 10DLC and TCPA) that apply to your business.
Where it is stored
On servers in the United States operated by our infrastructure providers: Railway (application hosting) and Supabase (database). Data is encrypted in transit.
Retention and deletion
When you uninstall Reply Relay from a sub-account, we delete that sub-account's tokens, settings, reply codes and counters. You can also ask us to delete your data at any time by emailing clearstagelabs@gmail.com.
Your rights
Depending on where you are, you may have the right to access, correct, delete or export your data, or object to its processing. Email us and we will respond within 30 days. If you are an agency installing Reply Relay for a client, you are responsible for having the right to share that client's data with us.
Changes
We will update this page if our practices change and revise the date above.