FinchSend documents
Anti-spam and acceptable use policy
Acceptable Use Policy (AUP): rules for collecting contacts, sending messages and handling abuse in FinchSend.
Version dated
Operator and abuse contact
- Full legal name
- Ecom Mariusz Małachowski
- Registered / correspondence address
- ul. Poleska 23/6, 15-476 Białystok, Polska
- Tax ID and registration details
- NIP: 5432027712
- Abuse reports and appeals
- biuro@brandstyle.pl
1. Scope
This policy sets out user responsibilities for FinchSend campaigns, contact imports, signup forms, test messages, integrations and campaign assets. It protects recipients and the reputation of sending domains and infrastructure shared by customers. The operator is identified above.
This policy supplements the terms of service. It does not replace the privacy policy, data processing agreement (DPA) or the sender’s obligations to recipients. You are also responsible for people and integrations you allow to use your account. Paying for a plan does not authorise unsolicited email.
2. Permission and permitted contact sources
Send marketing campaigns only to people who have knowingly agreed in advance to receive email from that sender for the stated purpose. Consent must be freely given, specific, understandable and withdrawable. You must also establish a lawful basis for processing and provide the required privacy information. In Poland, Article 398 of the Electronic Communications Law governs marketing communications; a legitimate interest in processing data does not replace consent required for the email channel.
Purchased, rented, traded, scraped and guessed addresses, lists taken from public websites or directories, and cold outreach without prior permission are prohibited. A public business address, business card, purchase or social media connection does not by itself subscribe someone to a newsletter. This also applies to B2B messages and consent requests sent to unsolicited lists.
Migrating your own list from another provider is allowed if you can demonstrate permission covering the same sender and purpose. Carry over unsubscribes, bounces and complaints as well. FinchSend forms use email confirmation (double opt-in); importing an active, verified contact is not evidence of lawfully obtained consent.
3. Consent evidence and list maintenance
Before importing, keep evidence of the recipient’s address, signup date and method, form source, consent wording at signup, sender identity and scope of communications. Retain confirmation evidence where confirmation was used and subsequent withdrawals. Keep only what is necessary to demonstrate permission for a justified retention period.
On a justified request, provide the operator with evidence for the contacts in question and explain the list’s origin. Do not send a whole list without agreeing a secure transfer method. If you cannot demonstrate permission, exclude those addresses from sending; do not send them a campaign asking to confirm consent.
Regularly review list accuracy, exclude invalid addresses from active sending and assess whether recipients still expect your messages. A lack of recorded opens alone does not prove disinterest: mail software may block or automatically fetch images.
4. Sender identity and message content
Each campaign must clearly identify the actual sender, give their name, current postal address and working contact details, and explain why the recipient is receiving it. Subjects, display names, reply addresses and links must not mislead. Do not impersonate another person or brand or fabricate a previous conversation.
Use only domains you are authorised to use. Maintain domain verification, correct SPF and DKIM, and DMARC in line with mailbox provider requirements and configuration guidance. Do not rotate domains or identities to evade a restriction.
Send tests only to your own inboxes or people who have agreed to participate. Do not use tests or signup confirmations as a campaign channel. Technical messages must respond to a real recipient action; adding promotions does not exempt them from marketing rules.
5. Unsubscribes, complaints and bounces
Every campaign must provide a visible, working, free unsubscribe link requiring no login. Do not remove or hide it, obstruct its use or bypass unsubscribe mechanisms supported by the service. Requests received through other channels must also be acted on without delay by excluding the address from further marketing.
Do not send further campaigns after an unsubscribe or spam complaint. Exclude addresses that permanently bounce and investigate recurring temporary failures before sending again. Do not restore blocked contacts by reimporting them, deleting and recreating them, switching lists or opening another account.
A previous subscriber wishing to rejoin must initiate a new, documented signup and the previous restriction must be resolved with support. This does not authorise you to remove a complaint or permanent-bounce restriction yourself. An unsubscribe cannot recall messages already handed to the mail provider.
6. Prohibited content and activity
Fraud, phishing, malware, credential theft, threats, harassment, unlawful content and infringements of others’ rights are prohibited. This covers message content, included materials and linked destinations.
The sending provider also prohibits campaigns involving pornography, escort services, pharmaceuticals, gambling, MLM or pyramids, get-rich-quick offers, credit repair or debt relief, payday loans, list trading, and selling followers or likes. Resolve uncertain cases with the operator before importing or sending; the Resend restrictions linked below also apply.
Do not overload the service, attack forms, subscribe others without their knowledge, access others’ data or evade limits and safeguards using multiple accounts or integrations. Do not put confidential data in publicly accessible campaign images. Report suspected account or integration-key compromise to the operator without delay.
7. Sending quality and reputation
Review campaign results and act on rising bounces and complaints. FinchSend’s recommended operational targets are below 2% bounces and below 0.05% spam complaints. These are quality guidelines, not a spam allowance or a guarantee of continued sending.
As of this edition, Resend requires bounce rates below 4% and spam complaint rates below 0.08%; exceeding them can lead to provider restrictions. Its current requirements apply, and mailbox providers may use additional criteria. Calculation methods and reporting periods can differ, so a single campaign’s rate should not be equated with the provider’s account-level rate.
A sudden rise in complaints, spam traps, suspected account compromise or missing consent evidence can justify intervention regardless of percentages or list size. No recorded complaint does not prove that sending is acceptable. FinchSend does not guarantee inbox placement.
8. Responding to violations
The operator may request explanations and consent evidence, require you to stop a mailing, block an account or terminate service under the terms. The assessment considers severity, repeated violations, report credibility, recipient risk and your cooperation.
Immediate risks to recipients or infrastructure, phishing, bulk spam or a provider requirement may result in a block without prior warning. The operator communicates the reason, scope and way to resolve the matter, unless prohibited by law or disclosing details would undermine service protection.
Resumption requires correcting the cause, providing the necessary explanation and an operator decision; lowering a rate alone is insufficient. Reviewing reports and applying restrictions may require staff action and are not a promise to detect every violation automatically. A block does not determine subscription settlement or remove complaint or statutory refund rights.
9. Report spam or appeal a restriction
Report suspected abuse to biuro@brandstyle.pl, preferably with the subject “FinchSend — abuse report”. No FinchSend account is needed. Include the sender, date, subject, a description and, if available, the message ID. The original message or headers can help identify the source; redact unrelated data and never send passwords or entire contact lists. Do not open suspicious links just to prepare a report.
The operator reviews the report as necessary to investigate and may request more information. Reporter details are not routinely shared with the sender; any disclosure requires a justified need and lawful basis. The privacy policy explains how correspondence is processed.
Appeal a restriction by emailing biuro@brandstyle.pl with your account email, explanation, permission evidence and corrective steps. The operator reassesses the case and replies to the supplied address. An appeal does not automatically resume sending; service complaints follow the terms of service.
10. Versions and related documents
This policy is available without signing in. Its version date appears at the top; you can save or print a copy using your browser. Policy changes are communicated under the terms, identifying the changes, reasons and when they apply. Action needed to contain ongoing abuse may be taken immediately.
Publishing this policy does not record a particular user’s acceptance or recipient consent to marketing. Nothing here limits mandatory rights of users or data subjects.