A login popup gives account access a focused place in an interactive website. It can be useful when visitors want to save a draft, return to a learning activity, or keep a dashboard preference.
The important decision is the user journey: explain why sign-in helps, show a clear sign-in control, and let visitors return to their task once authentication is complete. The popup is one part of that experience.
What visitors experience with popup sign-in
| Feature | What it means for visitors |
|---|---|
| Hosted account login | Visitors complete sign-in with their Gammal Tech account in a dedicated popup. |
| Session confirmation | The website can check whether the current session is valid before loading account-specific information. |
| Saved preferences | Previously saved project data can be restored after successful sign-in. |
| Sign-out | Sign-out clears the local session; your website should then show its signed-out view. |
Gammal Tech’s website integration manages the popup and receives the session result. A popup is not a guarantee that unsaved work survives every browser interruption. If a draft matters, your application should make its save status clear and provide an appropriate recovery experience.
Sessions and saved preferences are different
The active session is kept per browser tab. A visitor who opens a fresh tab or reopens the browser signs in again. This should be explained wherever people expect to resume work.
Saved project data has a longer life: the same user can retrieve it across visits and devices after signing in. Each user has a 1 MB storage limit. Preferences, reading lists, and compact progress records are suitable examples; the storage feature is not a promise of unlimited file uploads.
Login does not pass the account’s email address, phone number, or identity to your website. This lets you provide continuity without automatically building a directory of personal contact information.
What the project owner needs to set up
Start with a verified Gammal Tech owner account and create a project in the Developer Console. Register the HTTPS domains that will use the service. Up to four domains are supported, and the main domain and its www version count separately.
The integration uses a project identifier and registered domains without developer API keys to manage. Your developer connects the website’s controls and checks the project settings against the current reference. If you are replacing an existing login, account linking and historical-data migration need their own plan.
Design a helpful sign-in journey
- Start from an intentional action. Let the visitor choose Sign in or Save, rather than opening a popup unexpectedly.
- Explain the benefit. Say whether sign-in will restore preferences, save progress, or reopen a workspace.
- Allow a second attempt. Browser settings may block the popup, or the visitor may close it. Give a clear way to try again.
- Confirm the result. Show the signed-in state and explain whether the requested work has actually been saved.
- Keep sign-out visible. Make it easy for people using a shared device to leave their account view.
Starting from a user click helps with common popup policies, but it does not guarantee that every browser or extension will allow the window.
Login is free; code delivery has its own allowance
Currency guide: Listed EGP prices are the billing amounts. USD figures are approximate, using USD 1 = EGP 51.78, the calculated midpoint of Banque Misr’s USD buying and selling rates on 24 September 2026. Your payment provider’s exchange rate and fees may differ.
Login, logout, session verification, and user storage within the 1 MB limit are free. Each project receives 200 OTP codes per month for login and checkout identity verification; additional codes cost 0.40 EGP (approx. US$0.0077) each.
To pay for additional codes, fund your personal wallet, then transfer money into the project balance. Those are separate balances. Paid OTP operations stop when the project balance runs out, so include balance checks in your operating routine.
Common questions
Will the popup always open?
No browser outcome is guaranteed. Use a clear visitor action and provide guidance if browser settings block the window or the visitor closes it.
Will visitors stay signed in across new tabs?
The session is kept per browser tab. A fresh tab or reopened browser requires sign-in again.
Can visitors keep their saved preferences across devices?
Yes. Project data saved for their account persists across visits and devices and can be loaded after sign-in, within the 1 MB per-user limit.
References
- Gammal Tech API reference — account setup, hosted login, project funding, pricing, and user storage limits.