Skip to content

Trust and security

Add Polargate as a safe sender.

If one of our emails lands in spam or arrives without images, this page shows how to fix it in your own inbox and, if you work in IT, for the whole company.

Download our contact cardGo to the IT section

Who writes to you

The addresses we send from.

Only these three. The links inside our emails point to polargate.ai and portal.polargate.ai. If something reaches you from another address that claims to be us, do not open it and tell us through the contact form.

  • hello@polargate.ai

    Projects, proposals and everyday conversation. Calendar invitations come from here too.

    Sent through
    Google Workspace
    Return path
    polargate.ai

  • invoicing@polargate.ai

    Invoices and payment reminders.

    Sent through
    Resend
    Return path
    send.polargate.ai

  • soporte@support.polargate.ai

    Support tickets and their replies.

    Sent through
    Resend
    Return path
    send.support.polargate.ai
Domains to trust
polargate.ai
support.polargate.ai
Address
hello@polargate.ai
invoicing@polargate.ai
soporte@support.polargate.ai

In your inbox

Two minutes in your own inbox.

Start by saving us as a contact: most mail programs trust a sender who is already in your address book. Then mark us as safe in the program you use.

Save us as a contact

The card holds the three addresses, POLARGATE S.L. and polargate.ai. Open it on your phone or computer and accept.

Download our contact card

01

Gmail

  1. 1.If one of our emails is in Spam, open it and click Report not spam.
  2. 2.Settings, See all settings, Filters and blocked addresses, Create a new filter. In From, type @polargate.ai OR @support.polargate.ai.
  3. 3.Create filter, tick Never send it to Spam and save.
  4. 4.Images: Settings, General, Images, Always display external images.

The filter lives in your Google account, so it also applies in the Gmail app on your phone.

02

Outlook for Windows (classic)

  1. 1.Right-click one of our emails, Junk, Never Block Sender's Domain.
  2. 2.Or: Home, Junk, Junk E-mail Options, Safe Senders tab, Add, and type @polargate.ai. Repeat with @support.polargate.ai.
  3. 3.Images: with us in Safe Senders, Outlook downloads our images as long as the Trust Center option to allow downloads from Safe Senders stays ticked (it is by default).

03

Outlook on the web and the new Outlook

  1. 1.Settings, Mail, Junk email.
  2. 2.Under Safe senders and domains, click Add and type polargate.ai. Add support.polargate.ai too.
  3. 3.Save.

04

Outlook on your phone

  1. 1.The app has no safe senders list of its own. With a work or Outlook.com account it uses the one you set on the web, so do the step above once.
  2. 2.If an email of ours is in Junk, open it and move it to the Inbox.

05

Apple Mail (Mac, iPhone and iPad)

  1. 1.Open the contact card above, or click our name in an email and choose Add to Contacts.
  2. 2.If one of our emails is in Junk, move it to the Inbox. On the Mac you can also click Not Junk.
  3. 3.Images on the Mac: Mail, Settings, Privacy. With Protect Mail Activity on, or Block All Remote Content off, images load.

Mail does not mark as junk a sender who is in your contacts, and with iCloud the contact reaches all your devices.

For your IT team

Let our email through for everyone.

Every message we send is signed with DKIM on polargate.ai or support.polargate.ai. Build the exception on that signature, never on the From line alone: anyone can type our address in a From. The console labels below are the English ones.

01

Microsoft 365: Tenant Allow/Block List

  1. 1.In Microsoft Defender go to Email & collaboration, Policies & rules, Threat policies, Tenant Allow/Block Lists.
  2. 2.On the Domains & addresses tab, add an Allow entry with polargate.ai and support.polargate.ai.
  3. 3.If your tenant does not let you create it there, submit one of our emails from Submissions as Should not have been blocked and tick the option to allow it: Defender then creates the entry.

02

Microsoft 365: transport rule with SCL -1

  1. 1.Exchange admin center, Mail flow, Rules, Add a rule, Create a new rule.
  2. 2.Condition one: The sender, domain is, polargate.ai and support.polargate.ai.
  3. 3.Condition two, the one that matters: A message header, matches these text patterns. Header Authentication-Results, with the pattern below. That is how the rule only fires when our DKIM signature has been verified.
  4. 4.Action: Modify the message properties, Set the spam confidence level (SCL), Bypass spam filtering. Save and turn it on.

Exchange Online writes the Authentication-Results header itself. If your mail passes through another gateway before Microsoft 365, check that header in a message of ours before relying on the rule.

The same rule in PowerShell
New-TransportRule -Name "Polargate (DKIM pass)" `
  -SenderDomainIs "polargate.ai","support.polargate.ai" `
  -HeaderMatchesMessageHeader "Authentication-Results" `
  -HeaderMatchesPatterns "dkim=pass[^;]*header\.d=(support\.)?polargate\.ai(;|\s|$)" `
  -SetSCL -1

03

Google Workspace: approved senders

  1. 1.Admin console, Apps, Google Workspace, Gmail, Spam, phishing and malware.
  2. 2.In Spam, edit the setting and tick Bypass spam filters for messages received from addresses or domains within these approved senders lists.
  3. 3.Create a list with polargate.ai and support.polargate.ai, and keep Require sender authentication ticked on both. Without it, a forged From would get through as well.
  4. 4.Save. The change can take a few hours to reach every account.

No IP addresses needed

We send through Google and through Amazon SES (via Resend), and their IP addresses change without notice. A rule on IPs breaks sooner or later; a rule on our DKIM signature does not.

Links in our emails

If you rewrite or filter links (Safe Links or a URL proxy), allow polargate.ai and portal.polargate.ai.

Authentication

Our DNS records.

SPF, DKIM and DMARC on our domains, exactly as dig returns them. Run the command yourself to check they are still the same.

Records checked on 13 October 2026.

  • SPF · Google Workspace (hello@)
    $ dig +short TXT polargate.ai | grep spf1
"v=spf1 include:_spf.google.com ~all"
  • SPF · Return path of invoicing@ (Resend)
    $ dig +short TXT send.polargate.ai
"v=spf1 include:amazonses.com ~all"
  • SPF · Return path of soporte@ (Resend)
    $ dig +short TXT send.support.polargate.ai
"v=spf1 include:amazonses.com ~all"
  • DKIM · Google selector on polargate.ai
    $ dig +short TXT google._domainkey.polargate.ai
"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxgtjZbrFoVcvoOPl64HKk4rjQnyz20Q1yBGn8wc6JoHJJuj/wanvMLhSrWpD2vRqDgotcwVvUFgkEdsLCfyAeQu6B/Kl1anigV4XmnR3GxxPjWKlzqYVziwihU4J5ZiT4SOSl+85IcMUZmf+dT1WsN2Fpl7sN6kkFFJt1MyzbUOKwEcrzLaSsff7pNBHoueD9" "LuEelRhYaw0etXVWb/bslTlhUwQvwYpTWWCr6zjuuvqSf09G0Y3pd98gNi8iWauuuSEPRYoyr0tLtCZX0SLfJzilZygpQom3KbRIYbUxvZFidKvlor/ypE2l5z5EwYl4XzD50I4DoPmY6Bf5PbzOwIDAQAB"
  • DKIM · Resend selector on polargate.ai
    $ dig +short TXT resend._domainkey.polargate.ai
"p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDUhLgp25oLmNuv8OVZ0cJ+OWXSNcTeP4nrJ8S4GevJF0HPtWEp25fXrUBF4qoTO75Iqr6LEI1raHwcMZPrVlZPfI+B3lK7IvahWIzZTtDNbmQYZljgKDlBx9cbanGQLq6pdbtkFRRk1kFWOXR9qg7nIodqTwACF1KiixdEob8gHQIDAQAB"
  • DKIM · Resend selector on support.polargate.ai
    $ dig +short TXT resend._domainkey.support.polargate.ai
"p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDBWpIm7zOfFWLz1Bg7Sp0RfMkXpFq4IQgu7Xgay+fK/Fv+GJ7pRvB2orZrkTHvOFp1RGCzoMKCNWQEOq7/XXzs5BAzkIXXpZ4XGE4A9z9pgPNHNXcuWlGCHBp57RKHvPF1UiwIq0mvE0Mvmlhk3/na6FKMo+whsPn84LvyjzqGKwIDAQAB"
  • DMARC · polargate.ai
    $ dig +short TXT _dmarc.polargate.ai
"v=DMARC1; p=quarantine; pct=25; rua=mailto:re+xb24gp4akjq@dmarc.postmarkapp.com,mailto:hello@polargate.ai; adkim=r; aspf=r; fo=1"
  • DMARC · support.polargate.ai
    $ dig +short TXT _dmarc.support.polargate.ai
"v=DMARC1; p=quarantine; rua=mailto:hello@polargate.ai"

FAQ

Frequently asked questions.

If your email is signed, why does it still end up in spam?
A valid signature proves the email is ours, but each filter still decides on its own, for example when nobody at your company has written to us before. Marking us as safe removes that doubt.
Can IT simply allow anything whose From is @polargate.ai?
Better not. The From line can be forged, so a rule on it alone also lets through anyone pretending to be us. Tie the exception to our DKIM signature, as in the steps above.
Do we need to allow your IP addresses?
No. We send through Google and Amazon SES, whose addresses change, and every message is signed with DKIM. Allow the signed domains instead.
Do I have to repeat this on every device?
Usually not. Gmail filters and the Outlook safe senders list live in your account, and an iCloud contact reaches all your Apple devices. Only the classic Outlook for Windows keeps some settings on the computer.
An email says it is from Polargate but comes from another address. What do I do?
Do not open links or attachments, and tell us through the contact form. We only write from the three addresses on this page.

For example: 39 tables with row-level security and zero errors in the August 2026 diagnostic. Globalia

Book a callTell us about your project

Get started

Tell us what you want to build.

Websites, apps, custom systems and AI for companies that need them in production in weeks. Fill in the form or book a 30 minute call: a senior engineer answers within 48 business hours with a first take on scope, timeline and price.

Book a 30 minute call
What do you need?
Budget
When

At least ten characters.

Answer in writing within 48 business hours. No newsletter, no automatic sequence.

Rather answer the full brief?

First step

Discovery Sprint

Two weeks to close scope, architecture and price before anything is built.

No price list. You get a private quote, in writing, after a short call.

Then, to build, always at a fixed price

Ask for your quoteHow we quote

Not ready yet?

AI-native digital studio for mid-market companies

POLARGATE, S.L. · CIF B24895005
Calle Electrónica 6, 28027 Madrid, Spain