PILOT PRIVACY NOTICE / OCTOBER 2026

Your information.

crickts is a founder-led pilot operated by Héctor Jasso. For privacy questions or account/data removal requests, email hector@neltik.com.

Browsing this site

The landing page has no advertising pixels or analytics scripts. Our hosting infrastructure processes requests to serve the website and may keep operational and security logs. The waitlist stores the name, email address and optional product description you submit, request time and review status. If you arrived from one of our ads, it also stores which page and ad campaign link brought you. We use them to review access and send an invitation if approved. Submission does not activate an account or authorize marketing outreach.

Client accounts

For invited clients, we store the account email, client name, a hashed password, hashed setup and session tokens, and the booking link, time zone and confirmations you save. This supports sign-in, recovery, abuse prevention and your booking setup. Account data is hosted on AWS in the United States. Email inquiries are handled through the founder’s email provider.

Campaign evidence and outcomes

Your private workspace also stores prospect research, business contact routes, draft messages, and the reply and meeting evidence your team records. These records support your campaign, preparation and experiment reviews. Corrections preserve an audit trail while excluding invalidated records from active metrics. We do not pool this information across client workspaces. Please record only information needed for the campaign.

Cookies and Google Calendar

Signing in sets a necessary session cookie that expires after eight hours. We do not use advertising cookies. A Google booking link does not give crickts access to your Google account, calendar contents or contacts. Visiting your booking page or other Google links is subject to Google’s own policies.

Optional Gmail connection

If you connect Gmail, crickts stores encrypted access credentials to send only messages you explicitly approve and submit. We store the approved message, recipient, Gmail message and conversation identifiers, timestamps and incoming sender headers. Reply checks are limited to conversations sent through crickts; we do not import email bodies, attachments or unrelated inbox conversations. Google’s metadata permission permits broader header access than the conversations our application checks. We use Google data only to provide your outreach and reply tracking, not for advertising, cross-client insights or training generalized AI models. Our use of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements. Disconnecting removes saved credentials; campaign records remain until you request their removal. You may also revoke access in your Google account.

Retention and requests

Waitlist requests are kept while under review; you can request removal using the contact above. We keep account, booking and campaign information while it is needed to operate your pilot account. Expired session and authentication-attempt records are cleaned during authentication activity. Infrastructure backups may retain prior copies under the backup retention policy. Contact us to request access, correction, account closure or deletion; we may need to verify account ownership.

Outreach is separate

Creating an account, submitting an inquiry or saving a booking link does not authorize outreach. Any campaign scope and outbound activity must be agreed separately.