Privacy Policy
How SMTP2Hook uses, protects and retains information when delivering email to your webhooks.
1. Who we are
SMTP2Hook (the “Service”) is operated by REXX IT LLC, a limited liability company registered in Wyoming, United States (“we,” “us,” or “SMTP2Hook”). The Service receives email addressed to customer-specific endpoints and forwards structured JSON to webhooks chosen by the customer.
Privacy questions and requests can be sent to smtp2hook@rexx-it.com. We will assess requests in accordance with applicable privacy laws.
2. Information we process
Depending on how you use SMTP2Hook, information may include:
- Account data: your name, email address, organization name, account and customer identifiers, password verification data, and account settings.
- Endpoint configuration: assigned SMTP addresses, destination webhook URLs, delivery settings, authentication configuration, and subscription-plan and usage information.
- Incoming email: sender and recipient addresses, email headers and metadata, subject, message text and, where included, attachments or attachment information.
- Delivery records: webhook delivery status, timestamps, retry attempts, response and error information, and related diagnostic records.
- Security and technical data: IP addresses, access and authentication events, session information, and logs generated by the Service and its hosting infrastructure.
- Billing and subscription information: plan, checkout, transaction and subscription identifiers, payment or subscription status, and billing events shared by Creem for Test Mode evaluation and Live paid checkout. Payment-card details are handled by Creem rather than entered into the SMTP2Hook portal.
Email can contain personal or confidential information about third parties. Customers should send only information they are authorized to process and forward.
3. Why we use information
- To create and administer accounts and verify users.
- To receive email, assemble webhook payloads, deliver messages, and retry failed deliveries.
- To manage configured endpoints, enforce plan limits and show delivery history.
- To detect misuse, protect accounts and infrastructure, investigate operational failures, and provide customer support.
- To communicate registration or verification information and important service notices.
- To verify checkout and subscription payments, process billing events, and provide the appropriate paid-plan access.
- To meet applicable legal and recordkeeping obligations.
Where privacy laws require a legal basis, the applicable basis depends on the processing activity and jurisdiction. It may include providing the requested service, legitimate security and operational interests, compliance with law, or consent where required. We do not use email message content for advertising.
4. Customer-controlled email content
Customers choose which email is directed to their SMTP2Hook addresses and which external systems receive its JSON webhook payload. We process this information to deliver the service and act on the customer's configuration. Customers remain responsible for having permission and a lawful basis to route message content, including information about third parties.
A destination webhook is controlled by the customer or its chosen provider. Once a payload reaches that destination, the destination's own security and privacy practices apply. SMTP2Hook is not an email archive and should not be treated as long-term storage.
5. Sharing and service providers
We share information only as necessary to operate SMTP2Hook, deliver information to customer-selected webhook destinations, respond to lawful requests, or meet legal requirements. Relevant service providers include hosting and infrastructure providers for the public website, Customer Portal and processing servers, and email-delivery providers for account communications.
SMTP2Hook uses Creem for Live paid subscription checkout and also uses Creem Test Mode for development testing. Creem handles checkout details under its applicable privacy terms, while SMTP2Hook receives the subscription and payment status information needed to assign customer plans and manage subscriptions. Payment-card details are not entered into the SMTP2Hook Customer Portal.
We do not sell personal information or the contents of incoming messages to advertisers.
6. Storage and retention
SMTP2Hook processes and forwards incoming messages. It is not a permanent email archive. The following describes normal operational retention:
- Original incoming email and attachments: the email file, including any attachments, is stored temporarily for delivery processing. The worker deletes this file following successful webhook delivery or a permanent delivery-policy rejection.
- Pending delivery queue: queue records may contain email text and delivery metadata. Failed deliveries are retried and ordinarily expire after 72 hours, when the worker removes both the original email and queued record. A service outage or exceptional failure can delay cleanup.
- Delivery history: retained for approximately 30 days. Records may include sender, subject, a message preview of up to 100 characters, timestamps, attempts, delivery status and error details, but not the full original email and attachments.
- Account and endpoint records: retained for account operation and as reasonably necessary for support, security and legal obligations. Customers may request deletion subject to applicable obligations and exceptions.
- Operational logs: may contain connection details, sender or subject information, login and diagnostic events. Logs are kept for operational and security purposes; no single fixed maximum retention period currently applies to all logs.
Routine server backups. The processing server at OVHcloud uses the Standard automated daily backup option, with a rolling backup normally replaced after approximately 24 hours. Information deleted from the live server may therefore temporarily remain in the backup copy.
Manual snapshots and software archives. Separately created server snapshots and older software-build archives are not subject to the daily backup rotation and may contain copies of operational records from the time they were created. They can persist until independently removed. We distinguish such archives from the normal live-message deletion schedule.
Customers should retain their own copies of messages they need to archive. Exceptional faults, required legal preservation, or recovery from a backup may affect the normal deletion times above.
7. Security
We use measures intended to protect the Service, including authenticated portal access, password hashing, session controls, rate limiting and validation of destination webhook addresses. However, no email or Internet transmission and no storage system can be guaranteed completely secure.
Customers should protect their account credentials and webhook authentication secrets and securely operate any external webhook receiver. We recommend not transmitting payment-card numbers, health records or other highly sensitive data through the Service unless appropriate safeguards have been separately evaluated and agreed.
8. Cookies and website data
The Customer Portal uses a session cookie to maintain authenticated access. Web and API infrastructure may also process standard technical connection information for delivery, diagnostics and security.
The current SMTP2Hook landing page does not load third-party advertising trackers or analytics scripts. If this changes, we will update this policy as appropriate.
9. International processing
REXX IT LLC is registered in the United States. The public website and portal use hosting in the Netherlands, and the SMTP/API processing server is hosted in Canada. Accordingly, information may be processed outside the country where a customer or email sender is located.
Cross-border processing may be subject to additional legal requirements depending on the jurisdiction. For questions about the hosting locations or international processing relevant to your account, contact us at smtp2hook@rexx-it.com.
10. Your privacy rights
Depending on your location and applicable law, you may have rights to request access to, correction of, deletion of, or portability of personal information, and in some cases to object to processing or restrict its use.
For requests, contact smtp2hook@rexx-it.com. To protect accounts and other individuals, we may need to verify the requester's identity. Some records may need to be retained to satisfy legal obligations or protect the integrity and security of the Service.
Where SMTP2Hook processes message content according to another customer's instructions, requests about that content may need to be directed to the customer who controls the endpoint.
11. Children and sensitive information
SMTP2Hook is intended for organizations, developers and operators of email-capable systems; it is not directed to children. Please avoid directing sensitive personal data through SMTP2Hook without evaluating whether the Service and downstream webhook destination have suitable protections for that use.
12. Updates to this policy
We may update this policy as the Service, its providers or applicable requirements change. The latest published version will carry an effective date, and we will provide further notice of material changes where legally required.
For privacy questions, contact smtp2hook@rexx-it.com.
Related documents: Terms of Service · Refund & Cancellation Policy.