invokationPrivacy and early-access data
How the Invokation website handles waitlist information, optional research answers, consented analytics, storage, retention, and deletion.
Effective 20 October 2026. This policy describes the marketing website and early-access research, not an operating integration platform.
Operator and contact
This website is operated by Rafat Awartani. For privacy questions, correction, or deletion requests, contact rawartani@aaalabs.io.
What you submit
The waitlist stores your normalized email address and submission date. Optional research answers can include integration context, authentication pattern, role, team type, company name or site, systems to connect, main integration pain, approximate integration count, timing, exploratory price range, and permission for a design-partner conversation. Do not submit credentials, sensitive personal data, or confidential customer information.
Joining requests product-development updates and related early-access research. It does not create a product account, guarantee access, or require unrelated marketing consent. This website sends no automatic email. Addresses are not verified; an entry records a submitted interest request rather than verified mailbox ownership.
Storage and service providers
The static site is designed for Firebase Hosting. A Firebase function validates submissions and writes them to Google Cloud Firestore before returning success. The database is server-only; the browser cannot list leads. Access is limited through the hosting project's administration and service identity.
Qualification is authorized by a signed, HttpOnly session cookie lasting 30 minutes. Every accepted submission creates or resumes its own isolated research session. A returning email can submit new answers but cannot read or overwrite earlier sessions or their contact permissions. The cookie contains a scoped authorization capability and is not sent to analytics.
Necessary abuse prevention
The API validates request origin, bounds input size, checks a honeypot field, and applies Firestore-backed request limits. Short-lived rate-limit records contain keyed address digests and counters, not raw form bodies or raw IP addresses. Platform infrastructure may process IP addresses and request metadata in operational logs; do not put personal details in URLs.
Optional measurement
Google Analytics runs only after you accept optional analytics and only if a real measurement ID is configured. Events contain bounded categories such as CTA placement, integration context, team type, or primary need. We do not send emails, company names, free-text needs, lead identifiers, or signed cookies to analytics.
With analytics accepted, the site keeps first and last campaign touch for the current tab session using approved campaign fields and known landing routes. Refusing analytics prevents this optional attribution storage. Search Console provides aggregate search and indexing information, not a visitor-to-lead query record.
Retention, access, and deletion
Waitlist entries have a configured retention period of 365 days from their original creation. The operator must run the documented purge command and apply the same policy to exports. Rate-limit records expire operationally within about two hours and are removed through operator cleanup. Research sessions expire with their linked lead; their authorization lasts at most 30 minutes. Deleting a lead also removes its linked research sessions. Legacy answers remain separate. Expired sessions cannot save answers.
Once the owner contact above is configured, use it to request correction or deletion. The operator locates and removes the lead through protected Firestore administration and confirms the request as appropriate. Exports and backups require separate retention and deletion handling. There is no public deletion or export endpoint.
Your choices
You can join without accepting analytics and skip all qualification questions. You can revisit at any time. Withdrawal stops future measurement, clears applicable first-party analytics cookies where feasible, removes optional attribution, and reloads the page if the Google tag was loaded. It does not erase data already processed by Google.
See cookies and analytics for the storage details. The operator must confirm the configured processing location and any jurisdiction-specific disclosures before public launch.