Sending email

Every email GIG sends on your organization's behalf carries your organization's own name, not GIG's — and it almost always goes out because someone on your team clicked Send.

Nothing sends in the background

There is no scheduled mailer — nothing sends on a timer or a cron job. Creating a link, filling in a draft, or generating a credential does not send anything by itself; for everything an operator can trigger, sending is a separate, explicit click. There are exactly two narrow, deliberate exceptions, both bounded by their own rate limits and both respecting suppressions: a public form can email the person who just submitted it their own copy (nobody on your team clicks anything — the respondent's own Submit does), and a stranger requesting a demo on GIG's marketing site triggers a notice to GIG itself, not to your organization. Neither is scheduled or background; both fire once, in direct response to somebody's own action.

What the recipient sees

• The sender name reads "Your Organization via GIG."
• The top of the message carries your organization's own name, or its logo if you've set one — never GIG's.
• If the message includes a button, the same destination is repeated as a plain link underneath it, so the message still works in inboxes that strip button styling.
• The footer names why the recipient received the message, followed by a small "Powered by" line carrying GIG's logo.
• Replying goes back to your organization's own contact address, not to GIG, so a reply reaches your team.

Every send is logged before it's attempted

If a send fails outright, that attempt still appears rather than silently disappearing. See Delivery status for what each status means.

Opens and clicks are not tracked

GIG does not add tracking pixels or rewrite links to detect whether a message was opened or a link was clicked. That's deliberate, not a missing feature — the same techniques that would report it back also make a message more likely to be filtered as spam.