Who we are
Our website address is: https://albinson.iafr.org.
The site is affiliated with International Association for Refugees (IAFR), a US registered 501(c)3 nonprofit agency that helps people survive and recover from forced displacement.
Physical Address: 1515 East 66th Street, Richfield, MN 55423 USA
Click here to contact us by email.
What personal data we collect and why we collect it
This blog collects no personal data from site visitors.
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
This blog does not include any contact forms.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
This blog does not collect or utilize any analytics or tracking services.
Who we share your data with
With the exception of approved comments posted by visitors to this blog, no data related to visitors to this blog is shared with anyone.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
Any questions related to privacy concerns can be directed to us in writing at our US office address or by email (see “Who we are” above).
How we protect your data
This blog is protected by an SSL connection. IAFR has also contracted the website hosting service to monitor and report on website security issues or concerns if they should arise.
What data breach procedures we have in place
Should concerns related to a data breach arise, we will immediately take the site offline until the issue is resolved.
What third parties we receive data from
This blog neither receives or shares data from third parties.
What automated decision making and/or profiling we do with user data
This blog includes no automated decision making or profiling with user data.