- Technical.ly is wholly owned by Technically Media Inc., a Philadelphia-based corporation
- Technical.ly does not have investors or other financial backers
- Technical.ly does not have investments in other companies or projects
- Technical.ly earns its principal income from events sponsorship, advertising and services on the Technical.ly web site
EDITORIAL CONTENT POLICY
- Above all else, we value transparency. If we make any significant changes to a story, we’ll tell you. If there is a potential conflict of interest, we will disclose it. If content is sponsored, supported, or part of a previously agreed-upon partnership, we will disclose that relationship as defined in our Sponsored Content and Events policies on the piece of content in question.
- We correct factually inaccurate information that we provide. If we report something incorrectly, we will correct it as soon as possible, in the published story with a time-stamped update notice on that article. When necessary for particularly important corrections, we will also share a correction via the same communication methods we use to promote all of our content.
- Community journalism should be a conversation. If a reader emails, comments, tweets, writes a blog post or otherwise responds with criticism, a request for clarification or a comment commenting offering perspective on our coverage, we will do our best to respond in a timely manner.
- Once we publish content, it will not be removed. As stated above, we will correct factually inaccurate information. In extremely rare situations (we have never done this before) in which a piece of content is entirely structured incorrectly, we may replace it with a note of clarification but no content will be entirely removed.
- If it’s on the record, it’s on the record. We will not remove content and quotes of a conversation that happened during an on-the-record conversation. That said, like any other journalist, we regularly speak with sources ‘off the record for background,’ as that perspective can help us report our beats more accurately. A source on the record, though, is always the most transparent and something for which we strive.
- Sources do not preview Editorial Content before it is published. Please do not ask to preview before published, we will not honor any such requests. We may ask for clarification of a quotation or figure, reference or number. We often follow up to do our job more precisely. This should be contrasted with Sponsored Content, which can be previewed by sponsors and is disclosed.
- We give credit. We will always link to the sources of a tip or story and expect others to do the same when writing about a topic first, recently or well reported by Technical.ly.
- All content posted by users to Technically Media Inc. owned and operated web properties (collectively “User Content”), including, but not limited to story comments, whether publicly posted or privately transmitted, is the sole responsibility of the person who posted the User Content.
- You agree not to provide User Content that is false, misleading, libelous, slanderous, defamatory, obscene, abusive, hateful or sexually-explicit. Citing Section 230 of the federal Communications Decency Act of 1996 as a news publisher, Technically Media is not responsible for the content of online comments, but we only support productive and welcoming discussion.
- Technically Media does not and cannot inspect all User Content and is not responsible for these messages. Technically Media is not in any manner endorsing any User Content and cannot, and will not, vouch for its reliability.
- Technically Media is not responsible for any User Content and has no obligation to monitor the User Content posted on the Services. When Technically Media is notified, comments that are violent, hateful or clearly false will be removed. Technically Media can edit content to remove these harmful elements, if the rest of the comment is productive, relevant and accurate.
SPONSORED CONTENT POLICY
- Technical.ly publishes both Editorial Content, independently reported, and Sponsored Content, which includes direction from sponsors. Editorial Content is never influenced, edited or reviewed by outside parties. The sponsoring entity behind Sponsored Content is given a limited timeframe to offer feedback on that content it underwrote. In all cases, Technical.ly’s editorial team has final say on what is published and prioritizes accuracy and reader value.
- Above all else, Technical.ly values transparency. Sponsored content that generates revenue for Technical.ly will always be clearly marked.
- We promise that all sponsored and advertising content will be clearly distinguishable from editorial content, marked with appropriate language to make that distinction.
- We maintain a high standard for our editorial product, whether sponsored or independent, which we feel delivers greater value to our audience and other supporters.
- We hold the right to refuse or remove any advertising that is inconsistent with or could disparage, harm or damage our community or the Technical.ly brand.
- Technical.ly “Sponsored Content” is content created by the Technical.ly Creative team and paid for by a client. A “Sponsored Guest Post” is produced by a client.
- As a community news organization, we often also accept and publish Editorial Guest Posts, which are unpaid, that strengthen that community.
- We adhere to these guidelines when defining the difference between Sponsored and Editorial content:
- Does the organization benefit financially? i.e. Are they promoting an event/program from which they will profit?
- Is the organization/person headquartered or have significant operations outside of the Technical.ly market in which they intend to promote?
- Are they a company larger than 20 employees?
- If there is a significant enough community focus or journalistic cause to merit it fitting our editorial mission, Technical.ly’s Publisher will make the final decision in any unclear situations.
- We strive to host events that are complementary to our editorial mission and editorial ethics. We believe both our editorial team and business team can contribute to and benefit from our events programming. Editorial is in a clear position to contribute speaker ideas, programming topics, and to lead discussions and provide events coverage. Our editors ensure that reporters maintain editorial independence and represent an unbiased perspective.
- We aim for a diverse representation of experience and opinions among our event speakers and participants. Their views are their own, and do not represent Technical.ly opinions or editorial directives.
- Technical.ly events are comitted to providing a harassment-free experience for everyone, regardless of gender affiliation, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form.
- We strive to have our events be a welcoming, friendly event for all and expect all event related communications to be appropriate for a professional audience including people of many different backgrounds. We ask all attendees to support this atmosphere.
- We value transparency and disclose event partners and sponsors in our marketing material and in Editorial Content. Sponsors and partners participate in event programs based on predetermined agreements, and those agreements can include Events Sponsorship and Sponsored Content initiatives.
- For ticketed events, Technical.ly offers this return policy: “For events hosted by Technical.ly, we will honor full refunds for orders canceled 30 days or more prior to the ticketed event. If cancelled 29 days or fewer before the event, the ticket can be transferred to another guest or applied as credit for a future Technical.ly event. NO CREDITS OR REFUNDS will be given to cancellations made within 24 hours or less of the event.”
- Technical.ly recommends the above return policy for events in which we are partners, but cannot override another organization’s policy.
- Technical.ly events with a topical subject are open to publishers, reporters and other news media with prior written consent and an expectation of content sharing with reference to Technical.ly’s role.
- Attendees are responsible for their own travel to and timely arrival at the event. Refunds are not given for traffic, transit delays, parking difficulty or other transportation issues out of our control.
- We will do our best to provide post-event editorial coverage that adheres to our Editorial Content policy.
- By providing Technical.ly with your email address, you consent to our use of the email address to send you notices related to Technical.ly. We may use your email address to send you messages, such as newsletters, or transactional or relationship messages, related to your registration or account status, and notifications of changes to the terms of your account or the services provided. By providing your email address, you agree that we may send you notifications of activity from Technical.ly to that email address, in accordance with any applicable privacy settings.
- We don’t share your e-mail address with anyone without your explicit permission.
- Email messages from Technical.ly will include clear instructions on how to opt out from that list.
- Technical.ly takes reasonable precautions to prevent the loss, misuse, and unauthorized alteration of Personal Information under our control.
- When you access any part of our Web Sites, our Web server software automatically logs information provided by your network connection and Web browser software, including the Internet Protocol (IP) address of your network connection and the type of Web browser and operating system that you are using. Our Web server may also log the URL of the file that you are requesting, the current date and time, and the URL of the last Web page requested by your Web browser.
- Technical.ly analyzes this aggregated information to learn more about how visitors use our Web Sites, to analyze trends, to administer the site, to track visitor movement, and to gather general demographic information for reporting and sponsorship purposes.
- At Technical.ly, we understand the importance of exercising caution when sharing Personal Information about yourself or information your organization via the Internet. Please be assured that we are committed to maintaining your privacy and protecting the information that you submit on our Web site.
- This page was last updated on Dec. 12, 2014