Privacy policy

The IEB Campaign Portal is a private, invitation-only workspace run by the candidate's campaign team for an Institution of Engineers, Bangladesh (IEB) election campaign. It helps a small team of approved volunteers organise outreach to IEB member engineers — calls, SMS, WhatsApp and email — and keep track of it. It is not an official IEB service.

The candidate's campaign team decides how the information in the portal is used and is responsible for it. Contact: the campaign admin.

• IEB member list. From the IEB voter list used for the election: name, IEB membership number and type, mobile number, email address, mailing address, engineering division, university, passing year and IEB center. To help filtering, the portal also estimates a likely employer from the address and gender from the name; team members can correct these.
• Campaign records. Support status, tags and notes added by team members, a “do not contact” flag, and a contact history (channel, date, which team member, outcome).
• Pledges. What people enter on the public support page: name, mobile number, and optionally their IEB membership number and a message.
• Team member accounts. Name, email address, mobile number, IEB membership number (optional), role, approval status, sending budget, and a record of the messages each member sent through the portal.
• Email connections (only for team members who choose to connect their own email). See Google user data below. If an admin has allowed it, a member may instead connect a mailbox with an app password; it is stored encrypted in the same way and deleted on disconnect.
• Technical data. Sign-in cookies that keep you signed in. The portal uses no advertising or analytics cookies. Our hosting providers keep standard server logs (for example IP address and time of a request) for a short time for security.

• Only to run this election campaign: finding and filtering IEB members, contacting them about the candidate and the election, and recording who has been contacted.
• Members marked “do not contact” are left out of every campaign. A weekly limit stops any member from receiving too many messages, and automatic sending pauses at night (Bangladesh time).
• We do not sell or rent this information, use it for advertising, or use it to train artificial-intelligence models.

• Only team members approved by an admin, after signing in. Admins can suspend an account at any time.
• Service providers that run parts of the portal for us, only to provide that service: Supabase (database and sign-in), Vercel (website hosting), the SMS gateway when an SMS is sent, Brevo when the team's email service is used, and Google when a team member sends from their own Gmail. Each message's recipient details go to the provider that delivers it.
• Authorities, if the law requires it.

Team members can connect their own Gmail account so that campaign emails they choose to send go out from their own address. This section explains exactly what the portal does with information it receives from Google.

What the portal asks Google for

• https://www.googleapis.com/auth/gmail.send — shown by Google as “Send email on your behalf”. This is the only Gmail permission the portal requests. It allows sending messages; it does not allow reading, searching, changing or deleting any email.
• Your basic account identity (openid, email): your Google account's email address, so the portal can show which account is connected and send from that address.

How it is used

Only to send campaign emails that you chose to send. You pick a campaign and start sending; the portal then sends one personal email per recipient from your Gmail account, within a daily limit, and the messages appear in your Gmail “Sent” folder. Nothing is sent from your account unless you start it.

What the portal never does

The portal never reads, searches, stores or otherwise accesses the content of your mailbox — your emails, contacts, attachments or settings. The permission above does not allow it.

What the portal stores

• A refresh token — the key Google issues so the portal can send on your behalf until you revoke it. It is stored encrypted (AES-256-GCM) in the portal's database, decrypted only by the portal's server at the moment it sends (or revokes access when you disconnect), never logged and never shown to anyone, admins included.
• Your Google account's email address, its Google account ID (a number that tells the portal which account is connected, so one Gmail account is connected by one team member only), the permissions Google granted, and when you connected it.
• The portal's own campaign record that an email went to a member, when, and whether it was accepted — the same record the portal keeps for every channel. Nothing from your mailbox.

Disconnecting and deletion

• Disconnect on the portal's My account page deletes the stored token immediately and asks Google to revoke the portal's access.
• You can also remove access at any time in your Google Account: myaccount.google.com/permissions. The portal can then no longer send from your account.
• When a team member's access to the portal is removed or suspended, their email connection is deleted too, and the portal asks Google to revoke its access.

Sharing and Limited Use

We do not sell Google user data, share it with anyone, use it for advertising, or use it to develop, improve or train artificial-intelligence or machine-learning models. The only Google user data people can see is which Gmail address a team member connected — shown to that member and to admins; nobody can see the token. The only transfer is the email itself, sent through Google to the recipient you chose.

IEB Campaign Portal's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• The member list, campaign records and pledges: only for this election campaign. They are deleted after the election.
• Team member accounts: until the campaign ends or the member asks to be removed.
• Email connections (including Google tokens): until you disconnect or your portal access is removed — then deleted immediately. If you remove access in your Google Account instead, the stored token stops working at once; press Disconnect in the portal to delete it as well.
• Server logs: kept by our hosting providers for a short period under their own policies.

• IEB members can ask not to be contacted again (we mark you “do not contact”), ask what the portal holds about you, or ask us to correct or delete your contact details.
• Team members can update their profile and disconnect their email on the My account page at any time, and can ask us to delete their account.
• Send requests to the campaign admin. We reply as soon as we can, and within 30 days.

Only approved, signed-in team members can open the portal, and every database request is checked against that member's permissions. All traffic uses HTTPS. Email passwords and Google tokens are encrypted, and nobody — admins included — can read them back.

If this policy changes, we update the date at the top of this page. Questions about this policy or your data: the campaign admin.

See also the terms of use for team members.