What type of Social Data does Stackla store?
Stackla does not store any private or sensitive information relating to Social Posts ingested into the Platform.
Stackla, by design, only ingests social posts which have been made public on the various social networks and is compliant with the Terms and Conditions for each Social Network's API suite.
The information attributed to each social post (Meta Data) varies based upon the Social Network's API rules however at a high level includes:
- User Handle
- URL to Avatar Image
- URL to Social Image
- Social Text
Any enrichment of this data that maybe done by Stackla or a third party as part of the aggregation process is purely for display, filtering or moderation purposes.
All data downloaded is stored on the Stackla hosted infrastructure.
Where is Stackla infrastructure hosted?
Stackla is hosted on Amazon Web Service Sydney region at the SY3 Sydney IBX+ Data Center. The data centre is physically located in the Sydney metropolitan region of New South Wales, Australia.
As we utilise 100% cloud-based hosting, we understand that the specific location may change at any time, however remaining in the Sydney metropolitan region.
Portions of our assets are served via various Content Delivery Networks (CDN) from various locations across the world and of course from the social networks themselves. Social Networks store content such as images and videos on their infrastructure, which is commonly Akamai, CloudFront, Cloud Files and others.
Does Stackla outsource the management of infrastructure to other service providers?
Yes, Stackla outsources to Amazon Web Services.
Is all data stored within Australia? Is all Stackla infrastructure within Australia?
Yes, at present all of Stackla’s infrastructure is geographically located within Australia.
For performance purposes Stackla may utilise infrastructure located in other parts of the world for content delivery in the future.
Can we have access to web log files? How can we perform an audit of web server access?
We do not give access as we do not track each stack individually -- we track web server requests across the whole platform.
Splitting log records across stacks is not a trivial task and would only be permitted in the most extreme of cases due to the cost involved.
Requests should be made via the standard support process and will be treated on a case-by-case basis.